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

Section 5. Requirements for Both Directory Sync Pro for Active Directory and Migrator Pro for Active Directory

4.1 Migrator Pro for Active Directory Basic Installation Requirements

The Migrator Pro for Active Directory suite consists of Directory Sync Pro and Migrator Pro for Active Directory software packages. Both packages will require access to Microsoft SQL Server.

Single Server Installation Requirements

If you are planning to have a long-term co-existence (1 year+), we recommend using the following formula to determine if you should use a full edition of SQL Server with our products. This formula assumes High / Verbose logging turned on for all profiles = worst case scenario.

Formula: (Expected months of co-existence x Users) x Profiles = N

If calculated N >= 12000 then we recommend full edition of SQL Server.

• Low example: 3 months x 300 users x 1 profile = 900

• Medium example: 6 months x 1000 users x 2 profiles = 12000

• High example: 12 months x 3000 users x 5 profiles = 180,000

• Extreme example: 14 months x 6000 users x 7 profiles = 588,000

Multi-Server Installation Requirements

Migrator Pro for Active Directory is scalable and supports segregating components and can be installed in a multi-server configuration to support larger or complex environments.

If required in larger installations, remote SQL Servers may be used for the primary database and the logging database. Additionally, the primary database and the logging database can be segregated onto separate SQL Server instances.

Each of the following roles/functions may be separated onto different servers as required in advanced configurations:

• Directory Sync Pro for Active Directory/Migrator Pro for Active Directory Administrative Web Interface

• Migrator Pro for Active Directory Web Service

• Directory Sync Pro for Active Directory Databases

  When installed independently, the components require the following resources:

Report Server Requirements

4.2 Workstation and Member Server System Requirements

4.3 Admin Agent Device Requirements

4.4 Networking Requirements

Domain Controller Access

For most scenarios, Migrator Pro for Active Directory requires access to at least one read/write domain controller in each source and target Active Directory domain. For fault tolerance, at least two domain controllers in each source and target domain is recommended.

If SID History will be synchronized, any domain controller listed in the Target DCs tab within a Directory Sync Pro for Active Directory profile will require access to the domain controller holding the PDC Emulator Active Directory FSMO role in the source. Keep in mind that even if the domain controller holding the PDC Emulator Active Directory FSMO role is not listed in the Source DCs tab, any SID History migration attempts will require a DC in the target to communicate with the PDC Emulator domain controller. For this reason, it is a best practice to ensure that all domain controllers specified on the Target DCs screen within a Directory Sync Pro for Active Directory profile have the appropriate networks access to communicate with the source domain controller holding the PDC Emulator Active Directory FSMO role before a SID History migration is attempted.

In limited scenarios, it is possible that Migrator Pro for Active Directory will not be responsible for creating or updating any accounts in the source or the target domains. In this scenario, Migrator Pro for Active Directory can be configured to communicate with Read Only Domain Controllers (RODCs).

Network/Firewall Requirements

Migrator Pro for Active Directory requires the following network ports to enable full functionality:

The following ports need to be opened between workstations/servers and writable domain controllers for a successful domain join operation:

4.5 SSL Certificate Requirements

Migrator Pro for Active Directory does not require HTTPS (HTTP with SSL), and can operate using HTTP. However, it is strongly recommended to implement Migrator Pro for Active Directory using HTTPS to secure communications between the devices to be migrated and the Migrator Pro for Active Directory Server. In order to activate HTTPS on the IIS component in Windows, the Migrator Pro for Active Directory system will require that a SSL certificate is present.

An SSL Certificate is not provided as part of the installation. For the most secure installation, purchasing an SSL Certificate from a Windows supported 3rd party provider is recommended.

In scenarios where this is not possible, self-signed SSL Certificate can be generated in Windows following these directions: https://technet.microsoft.com/en-us/library/cc753127(v=ws.10).aspx

