regibox Manager Deployment
version 2.1.0-7078, 2022-02-08
- Description of the setup process
- Installation options
- Uninstalling the software
- Proxy/Network Setup
- First use
- Windows Registry options
- Terminal Server and Citrix Information
- Linux options
- Debugging Problems
- Other resources and help
This document is meant to help administrators in deploying the regibox manager software to the users computers using software distribution methods. It also gives help on generic questions.
Description of the setup process
Upon started, the regibox Manager setup will close any running regibox manager instances automatically. This is mandatory in order to update files on Windows. This may take up to 30 seconds!
After installation, the regibox manager is set-up for auto-start! If users do not want to have regibox started automatically, they can turn it off individually in regibox Manager configuration.
|To get the customization, the regibox Manager automatically downloads his customizing information from the assigned regify provider after the user entered his credentials.|
The executable setup is well designed to get used in automatic software distribution and deployment. You can call it with several options.
Force the setup to do a complete silent installation.
Creates a logfile with the name Logfile_<ProductName>_MSI.txt in your system %TEMP% folder.
During the installation, an existing previous version will get updated.
Uninstalling the software
Uninstall the regibox Manager using standard system calls for uninstalling (like for any MSI package).
In order to allow regibox to work perfectly, you need to allow regibox to use several ports and addresses. By default, make sure that ports 443 and 80 are available for internet access and WebSockets are not filtered.
If you are using whitelist proxy or routing, you can determine all needed domains by using our tool located at regify.com/checkWhitelist.php.
More information can be found here: wiki.regify.com/index.php?title=Troubleshoot_Connectivity
If the software gets used the first time, the configuration automatically starts. Upon this, the user is asked to enter his login credentials in order to configure the software and to check for successful login. This is done automatically in the backend using the regify PLS service (Provider Lookup Service).
After successfull configuration, all values are written to the configuration location (%APPDATA%\regify\regibox\).
|Please note that the settings and configuration from %APPDATA%\regify\regibox\ can not get copied to another system! Values are encoded using hardware dependent information. Also there is cache information which will not match on other systems. Copying this data will very likely cause serious problems and may even damage regiboxes.|
Manual provider configuration
In order to enter all settings manually (without utilizing the regify PLS), please press Ctrl+m on the initial dialogue to enter the extended form. There you can enter all values manually and override the PLS function.
Windows Registry options
Registry options of the regibox Manager
This are the available registry parameters that must be located in
or for 64 bit systems in
If you set this parameter to 1, the regibox Manager does no search for available updates. Also, the search update will always say that the program is up to date.
|In environments with software deployment systems, most administrators do not like external software to ask users for updating. In such case, set DenyUpdateCheck to 1 to stop the regibox Manager looking for updates by himself.|
64 bit registry information
If you are on a 64 bit environment, please respect that your regedit.exe settings may not be visible by 32 bit apps like the regibox Manager. In this case, try to run regedit to edit the 32 bit registry using this hint:
In 64-bit Windows the entire 32-bit registry is located under the key HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node.
For example, on a 32 bit system:
is located on a 64 bit system at:
HKEY_LOCAL_MACHINE\SOFTWARE\ WOW6432Node \regify\Settings
Terminal Server and Citrix Information
Please note the following information in order to use regibox Manager software in Terminal-Server or Citrix environments:
Install normally on the server. If you run a cluster with multiple servers/hosts, please install on all host machines!
Special settings for Terminal-Server and Citrix
Using Windows Terminal-Server or Citrix with more than one physical host will trigger the need of a special registry entry on each host. Please ensure, that the key mentioned in this WIKI article exists on each host machine: https://wiki.regify.com/index.php?title=Terminal_Server_%26_Citrix_Host
ini file location
The regibox Manager on Linux offers some extra configuration by using a settings file:
Debian based systems:
Currently, only Debian based systems are supported.
Options on Linux:
If you set this parameter to 1, the regibox Manager does not search for available updates. Also, the search update button in configuration will always say that the program is up to date.
It is quite easy to debug connection issues. Ask the client to follow this guide:
Open regibox manager and prepare the situation you want to show us.
Press Ctrl+Alt+d in order to activate debug logging. Please confirm with YES.
Now, please try to replicate your problem or wait at least for 60 seconds.
Stop debugging by pressing Ctrl+Alt+d again.
The program is asking you for a location to store the debug information. We suggest to use the Desktop folder of your profile.
Ask the user to send you the file.
The diagnostics file is a ZIP compressed archive. Now open the contained regibox-log.txt. The entries beginning with VERB: or CURL: are showing all connectivity progress. Look for CRIT: or WARN: to identify issues.
If problems occur initially, you can run the regibox manager using command-line option to trigger logging:
regibox.exe -v -l "c:\somePath\box.log"
The diagnostics does not include document content, passwords or other sensitive information.