Uncategorized

The term ‘New-Mailbox’ is not recognized as the name of a cmdlet, function, script file, or operable program.

When you want to create a new user mailbox, and selecting a new user you receive the following error:

The term ‘New-Mailbox’ is not recognized as the name of a cmdlet, 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.

while no problem when selecting Existing User.

The reason for that is the Active Directory split permissions as when you select new user (i.e. New-Mailbox) you need to create an object in the AD while you don’t have permissions for that so the operation fail. while in the existing user case (i.e. Enable-Mailbox) the user object is already created and the additional work is exchange related.

to solve this:

1- you can let your AD team to previously create the user object then you can mail-enable it.

2- you can switch from AD split permissions to shared permissions ( reference: http://technet.microsoft.com/en-us/library/dd638146.aspx).

  1. From a Windows command shell, run the following command from the Exchange 2013 installation media to disable Active Directory split permissions.
    setup.exe /PrepareAD /ActiveDirectorySplitPermissions:false
  2. From the Exchange Management Shell, run the following commands to add regular role assignments between the Mail Recipient Creation role and Security Group Creation and Management role and the Organization Management and Recipient Management role groups.
    New-ManagementRoleAssignment "Mail Recipient Creation_Organization Management" -Role "Mail Recipient Creation" -SecurityGroup "Organization Management"
    New-ManagementRoleAssignment "Security Group Creation and Membership_Org Management" -Role "Security Group Creation and Membership" -SecurityGroup "Organization Management"
    New-ManagementRoleAssignment "Mail Recipient Creation_Recipient Management" -Role "Mail Recipient Creation" -SecurityGroup "Recipient Management"
  3. Restart the Exchange 2013 servers in your organization.
    Note:
    If you have Exchange 2010 servers in your organization, you also need to restart those servers.
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s