Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, August 31, 2010 2:10 PM
Hi Tried to you the command as above but just get that error as below. Both Mailbox servers have sp1 installed and that is the consoles that I am running on. I must be missing something really silly. Thanks
The term 'New-MailboxImportRequest' is not recognized as the name of a cmdlet, function, script file, or operable prog
am. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:25
- New-MailboxImportRequest <<<< /?
+ CategoryInfo : ObjectNotFound: (New-MailboxImportRequest:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
All replies (11)
Tuesday, August 31, 2010 2:51 PM âś…Answered | 4 votes
Yeah, the cmdlets aren't visible if the role has not been assigned. Did you restart EMS after creating the role assignment? If not, that should solve the problem.
Tuesday, August 31, 2010 2:18 PM
are you first Launching Exchange Management Shell or just Powershell? Sean McNeill Microsoft Gold Partner http://staterainfrastructure.blogspot.com/
Tuesday, August 31, 2010 2:34 PM
Exchange Mangement Shell.
I am able to set the New-ManagementRoleAssignment but just can't run the New-MailboxImportRequest
Tuesday, August 31, 2010 2:40 PM
Your account may need a role assignment for the "Mailbox Import Export" role. It's not done by default.
http://technet.microsoft.com/en-us/library/ee633452.aspx
Tuesday, August 31, 2010 2:47 PM
I did already assign administrator to that. I figured it would just give me an access error not tell me the command isn't found?
Tuesday, August 31, 2010 2:54 PM
Darn you guys are good!
Thanks just had to restart.. Duh!
Thanks again
Tuesday, August 31, 2010 2:58 PM
Try Get-ExCommand *mailbox*, see whether import script was in the list.MT | MCITP Please vote helpful or mark as answer if it's answered your question, this help us follow up the question status.
Tuesday, October 11, 2011 8:33 PM
I've done every step outlined in this post and others like it and I'm still not getting the New-MailboxImportRequest cmdlst ... ARG!
I tried to re-add the admin to the security group and it says it is already there ...
[PS] C:\Windows\system32>Add-RoleGroupMember "Mailbox Import Export Group" -Member "Administrator"
The recipient "Administrator" is already a member of the group "xxx.com/Microsoft Exchange Security Groups/Mailbox
Import Export Group".
+ CategoryInfo : InvalidData: (Administrator:SecurityPrincipalIdParameter) [Add-RoleGroupMember], MemberA
lreadyExistsException
+ FullyQualifiedErrorId : 473E65FA,Microsoft.Exchange.Management.RbacTasks.AddRoleGroupMember
I've closed and reopened EMS ... as well as rebooting the server :)
Nothing seems to get around this ... I'm sure it is something silly but perhaps someone has an idea for me.
Thanks - Clay
Sunday, December 18, 2011 2:43 PM
I've done every step outlined in this post and others like it and I'm still not getting the New-MailboxImportRequest cmdlst ... ARG!
I tried to re-add the admin to the security group and it says it is already there ...
[PS] C:\Windows\system32>Add-RoleGroupMember "Mailbox Import Export Group" -Member "Administrator"
The recipient "Administrator" is already a member of the group "xxx.com/Microsoft Exchange Security Groups/Mailbox
Import Export Group".
+ CategoryInfo : InvalidData: (Administrator:SecurityPrincipalIdParameter) [Add-RoleGroupMember], MemberA
lreadyExistsException
+ FullyQualifiedErrorId : 473E65FA,Microsoft.Exchange.Management.RbacTasks.AddRoleGroupMemberI've closed and reopened EMS ... as well as rebooting the server :)
Nothing seems to get around this ... I'm sure it is something silly but perhaps someone has an idea for me.
Thanks - Clay
I have exactly the same issue as you. Done everything you have done.
Did you find a solution to this?
Wednesday, December 28, 2011 8:45 PM
How do you add the command if it's not in the list?
Thursday, September 25, 2014 2:29 PM
I had the same issue, solved by running Exchange Management Shell as an administrator!