|
Source |
Target |
Ports |
Protocol |
|---|---|---|---|
|
Directory Sync Pro |
SQL Server holding the primary database |
1433 |
TCP & UDP |
|
Directory Sync Pro |
SQL Server holding the logging database |
1433 |
TCP & UDP |
|
Source |
Target |
Ports |
Protocol |
|---|---|---|---|
|
Directory Sync Pro |
SQL Server holding the primary database |
1433 |
TCP & UDP |
|
Directory Sync Pro |
SQL Server holding the logging database |
1433 |
TCP & UDP |
|
Source |
Target |
Ports |
Protocol |
|---|---|---|---|
|
Directory Sync Pro |
Source Domain controllers |
88, 389, 445*, 3268 |
TCP (all) UDP (88, 389) |
|
Directory Sync Pro |
Target Domain controllers |
88, 389, 445, 3268 |
TCP (all) UDP (88, 389) |
* Port 445 only needs to be open to the Source Domain Controller during Directory Sync Pro Profile creation
|
Source |
Target |
Ports |
Protocol |
|---|---|---|---|
|
Directory Sync Pro |
Source Domain controllers |
88, 389, 445*, 3268 |
TCP (all) UDP (88, 389) |
|
Directory Sync Pro |
Target Domain controllers |
88, 139, 389, 445, 3268 |
TCP (all) UDP (88, 389) |
* Port 445 only needs to be open to the Source Domain Controller during Directory Sync Pro Profile creation
|
Source |
Target |
Ports |
Protocol |
|---|---|---|---|
|
Directory Sync Pro |
Source or Target Domain controllers |
88, 139, 389, 445, 3268 |
TCP (all) UDP (88, 389) |
|
Source |
Target |
Ports |
Protocol |
|---|---|---|---|
|
Directory Sync Pro |
Source or Target Domain controllers |
88, 135, 137, 139, 389, 445, 3268 and 49152-65535 |
TCP (all) UDP (88, 389) |
|
Directory Sync Pro |
Source or Target Domain controllers |
88, 135, 137, 139, 389, 445, 3268 and 1024-5000 |
TCP (all) UDP (88, 389) |
|
Target GC |
Source PDC |
135, 389, 445, 1027 |
TCP (all) |
The Migrator Pro suite consists of Directory Sync Pro and Migrator Pro software packages. Both packages will require access to Microsoft SQL Server.
Single Server Installation Requirements
|
Supported Operating Systems |
|
|
SQL Server Requirements |
|
|
Minimum Hardware Requirements |
|
|
Additional Components |
|
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 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/Migrator Pro Administrative Web Interface
Migrator Pro Web Service
Directory Sync Pro Databases
When installed independently, the components require the following resources:
|
Supported Operating Systems |
|
|
Migrator Pro Split Role Minimum Hardware Requirements |
|
|
Directory Sync Pro Hardware Requirements |
|
|
SQL Server |
|
|
Additional Components |
|
Report Server Requirements
|
SQL Server Requirements |
|