Client Server Pre-Requisite Overview
Before any client installations can take place you should ensure that the appropriate environment is available and that you attend to each of the following items. You should work through the pre-requisite checklist below to ensure that you achieve a successful installation or alternatively you can run the Client Server pre-checker which will do an automatic pre-install check.
System Requirements
- The minimum operating systems supported is: Windows server 2008 R2 64 bit.
- SQL Server 2008 (any edition).
- Microsoft .NET framework 3.5 is a necessary requirement and must be installed. This is required even if you have .NET framework 4 and above installed already.
- The server that will be used for the Conductor4SQL Client server must have network connectivity, to communicate with the Central Server.
- The user performing the installation must be in the sys-admin user role in SQL Server.
Networking
For example, if your central server is 10.0.0.100 and the client server is 10.0.0.101, then configure your firewall to allow the client server to connect to tcp://10.0.0.100:4321 and the central server to connect to tcp://10.0.0.101:4321.
SQL Server access from the Central server to the client server is also required. If you're using a default SQL instance, you'll need to open port 1433 (tcp://10.0.0.101:1433 in our example) and allow traffic from the central server.
If you're using a named SQL instance, you'll need to open the SQL Browser port (UDP port 1434 to udp://10.0.0.101:1434) and either explicitly configure the SQL Server to use a single port or open the entire dynamic port range (49152 - 65535) in your firewall configuration.
Authentication
- Mixed-Mode authentication must be enabled in Microsoft SQL Server (if you have configured Conductor4SQL to use SQL Authentication)
- A username with sys-admin role is required
SQL Server services
If you wish to use Enterprise Data Sync with this client the "SQL Server Agent (MSSQLSERVER)" must be set to start automatically