XoT Client installation guide for Windows 10 and 11
Download
Download the .msi installer package from https://support.xertified.com
Install
Start the .msi installer.
If your company uses Microsoft Company Portal, search for XoT Client and select Install.
Alternatively, you can install the .msi installer via command line msiexec.exe /i <path_to_package> [/quiet][/passive][/q{n|b|r|f}]
Configure
You need a personal .zip package to configure the XoT Client. This is generated via the XMS and shall be distributed by the administrator.
If no configuration is found when starting the XoT Client, the XoT Client Config application then opens. Alternatively, if you need to reconfigure the XoT Client, start the XoT Client Config application.
In the XoT Client Config application, select the toggle buttons you would like to configure. A default option should be to select all toggles for which you need administrator privileges.
Then select your zip package by clicking "Open" and browsing to the zip package.
If a password is needed, apply the password now.
Press apply, allow the service to restart, and close the XoT Client Config application. You are now ready to start the XoT Client.
Start
Open the start menu and select the XoT Client.
The connections come up as soon as you have established a connection to the XMS server.
XoT Client installation guide for MacOS
Download
Download the .pkg installer package from https://support.xertified.com
Install
Click the .pkg installer package.
If your company uses Microsoft Company Portal, search for XoT Client and select Install.
Alternatively, you can install the .msi installer via command line msiexec.exe /i <path_to_package> [/quiet][/passive][/q{n|b|r|f}]
Configure
You need a personal .zip package to configure the XoT Client. This is generated via the XMS and shall be distributed by the administrator.
run $ /opt/xertified/bin/config-setup.sh and follow the instructions.
3.
Start
Click the XoT-Desktop client icon to start.
Troubleshoot
If the "Global config file not valid" error occurs. It is due to an incompatible Client configuration version. Follow this procedure to upgrade your Client config version.