This article will help you migrate your NetSupport Manager Gateway (NetSupport Connectivity Server) to a new server machine.
Installing the NetSupport Manager Gateway on the new server
First, you need to install the Gateway component on the new server machine. To do this, create a folder on the new server and copy the Setup.exe installer and corresponding NSM.lic licence file into it. Run the installation and follow the instructions. The Gateway can be installed via a ‘Custom’ installation. The licence details will be read automatically.
Migrate the server configuration to the new server
In order to carry over your old server’s existing configuration to the new server, it is possible to export the registry key from your old server and then import this onto the new server.
The configuration of the Gateway Server is stored in HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Productive Computer Insight\Gateway.
If you export this registry key to a *.reg file, you will then be able to import this onto the new server once the Gateway has been installed and your configuration will be carried over.
Note: A restart of the Gateway32 service will be required once this registry has been imported.
Connecting the NetSupport Manager Control and Client machines to the new Gateway
If you have configured the new server to use the same IP address or hostname as the old server, the Client and Control machines will start connecting to the new Gateway Server automatically once it is available.
If the new server has a different IP address or hostname, you will need to reconfigure your Client and Control machines to connect to the Gateway using the new address.
If your Client and Control machines are domain-joined, the easiest way to push out the updated configuration is via Group Policy. The following technical article explains how you can configure the Gateway for your Client and Control machines via GPO: Configuring the NetSupport Connectivity Server details for NetSupport Manager Clients and Controls by Group Policy (GPO)
If your machines are not domain-joined, please see the following sections for steps on updating the configuration on your Client and Control machines.
Configuring the Client machines
To configure the Client machines, you will need to push out a modified Client32u.ini configuration file to your Client machines which contain the updated server IP address or hostname of the server. All other settings can be left as they are. In order to change the configurations for the Clients, please see the steps below:
- Open the NetSupport Manager Configurator by navigating to Start > NetSupport Manager on an existing Client machine.
- Select Advanced, and then double click Master Profile.
- In the Connectivity section, select HTTP.
- Modify the Gateway Address field to match the new details of your NetSupport Manager Gateway.
- Click OK and then click Save to apply the settings to the Client.
The steps above will modify the Client32u.ini file that is located in C:\Program Files (x86)\NetSupport\NetSupport Manager.
Once you have changed this setting on one of your Client machines and checked that the configuration successfully connects to the Gateway, you will then be able to take a copy of the updated Client32u.ini file and push it out to the rest of your Clients. This file will need sending to C:\Program Files (x86)\NetSupport\NetSupport Manager.
Configuring the Control machines
To configure the Control machines, you can use the configuration interface within the Control application.
- In the Control Console, select Internet Gateways from the left-hand side menu.
- Right click your Gateway from the list and select Properties.
- Modify the Address field to match the new details of your NetSupport Manager Gateway.
- Click OK to apply the changes.
If you have multiple Control machines that you need to update, you can export the Control configuration to a *.reg file and then import this onto another Control machine.
The Control configuration is stored in HKEY_CURRENT_USER\SOFTWARE\NetSupport Ltd\PCICTL\ConfigList\Standard
After following the steps above, the NetSupport Manager Gateway should now be running on your new server machine and your Control and Client machines will be connecting to this.