Directory Sync Pro for Notes 20.13.02 - Requirements and Installation Guide

Section 4. Directory Sync Pro Requirements

4.1 Directory Sync Pro Basic Installation Requirements

The Directory Sync Pro suite consists of the console and the Web service, and Directory Sync Pro software packages. Both packages will require access to Microsoft SQL Server. In most environments, all components of Directory Sync Pro will be installed on the Domino coex server and the Windows coex 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

4.1 Directory Sync Pro Basic Installation Requirements

The Directory Sync Pro suite consists of the console and the Web service, and Directory Sync Pro software packages. Both packages will require access to Microsoft SQL Server. In most environments, all components of Directory Sync Pro will be installed on the Domino coex server and the Windows coex 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

4.2 Networking Requirements

Domain Controller Access

For most scenarios, Directory Sync Pro 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, Binary Tree recommends at least two domain controllers in each source and target domain.

Network/Firewall Requirements

Directory Sync Pro requires the following network ports to enable full functionality:

4.3 Service Account Requirements

Directory Sync Pro requires the following user account permissions and privileges: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