System Requirements

IDSync's contacts connector consists of three components:

  1. The IDSync Management Studio - The IDSync Management Studio is typically installed on a server machine at the PSA's customer site. This interface provides screens for all of the configuration of the IDSync system and provides a means to install and monitor the services which are necessary for cyclical communications between active directory and the PSA system. 
  2. The IDSync Agent Service - The IDSync Agent Service is installed on each non-read only domain controller in a PSA's customer's active directory.  This component captures password information from Active Directory and makes that information available for the purposes of synchronization of passwords with the PSA's customer portal.
  3. The IDSync MMC Components - The IDSync MMC Components can be installed on any machine running the Active Directory Users and Computers snap-in in the PSA's customer's active directory.  This component adds IDSync specific tabs to the Active Directory Users and Computers screens for the purpose of configuring and provisioning contacts within the PSA system.

** All of the machines on which the IDSync Components are installed will require connectivity to the active directory domain for the Windows Network and to a Microsoft SQL database server. If Microsoft SQL is not available at the location, IDSync can (optionally) install Microsoft SQL Express.


User Credentials & System Information Required for Installation

  1. Domain Administrator Credentials
  2. SQL Database Credentials (for existing SQL Server only)
    1. You will need to create credentials if you are installing SQL Express (the Instance must be configured to use Mixed Mode Authentication, because an username and password combination is required).
    2. Initially, the SQL User needs to have sysadmin rights in order to create the database. After the database has been created, the SQL User needs the dbowner role to operate without problems (the sysadmin role may be then removed from its security profile)
  3. Autotask Credentials
    1. Autotask site API URL
    2. Autotask Company ID
    3. Autotask Admin ID
    4. Autotask Admin Password

IDSync System Requirements

  1. IDSync Management Studio Machine:
    1. Windows Server 2008 (all versions) or above
    2. 32 or 64-bit Supported
    3. .NET Framework 4.6 (or above) *
  2. Microsoft SQL Server
    1. Can use an existing Microsoft SQL Server
    2. Can (optionally) install Microsoft SQL Express
    3. SQL Server Instance must be configured for US English Code: 1033/en_US
    4. TCP-IP and Named Pipes protocols must be enabled on the server
    5. SQL Server and SQL Server Browser services must be Running

    6. Mixed-mode authentication must be enabled on the SQL Server

    7. Microsoft SQL Server Management Studio is needed for support / troubleshooting purposes.

    8. If Enabled, the local firewall on the SQL Server must permit traffic on the ports that are in use by both the SQL Server Service and the SQL Browser service.

  3. IDSync Agent Service 
    1. Windows Server 2008 (all versions) or above
    2. 32 or 64-bit Supported
    3. .NET Framework 4.6 (or above)*
    4. Microsoft SQL Native Client*

* Will be automatically installed by IDSync™ if not available on the machine 

Security Requirements

    1. Domain Administrator access privileges
    2. Database Administrator account
    3. SQL Service account for IDSync
      1. Account that IDSync will utilize to connect to the database



Autotask enforcing use of TLS 1.2

In order to maintain compatibility with Autotask standards on the TLS protocol usage, please make sure the next registry entries exist in every server that communicates with the Autotask API:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SchUseStrongCrypto
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319\SchUseStrongCrypto


You can find more information on this how-to guide: Create Registry entries to Enable TLS 1.2