< Back
You are here:
Print

In NetSupport Manager pre-v12.50, the default Client Configuration file was Client32.ini; this file stored the information using the ANSI format. From version 12.50, NetSupport Manager provides Unicode support and the NetSupport Client Configuration file was updated to store the information using the UTF8 format.

NetSupport Manager Clients running pre-v12.50 do not support the new format of the Client Configuration file. To ensure this file is not applied to them, from NetSupport Manager 12.50, the Client Configuration is saved to a Client32u.ini file.

The NetSupport Manager v12.50 installer, Client component, Client Configurator and Deploy tool have all been updated to use the new Client32u.ini file in preference to the old Client32.ini Configuration file.

In addition, when using the NetSupport Manager Client Configurator from version 12.50, this will automatically store any changes made to both the new and old Client Configuration file, allowing the Configuration files to be deployed from a 12.50 installation to a mixture of Client versions.

Client32.ini – Legacy code page-based content stored in ANSI format.
Client32u.ini – Unicode content stored in UTF8 format.

Note: If the Client32u.ini file is deployed to a version of NetSupport Manager that is running a version earlier then 12.50, the file will be ignored by the Client.

Below are details of which Client Configuration files will be used for installations, deployments and configuration changes when using NetSupport Manager 12.50.

New installations
When performing a new installation of NetSupport Manager 12.50, the Client Configuration files applied to the installation will be in the following order:

  1. Client32u.ini if located in the same folder as the installer.
  2. Client32.ini if located in the same folder as the installer (ignored if the Client32u.ini file is present).
  3. If no external Client Configuration file exists, a default configuration applies.

Upgraded installations
When performing an upgrade from a previous version of NetSupport Manager to the latest version, the Client Configuration files applied to the installation will be in the following order:

  1. Client32u.ini if located in the same folder as the installer.
  2. Client32.ini if located in the same folder as the installer (ignored if the Client32u.ini file is present).
  3. If no external Client Configuration file exists with the installer, then a Client32u.ini stored in the program directory before the upgrade will be used.
  4. Client32.ini file in the installed program folder before the upgrade will be used.

Deploying a package
When performing a deployment of a new version using the NetSupport Deploy tool, the Client Configuration files applied to the installation will be in the following order:

  1. Client32u.ini if located in the Deploy folder with the installer.
  2. Client32.ini if located in the Deploy folder with the installer (ignored if the Client32u.ini file is present).
  3. If there is no external Client Configuration file in the Deploy folder, the order of a new installation will be applied.

Deploying a Client Configuration
When performing a deployment of the new version using the NetSupport Deploy tool, the Client Configurations files applied to the installation will be in the following order:

  1. Client32u.ini if located in the folder selected.
  2. Client32.ini if located in the folder selected (ignored if the Client32u.ini file is present).

Using the Client Configurator
When using the NetSupport Manager Client Configurator from version 12.50, this will use the Client Configuration files in the following order:

  1. Client32u.ini.
  2. Client32.ini file (ignored if there is a Client32u.ini).

You can, however, use navigate/select to open a specific Client Configuration file but if both the Client32.ini and Client32u.ini are present and you select Client32.ini, the Client32u.ini will be used instead.

Saving the Client Configuration will store any changes in both formats Client32u.ini (UTF8) and Client32.ini (ANSI).

NetSupport Manager Client Service
The NetSupport Manager Client service for version 12.50 and above will read its configuration from the Client Configuration files in the following order:

  1. Client32u.ini.
  2. Client32.ini (ignored if the Client32u.ini file is present).

 

Was this article helpful?
4 out Of 5 Stars

2 ratings

5 Stars 0%
4 Stars 50%
3 Stars 50%
2 Stars 0%
1 Stars 0%
5
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Need help?