• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2810
  • Last Modified:

Import-Mailbox cmdlet is not recognized

Exchange 2010 SP1

I followed dematzer's instructions at...
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2709-Importing-PST-files-in-to-Exchange-2010.html?sfQueryTermInfo=1+10+2010+30+exchang+file+import+pst

I have installed only Outlook 2010 x64 (plus the tools and shared comps)

I have both a security group and administrator added to role assignments and verified using get-managementroleassignment

Outlook and Exchange on same box single server setup

But still no import-mailbox ..........HELP!!!
0
BigBadWolf_000
Asked:
BigBadWolf_000
  • 12
  • 7
  • 3
  • +1
1 Solution
 
Glen KnightCommented:
This would normally indicate that the management role assignment isn't working.
Are you logged in using the "Administrator" user account?

How long is it since you ran the command?
0
 
tedoffCommented:
After creating the proper role assignment you'll need to make sure you log out and log back in to Exchange Management Shell.  If you haven't done that try that first.
0
 
BigBadWolf_000Author Commented:
I ran the command new-managementrole then restarted the server and tried import-mailbox
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
BigBadWolf_000Author Commented:
Yes logged in as administrator
In group member is administrator too
0
 
AkhaterCommented:
import-mailbox was removed in exchange 2010 sp1 and replaced by new-mailboximportrequest

http://technet.microsoft.com/en-us/library/ff607310.aspx
0
 
Glen KnightCommented:
BigBadWolf, I can only appologis, I have missed a whole section out of my article.  or it's at least a little ambiguous.

You have created the Management Role but have you added the users to the group you have assigned that role to?

Did you create a new group or use an existing one?
0
 
BigBadWolf_000Author Commented:
Here is what I get when I run get-managementroleassignment
Snap1.jpg
0
 
AkhaterCommented:
BigBadWolf just in case you missed my previous post

import-mailbox was removed in exchange 2010 sp1 and replaced by new-mailboximportrequest

http://technet.microsoft.com/en-us/library/ff607310.aspx
0
 
BigBadWolf_000Author Commented:
no i got it ....just reading up...would this syntax work
New-MailboxImportRequest -Mailbox Ayla -FilePath F:\PST\ayla.pst
0
 
BigBadWolf_000Author Commented:
Akhater: Can you help me identify the prerequsites.....does this mean Outlook 2010x64 is not required
 
0
 
AkhaterCommented:
yep you don't need outlook anymore for the New-MailboxImportRequest
0
 
BigBadWolf_000Author Commented:
do I still need the new-management roles that I created....
0
 
BigBadWolf_000Author Commented:
How do I remove this...I earlier created using othe instructions...Note: I do not wat to delete the Mailbox Import Export role but just the assigment (as created below)


New-ManagementRoleAssignment –Name “MailboxImportExport” –SecurityGroup “Mailbox-IER" –Role “Mailbox Import Export”
0
 
Glen KnightCommented:
Yes the management role is still required.

It's just a different command, the syntax is almost identical

(looks like I need to update my article)
0
 
AkhaterCommented:
I am sorry but what do you want to remove ?
0
 
BigBadWolf_000Author Commented:
Thanks i will leave the role assignments as they are...
Ok i ran the command new-mailboximportrequest...it accepted the syntax and went to queued status.

But after a few minutes I ran the get-mailboximportrequest and it shows as failed.

What should I do next?
0
 
AkhaterCommented:
we need to know why it failed check the report or paste the get-mailboximportrequest | fl
0
 
BigBadWolf_000Author Commented:
Yeah did the get-mailboximportrequeststatistics.....see attached
see results below...note: the pst was created in outlook2003 and then migrated to oitlook 2010 (no issues at the time) client  no exc server.
test.txt
0
 
BigBadWolf_000Author Commented:
I will run a pst repair and try again
0
 
AkhaterCommented:
well it proves all is working well :)

just add -BadItemLimit  10 (for example) or unlimited
0
 
BigBadWolf_000Author Commented:
Fixing the PST did it
0
 
BigBadWolf_000Author Commented:
Akhater: Thank you very much!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 12
  • 7
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now