This section applies only if you are migrating to a proprietary Exchange target. If you are migrating to a hosted Exchange, skip ahead to Account permissions for migration to Office 365.
To set AD container permissions in Exchange 2010 or later:
• |
Use PowerShell to assign the necessary permissions to the AD admin using the following cmdlet (where <UserAcct> is the admin’s SecurityPrincipalIdParameter): |
LDAP policy can be configured to accommodate more than 1000 OUs in Active Directory, by adjusting the max items returned by ADSI interface. See these Microsoft links for LDAP Policies. | |
get-mailboxdatabase | add-adpermission -user <username> -extendedrights receive-as
The migration admin account must be configured with application impersonation, by this PowerShell cmdlet (in one continuous line): New-ManagementRoleAssignment -Role "ApplicationImpersonation" –User <userid> | |
The SQL bulk import directory (specified in the SQL Server Configuration screen of Notes Migration Manager) must be accessible to all migration servers, and to the user that the SQL Server will run as. | |||||
Both Windows Authentication and SQL Authentication are supported.
NOTE: Once the NME40DB database is created and tables populated, the dbcreator server role assigned to either the Windows user or SQL user is no longer required. The db_owner role is sufficient and is automatically granted to the Windows or SQL user when NME40DB is created. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center