Certifications
- Migrator Pro for Active Directory has been certified to work with Active Directory Domain and Forest Functional Levels 2003, 2008, 2008 R2, 2012, and 2016.
Migrator Pro for Active Directory Basic Installation Requirements
The Migrator Pro for Active Directory suite consists of Migrator Pro for Active Directory, which includes both the console and the Web service, and Directory Sync Pro for Active Directory software packages. Both packages will require access to Microsoft SQL Server. In most environments, all of these components will be installed on the same server.
Single Server Installation Requirements
|
Supported Operating Systems |
|
|
SQL Server Requirements |
|
|
Minimum Hardware Requirements |
|
|
Additional Components |
|
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:
- Migrator Pro for Active Directory Server Web Service
- Migrator Pro for Active Directory Administrator Console
- Directory Sync Pro for Active Directory Software
- Directory Sync Pro for Active Directory Database
- Directory Sync Pro for Active Directory Logging Database
When installed independently, the components require the following resources:
| Supported Operating Systems |
|
| Migrator Pro for Active Directory Split Role Minimum Hardware Requirements |
|
| Directory Sync Pro for Active Directory Hardware Requirements |
|
| SQL Server |
|
| Additional Components |
|
Report Server Requirements
|
SQL Server Requirements |
|
Workstation and Member Server System Requirements
| Supported Operating Systems |
|
| PowerShell Requirements |
|
| .NET Framework Requirements |
|
Admin Agent Computer Requirements
| Operating System Requirements |
|
| Supported Operating Systems |
|
| Additional Requirements |
|
Networking Requirements
Domain Controller Access
For most scenarios, Migrator Pro for Active Directory requires access to at least one read/write domain controller running Windows 2003 SP2 or newer 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 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.
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:
| Source | Target | Port/Protocol |
|---|---|---|
| Workstations and Member Servers | Migrator Pro for Active Directory Server |
443 (TCP) or 80 (TCP) |
| Migrator Pro for Active Directory Server | Source and Target Domain Controllers running Windows 2003 |
135, 137, 389, 445, 1024-5000 (TCP) 389 (UDP) |
| Migrator Pro for Active Directory Migrator Server | Source and Target Domain Controllers running Windows 2008 or newer |
135, 137, 389, 445, 49152-65535 (TCP) 389 (UDP) |
| Target domain controllers listed in the Target DCs tab | Domain controller in the source environment holding the PDC Emulator Active Directory FSMO role |
135, 137, 139, 389, 445, 3268 and 49152-65535 (TCP) 389 (UDP) |
The following ports need to be opened between workstations/servers and writable domain controllers for a successful domain join operation:
| Type of Traffic | Protocol and Port |
|---|---|
|
DNS |
TCP/UDP 53 |
| Kerberos |
TCP/UDP 88 |
| EPM | TCP 135 |
| NetLogon, NetBIOS Name Resolution | UDP 137 |
| DFSN, NetLogon, NetBIOS Datagram Service | UDP 138 |
| DFSN, NetBIOS Session Service, NetLogon | TCP 139 |
| C-LDAP | TCP/UDP 389 |
| DFS, LsaRpc, NbtSS, NetLogonR, SamR, SMB, SrvSvc | TCP/UDP 445 |
| LDAP SSL | TCP 636 |
| Random RPC | TCP 1024-5000 |
| GC | TCP 3268 |
| GC | TCP 3269 |
| DFS-R | TCP 5722 |
| Random RPC | TCP 49152-65535 |
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 computers to be migrated and the AD Migrator 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 as part of the installation is not provided. For the most secure installation, purchasing a 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 the 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
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.
- If administrative rights cannot be granted, the service account requires the following rights:
- A service account in each source and target domain with the ability to modify computer objects and add computers to the domain.
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.
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
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.
SID History intra-forest migration is supported (with SMART AD Migrator 9.0.2.0) with the use of an out-of-the-box script available from Support.
The source and target domains must not have the same NETBIOS name to allow the required trust between the two environments.
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$$$.
SID History synchronization will fail if members are added to this local group. - Enable TCP/IP client support on the source domain PDC emulator:
- 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.
- In Open, type regedit, and then click OK.
-
In Registry Editor, navigate to the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA
- Modify the registry entry TcpipClientSupport, of data type REG_DWORD, by setting the value to 1.
- Close Registry Editor, and then restart the computer.
- Enable auditing in the target domain:
- Log on as an administrator to any domain controller in the target domain.
- Click Start, point to All Programs, point to Administrative Tools, and then click Group Policy Management.
- Navigate to the following node: Forest | Domains | Domain Name | Domain Controllers | Default Domain Controllers Policy
- Right-click Default Domain Controllers Policy and click Edit.
- 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
- In the details pane, right-click Audit account management, and then click Properties.
- Click Define these policy settings, and then click Success and Failure.
- Click Apply, and then click OK.
- In the details pane, right-click Audit directory service access and then click Properties.
- Click Define these policy settings and then click Success.
- Click Apply, and then click OK.
- If the changes need to be immediately reflected on the domain controller, open an elevated command prompt and type gpupdate /force.
- Repeat the above steps in the source domain.
It may also be necessary to reboot the domain controller to have auditing take effect.
Even with group policy applied on the default domain controller for the domain audit, the server audit setting on the primary domain controller (PDC) may not be enabled. Please confirm this setting is enabled for the local security policy on the PDC server. If not enabled, use the local security policy to enable this setting.
Advanced security auditing can be configured instead of standard auditing if additional granularity is required.
Validate Cross-Domain Verification
A trust is not required to synchronize SID History in Migrator Pro for Active Directory. However, 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 /usero: domainadministratorAcct /passwordo: domainadminpwd
- From the target domain:
- Netdom trust TargetDomain /domain: SourceDomain /quarantine:No /usero: domainadministratorAcct /passwordo: domainadminpwd
If the trust between the source and target is a forest trust:
- From the source domain:
- Netdom trust SourceDomain /domain: TargetDomain /enablesIDHistory:Yes /usero: domainadministratorAcct /passwordo: domainadminpwd
- From the target domain:
- Netdom trust TargetDomain /domain: SourceDomain /enablesIDHistory:Yes /usero: domainadministratorAcct /passwordo: domainadminpwd
Password Requirements
Directory Sync Pro for Active Directory does 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.
Directory Sync Pro for Active Directory Requirement for Synchronize Passwords
If planning to use the Password Copy functionality of Directory Sync Pro for Active Directory, PsExec must be installed in the Directory Sync Pro for Active Directory program directory (C:\Program Files\Binary Tree\DirSync). Ignore the PSExec Installation Guide concerning the proper installation location. PsExec is available at: https://technet.microsoft.com/en-us/sysinternals/bb897553
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 computers 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.
Be aware that Microsoft's Djoin.exe utility only supports the Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016 operating systems. 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
Related Topics