AJKBOC
asked on
The term 'New-MailboxExportRequest' is not recognized as the name of a cmdlet
From what I could gather, this is the process for exporting a mailbox to a pst file on Exchange 2010 SP1
Create a folder and add full access to the "Exchange Trusted Subsystem" Security Group
Give the Administrator the "Mailbox Import Export" role. New-ManagementRoleAssignme
Open Exchange Management Shell and run the following command to export the mailbox
New-MailboxExportRequest -Mailbox "myusername" -Filepath "\\mail\c$\Backup\myuserna
I realize that the commands were different before SP1 and I searched everywhere for the new ones.
My problem when I try the above export command, I get the below
[PS] C:\Windows\system32>New-Ma
\\mail\c$\Backup\myusernam
The term 'New-MailboxExportRequest'
function, script file, or operable program. 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-MailboxExportRequest <<<< -Mailbox "myusername" -Filepath "\\mail\c$\Backup
\myusername.pst"
+ CategoryInfo : ObjectNotFound: (New-MailboxExportRequest:
) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
[PS] C:\Windows\system32>
What I'm I doing wrong here?
Create a folder and add full access to the "Exchange Trusted Subsystem" Security Group
Give the Administrator the "Mailbox Import Export" role. New-ManagementRoleAssignme
Open Exchange Management Shell and run the following command to export the mailbox
New-MailboxExportRequest -Mailbox "myusername" -Filepath "\\mail\c$\Backup\myuserna
I realize that the commands were different before SP1 and I searched everywhere for the new ones.
My problem when I try the above export command, I get the below
[PS] C:\Windows\system32>New-Ma
\\mail\c$\Backup\myusernam
The term 'New-MailboxExportRequest'
function, script file, or operable program. 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-MailboxExportRequest <<<< -Mailbox "myusername" -Filepath "\\mail\c$\Backup
\myusername.pst"
+ CategoryInfo : ObjectNotFound: (New-MailboxExportRequest:
) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
[PS] C:\Windows\system32>
What I'm I doing wrong here?
Mohamed ElManakhly
you probably not login-ed as an exchange organization administrator . if you do try opening power shell , by right clicking on it and choose run as administrator
also you need to have the "Mailbox Import Export” management role assigned.
http://blogs.technet.com/b/samdrey/archive/2011/02/17/exchange-2010-rbac-issue-mailbox-import-export-gt-new-mailboximportrequest-and-other-management-role-entries-are-missing-not-available.aspx
http://blogs.technet.com/b/samdrey/archive/2011/02/17/exchange-2010-rbac-issue-mailbox-import-export-gt-new-mailboximportrequest-and-other-management-role-entries-are-missing-not-available.aspx
ASKER
I am logged in as the Administrator, and like I said in the original post, the "Mailbox Import Export" role has been assigned to the Administrator.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Mailbox import export is assigned to groups not users .
please note that the rule is not assigned by default to the organization management group.
from the Exchange management console , go to toolbox and open rbac user editor .. create a new group add administrator to it and assign the role "Mailbox import export " to it
please note that the rule is not assigned by default to the organization management group.
from the Exchange management console , go to toolbox and open rbac user editor .. create a new group add administrator to it and assign the role "Mailbox import export " to it
okay so assigning the role to administrator solved it ,
good luck
good luck
ASKER
No, closing and opening the Exchange Management Shell solved it.
Exactly the same as making ANY WINDOWS BASED AUTHENTICATION CHANGE. The user must log out and log in again. In you instance, log out of the management shell and back in again.
ASKER
Closing and opening the Exchange Management Shell solved it