Configuring the NSPI Connection Limit
|
|
Important: This step must be performed only if you have any Windows Server 2008 or later domain controllers acting as Global Catalog. |
By default, the maximum number of simultaneous Name Service Provider Interface (NSPI) connections equals to 50 per user for Windows Server 2008 or later domain controllers. Therefore, to avoid possible issues related to exceeding that value, you may need to increase the NSPI connection limit on all Windows Server 2008 or later domain controllers acting as Global Catalog. The recommended limit value equals the number of agent instances working simultaneously multiplied by 5.
To change the default connection limit for a domain controller, take the following steps:
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS - Click the Parameters key.
- On the Edit menu, point to New, and then click DWORD Value.
- Type NSPI max sessions per user, and then press Enter.
- Double-click NSPI max sessions per user, type the appropriate maximum number of the NSPI connections, and then click OK.
-
Restart the computer or restart Active Directory Domain Services.
For additional information, see the following Microsoft Support articles:
- Error: "Trying to connect to Microsoft Exchange Server" results in MAPI_E_LOGON_FAILED
- NSPI connection to a Windows-based domain controller causes MAPI client applications to fail and returns a "MAPI_E_LOGON_FAILED" error message
Setting Exchange Autodiscover URL (Optional)
Migration Agent for Exchange uses the Exchange Autodiscover service to query certain properties of mailboxes being migrated. In order to submit queries to the Autodiscover service, MAgE needs to know its URL. In most cases, the agent automatically gets the Autodiscover URLs for both the source and target organizations. However, you may experience situations when automatically discovering the URL fails or returns the incorrect URL.
When the correct URL cannot be obtained, an error will be generated causing the synchronization job to fail. Errors in the log file with the following exceptions indicate problems with obtaining the proper Autodiscover URL:
- AutodiscoverLocalException: The Autodiscover service couldn't be located.
- ServiceRequestException: The request failed. The remote server returned an error: (401) Unauthorized.
- ServiceRemoteException: Invalid user: 'Joe.User@contoso.com'.
- AutodiscoverDeploymentIdMismatchException: The User Deployment ID returned from Autodiscover does not match the expected value.
If you encounter any of the above exceptions, you need to manually configure the Autodiscover URL for the source or target organizations (or both) . The Autodiscover URL can be configured using the Set-MMExOrganizationProperties cmdlet from the MMExPowerShell module. Below is an example how to use the cmdlet:
Set-MMExOrganizationProperties -FQDN source.contoso.com -AutodiscoverUrl https://autodiscover.source.contoso.com/autodiscover/autodiscover.svc
|
|
TIP: For information how to use the MMExPowerShell.psm1 module, see Configuring Migration Project Settings Using PowerShell. |
Setting Up Connection with the Target Exchange Organization Using SMTP Connectors
This section describes how to set up a connection with the target Exchange organization using SMTP connectors. On this step you may need to coordinate with the administrator of the target Exchange organization to set up the connection properly.
For more details, see the related topics:
- Setting up Source Exchange Organization for Internet Mail Flow between Source and Target Exchange Organizations
- Configuring Source DNS Server for Mail Forwarding
- Testing the SMTP Connectors (Optional)
Setting up Source Exchange Organization for Internet Mail Flow between Source and Target Exchange Organizations
You need to establish Internet mail flow between the source and the target Exchange organizations. For that, you need to create an Internet Send connector and Receive connector on an Exchange Mailbox server that can be directly reached through the Internet.
To establish mail flow to and from the Internet through a Mailbox server, follow these steps:
- Create a Send connector (to send email from source Exchange organization to the Internet) on the Mailbox server.
- Modify the default Receive connector for the source domain to accept anonymous e-mail from the Internet
- Add the e-mail domain used for redirection to the list of accepted domains.
Each step is explained in further detail in the related subtopics.