If using a self-signed certificate, it should be noted that Migrator Pro for Active Directory’s agent component would utilize the operating system’s certificate trust list. Due to the security nature of Active Directory migrations, there is no method of implementing an override and forcing the agent to use an untrusted certificate. If a self-signed certificate is used, that certificate will need to be added to the trusted root certificate list for all computer objects to be migrated. This can be accomplished via group policy: https://technet.microsoft.com/en-us/library/cc738131(v=ws.10).aspx

4.6 Service Account Requirements

Migrator Pro for Active Directory requires the following user account permissions and privileges to support Active Directory migrations:

• One service account with read/write access to all organizational units (OUs) containing user, group, and computer objects in the source Active Directory to be migrated to the target environment.

• One service account with administrative rights on the target domain(s)

  • If administrative rights cannot be granted, the service account requires the following rights:

    • The ability to create and modify user objects in the desired OUs in the target Active Directory environment.

    • Read Permissions to the configuration container in Active Directory

    • User credentials with the delegated migrateSIDHistory extended right.

• A service account in each source and target domain with the ability to modify computer objects and add computers to the domain.

4.7 SQL Server Reporting Services (SSRS) Account Requirements

Migrator Pro for Active Directory's Reporting feature requires credentials in the following places:

• Content credential: Credential for accessing the report server content.

  You must set the securities in two different places in the SSRS ‘Report Manager’ web interface (http://<servername>/Reports) to connect to the report server and upload reports from the installation program.

  

  In the Site Settings, you MUST enable the ‘System Administrator’ role during installation. After installation is complete, you may change this user’s role to ‘System User’ if desired.

  

In the Folder Settings, you must add the same user with (at least) ‘Browser’ permission.

• Data Source Credential: The Data Source is used to access queries in the ADM database. These credentials and roles are set in the SQL server with SSMS

  The user must have public, db_reader, and db_executor roles on the ADM database.

  

The user must have the public role on the report server and report server temp databases.

4.8 DNS SRV Record Requirement

In each source domain, a SRV DNS record must be created to enable autodiscover for Migrator Pro for Active Directory agents.

• To enable autodiscover when HTTPS is desired

  • Record Name: _btadm._https.SourceDomainName.Local

  • Weight and Priority: 0

  • Port Number: 443

• To enable autodiscover when HTTP is desired

  • Record Name: _btadm._http.SourceDomainName.Local

  • Weight and Priority: 0

  • Port Number: 80

4.9 Offline Domain Join (ODJ) Requirements

In order to successfully facilitate the new Cached Credentials job (which supports the Offline Domain Join feature) a one-way external trust must be configured from the source domain to the target domain.

The devices that the ODJ process is being run on must have network connectivity to BOTH the source and target environments at the same time in order to have the Cached Credentials function work properly.

Offline domain join files must be created prior to running the Offline Domain Join process. A full explanation of Microsoft’s Djoin.exe utility and how to create these files can be found here:

https://technet.microsoft.com/en-us/library/offline-domain-join-djoin-step-by-step%28v=ws.10%29.aspx 

Section 5. Requirements for Both Directory Sync Pro for Active Directory and Migrator Pro for Active Directory

5.1 Browser Requirements

Directory Sync Pro for Active Directory uses a browser-based user interface. We recommend using Edge, Chrome, or Firefox.

5.2 SID History and Password Synchronization Requirements

SID History Synchronization Requirements

Microsoft requires an administrative account in the source domain.

In order to support synchronization of SID History from the source to the target domains, Windows requires that a specific domain local group exists and that account auditing is enabled.

The source and target domains must not have the same NETBIOS name to allow the required trust between the two environments.

Communication between a Source PDC and the configured Target GC is required for SID History Migration to successfully complete. Please note, there are additional ports that must be open between the Source PDC and the configured Target GC as defined in Section 3. Directory Sync Pro for Active Directory Advanced Network Requirement’s (Directory Sync Pro for Active Directory Profile with SID History Synchronization selected) of this document.

Preparing the Source and Target Domains

To prepare each source and target domain for SID History Synchronization, the following configuration steps must be completed:

• In the source domain, create a local group called SourceDomain$$$, where SourceDomain is the NetBIOS name of your source domain. For example, if your domain's NetBIOS name is ADM, you must create a domain local group named ADM$$$.

• Enable TCP/IP client support on the source domain PDC emulator:

  1. On the domain controller in the source domain that holds the PDC emulator operations master (also known as flexible single master operations or FSMO) role, click Start, and then click Run.

  2. In Open, type regedit, and then click OK.

  3. In Registry Editor, navigate to the following registry subkey:

     HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA

  4. Modify the registry entry TcpipClientSupport, of data type REG_DWORD, by setting the value to 1.

  5. Close Registry Editor, and then restart the computer.

• Enable auditing in the target domain:

  1. Log on as an administrator to any domain controller in the target domain.

  2. Click Start, point to All Programs, point to Administrative Tools, and then click Group Policy Management.

  3. Navigate to the following node: Forest | Domains | Domain Name | Domain Controllers | Default Domain Controllers Policy

  4. Right-click Default Domain Controllers Policy and click Edit.

  5. In Group Policy Management Editor, in the console tree, navigate to the following node: Computer Configuration | Policies | Windows Settings | Security Settings | Local Policies | Audit Policy

  6. In the details pane, right-click Audit account management, and then click Properties.

  7. Click Define these policy settings, and then click Success and Failure.

  8. Click Apply, and then click OK.

  9. In the details pane, right-click Audit directory service access and then click Properties.

  10. Click Define these policy settings and then click Success.

  11. Click Apply, and then click OK.

  12. If the changes need to be immediately reflected on the domain controller, open an elevated command prompt and type gpupdate /force.

  13. Repeat the above steps in the source domain.

Validate Cross-Domain Verification

In order to receive the maximum benefit a trust should be in place. When a trust is present, it is necessary to ensure that the trust is properly configured to permit cross-domain verification. To do so, first identify if the trust between the source and target domain is an external trust or a forest trust. Next, following commands must be run from an administrative command prompt:

If the trust between the source and target is an external trust:

• From the source domain:

  • Netdom trust SourceDomain /domain: TargetDomain /quarantine:No /user: domainadministratorAcct /password: domainadminpwd

• From the target domain:

  • Netdom trust TargetDomain /domain: SourceDomain /quarantine:No /user: domainadministratorAcct /password: domainadminpwd

If the trust between the source and target is a forest trust:

• From the source domain:

  • Netdom trust SourceDomain /domain: TargetDomain /enablesIDHistory:Yes /user: domainadministratorAcct /password: domainadminpwd

• From the target domain:

  • Netdom trust TargetDomain /domain: SourceDomain /enablesIDHistory:Yes /user: domainadministratorAcct /password: domainadminpwd

Domain Controller Access

If SID History will be synchronized, any Domain Controller listed in the Target DCs tab within a Directory Sync Pro for Active Directory profile will require access to the Domain Controller holding the PDC Emulator Active Directory FSMO role in the source. Keep in mind that even if the Domain Controller holding the PDC Emulator Active Directory FSMO role is not listed in the Source DCs tab, any SID History migration attempts will require a DC in the target to communicate with the PDC Emulator domain controller. For this reason, it is a best practice to ensure that all Domain Controllers specified in the Target DCs tab within a Directory Sync Pro for Active Directory profile has the appropriate networks access to communicate with the source Domain Controller holding the PDC Emulator Active Directory FSMO role before a SID History migration is attempted.

Password Synchronization Requirements

The domain controller with the PDC Emulator FSMO role must not be configured to run LSASS as a protected service or the password sync will fail with an access denied error.

5.3 Password Requirements

Directory Sync Pro for Active Directory and Migrator Pro for Active Directory do not validate the password policies present within your domains. Verify that the password entered as the Default Password complies with the password policy of your target environment. Objects will fail to be created if the password violates that policy.