This article demonstrates how to create a single MSI OSCE client installation package for OSCE clients' fresh installations and upgrades, then allow users to register these OSCE clients to different specific OSCE servers.
To create and configure a single MSI OSCE client installation package:
- Do either of the following:
- For OSCE 10.6 Service Pack (SP) 3, apply Hot Fix Build 5415 on the server machine where the MSI package will be created.
- For OSCE 11.0 and later, the feature has been merged, so there is no need to apply the hot fix.
- Open the Ofcscan.ini file in the \PCCSRV\ folder of the OSCE server A.
- Add the following key under "INI_CLIENT_SETUP_SECTION" and set its value to "1":
ForceRefresh=1 will make the OSCE client register to the new server from which the client package was created.
BypassServerChecking=1 enables the client to launch a package created from another OSCE server.
- Register the OSCE clients to different specific servers by adding the following keys under "INI_CLIENT_SETUP_SECTION" and assigning the correct values:
AssignedServerNumber= <total number of Assigned Servers>
- Save the changes and close Ofcscan.ini.
- Create the MSI installation package.
If you are upgrading clients using the MSI package and the upgraded clients need to be moved to a specified server, manually add the following registry key. Otherwise, proceed to the next step.
- Install or upgrade the OSCE clients using the MSI package.
- The "AssignedServerNumber" key accepts any integer number up to 1000.
- The "AssignedServerX" key allows users to specify a certain IP range of clients that should be registered to the assigned server.
- If the domain is not specified, the client will be registered to the default domain of the server.
- Make sure to put ''[ServerN][:Port][\Domain1\Domain2]'' on the same row with '[ClientIPRangeStart],[ClientIPRangeEnd]'.
- "ServerN" can be assigned an IP address or a hostname of the server.
- If you use the IP address of "ServerN", make sure you can ping the IP address of ''ServerN'' from the OSCE client machine.
- If you use the hostname of "ServerN", make sure you can ping the hostname of ''ServerN'' from the OSCE client machine.
- If the OSCE server A is the 11.0 version or later, Server1, Server2…Server N are also v11.0 or a later version, so make sure they use the same certificate during server installation (OfcNTCer.dat). If not, the client will fail to communicate with the new server.