Directory Sync Pro for Active Directory 20.11 - Requirements and Installation Guide

9.1 Installing the Migrator Pro for Active Directory Agent on Devices

The Migrator Pro for Active Directory Agent is a key component of Active Directory migration. The agent contacts the Migrator Pro for Active Directory server at regular intervals, called polling, looking for jobs and tasks to perform.

Refer to the Requirements to verify all workstations and servers meet the requirements for agent installation.

Agent Installation

The agent can be installed using a GPO (Group Policy Object) or manually.

To install the agent with a GPO:

1. Right-click on the Migrator Pro for Active Directory Agent Installer MSI, point to Share with, and click on specific people.

2. Add a security group. The "authenticated users" group already includes all computers and is a good group to use. The group you add must have the shared Read permission and NTFS permission.

3. Click Share.

4. Click Done.

5. From the Start menu, point to Administrative Tools and click on Group Policy Management.

6. Right-click on the domain or OU you will be migrating and click on Create a GPO in this domain, and link it here.

7. In the New GPO dialog box, enter a Name for the GPO and click OK.

8. Click on the new GPO and click OK.

9. Right-click on the GPO and select Edit.

10. Open Computer Configuration > Policies > Software Settings and right-click on Software Installation and then point to New and click on Package.

11. In the File Name field, enter the UNC path to the MSI file and click Open.

12. Select the Active Directory Pro Agent and click Open.

13. In the Deploy Software window, select the Assigned deployment method and click OK.

To verify the GPO:

1. Log on to a workstation within the scope of the GPO using administrator credentials.

2. From a command prompt on the workstation, run gpresult -r

3. The Computer Settings section will display the applied group policy.

To manually install the agent:

1. Copy the Active Directory Pro Agent Installer MSI file to each computer.

2. Double-click the file to open the installer.

3. On the Welcome screen, click Next.

   

4. On the Destination Folder screen, click Next.

   

5. On the Enter Server URL screen, enter the FQDN of the server running the Migrator Pro for Active Directory service and click Next.

   

6. On the Ready to Install the Program screen, click Install.

   

7. When the install completes, click Finish.

   

   Refer to the Troubleshooting section to resolve common agent install issues.

Creating SRV Records

The Migrator Pro for Active Directory Agent uses DNS to "autodiscover" the Migrator Pro for Active Directory server. An SRV (service location) record must be created in DNS to point the clients to the correct server or servers.

To create an SRV record using DNS Manager:

1. In the DNS Manager, right-click on the DNS server and click on Other New Records.

2. In the Resource Record Type dialog, select the Service Location (SRV) type and click Create Record.

3. In the New Resource Record dialog, enter "_btadm" in the Service field.

4. Enter the following information for HTTP or HTTPS:

• For HTTP:

  Protocol: _http

  Priority: 0

  Weight: 0

  Port Number: 80

  Host offering the service: the FQDN of server running the Migrator Pro for Active Directory service.

• For HTTPS:

  Protocol: _https

  Priority: 0

  Weight: 0

  Port Number: 443

  Host offering the service: the FQDN of server running the Migrator Pro for Active Directory service.

5. Click OK.

   Every client running the agent software must be able to resolve the DNS records.

   To verify the clients can resolve the SRV DNS records:

1. Open a command prompt on the client machine.

2. Run nslookup -q=srv _btadm._http.source.int where "http" is the protocol: http or https, and "source.int" is the name of the source domain.

Section 10. Troubleshooting

10.1 Migrator Pro for Active Directory Agent Installation Troubleshooting

• Problem: The device registers but does not get discovered (Discovery Status remains blank in the Migrator Pro for Active Directory console).

  Solution: Install PowerShell 2.0 or higher on the client. Operating systems earlier than Windows 7 do not natively include PowerShell.

• Problem: During manual installation, a "wizard interrupted" error appears.

  Solution: Install .NET 4.5.2 or higher on the client and run the installer again.

• Problem: After a successful manual install, an "Unable to register" error appears in the Event Viewer.

  Solution: Verify the path to the Migrator Pro for Active Directory server is correct and complete.

• Problem: After a successful manual install, an "Unable to auto-discover" error appears in the Event Viewer.

  Solution: The SRV records are missing, incorrect, or unreachable. Verify SRV records are set up properly.

Appendix A: Configuring Directory Sync Pro for Active Directory in a Non-English Active Directory Environment

Directory Sync Pro for Active Directory refers to several system groups by their English names, which will not function properly when deploying in environments where non-English Active Directory is deployed. To resolve this, the mapping of these systems group names can be configured to accommodate non-English language deployments.

There are five new .config file values, representing the five system groups used by Directory Sync Pro for Active Directory: All Users, All Groups, All Rooms, Default Global Address List, and Deleted Objects. To localize a value, edit BinaryTree.Dirsync.Exchange.exe.config on the Exchange server and add the colored text below (the existing configuration is shown below in black), replacing the value with the equivalent value in the appropriate language.

<configuration>

  <configSections>

  </configSections>

<!--

"ExchangeOrgCN" = The name of the Exchange Organization CN to use for the target AD.  This is only used if it cannot be automatically detected.

The names of the following AD objects can be localized.

         To use the localized versions, replace the string values belowe with the localized name.

         e.g. <add key="AllUsers" value="Tous les utilisateurs"/>

         e.g. <add key="DefaultGlobalAddressList" value="Liste d'adresses globale par défaut"/>

"ReferralChasingOption"

the available options for 'chase referrals' are:

         - None: Never chase the referred-to server. Setting this option prevents a client from contacting other servers in a referral process

         - Subordinate: Chase only subordinate referrals which are a subordinate naming context in a directory tree

         - External: Chase external referrals

         - All: Chase referrals of either the subordinate or external type

--> 

  <appSettings>

    <add key="ExchangeOrgCN" value="" />

    <add key="AllUsers" value="All Users" />

    <add key="AllContacts" value="All Contacts" />

    <add key="AllGroups" value="All Groups" />

    <add key="AllRooms" value="All Rooms" />

    <add key="DefaultGlobalAddressList" value="Default Global Address List" />

    <add key="DeletedObjects" value="Deleted Objects" />