KB2411211 - Using a central USBSecure.ini file
Nov-21-2024
This article explains the central use of the USBSecure.ini configuration file.
USBSecure Enterprise 5, USBSecure OT 5, USBSecure Enterprise 6, USBSecure OT 6
Using a central USBSecure.ini
The USBSecure client is configured via the USBSecure.ini file. By default, the file is stored locally on the clients without a central configuration option - but can also be managed centrally.
Advantages of the central USBSecure.ini file
If you use a central USBSecure.ini, you can specify various configuration settings centrally. The most important setting is the specification of the USBSecure server (Server=). If the name of your USBSecure server changes due to an upgrade or new installation, you only need to change one entry in one location. As soon as the client has received the information, it contacts the new server.
Further examples of central settings:
KeyboardInstall=allow/warn/block
Determines the behavior when connecting additional keyboards.
LocalDevicesCopy=0 (or minute value)
Specifies whether the device information found should be copied to a central location.
User texts
All texts that affect your users can be configured via the USBSecure.ini file.
Set up the central USBSecure.ini file
To set up a central USBSecure.ini, proceed as follows:
- Configure a central USBSecure.ini that you copy from a client (C:\Program Files (x86)\USBSecure) and make it available in your Device$ share. Customize the values within the file as desired.
- Make sure that the LocalDevicesCopy setting in the local USBSecure.ini files (under C:\Program Files (x86)\USBSecure) on the clients is set to a value greater than 0.
By default, this value is set to 15. This means that 15 minutes after the USBSecure service is started, the central USBSecure.ini file (if available) is copied locally. It will then be used the next time the USBSecure service is started.
KnowledgeBase Home | What's new?