More FAQ on the regify homepage.
I have problems, can I do some debugging?
Yes, please take a look at the regibox trouble shooting pages.
Is it possible to redirect the regibox root folder?
Yes, there is a chance to set this to another location. Follow this guide:
- Stop regibox manager (right click on the ToolTray icon and close the program).
- Move the whole regibox root folder to the new location (incl. all subfolders). Do not copy, please move the folder and files.
- Edit the regibox.ini:
- The file is located in
- Windows: %APPDATA%\regify\regibox\regibox.ini
- Linux: ~/.regify/regibox/regibox.ini
- Mac OSX: ~/.regify/regibox/regibox.ini
- Change the "boxRoot" entry to point to the new root. The path needs to end on backslash (Windows) or slash (Linux, OSX).
- The file is located in
- Re-start regibox manager.
There are a few limitations for the location of the new regibox root folder. Please respect.
- Do not point to a location which is not having full read/write/delete access permissions for the user.
- We do not recommend to use a network share as regibox may become slow and sync may be not reliable. If you do so, please activate network mode in regibox manager settings.
- regibox is only accepting one regibox root folder. You can not run multiple instances of regibox to get more root folders.
- We recommend to never point multiple regibox managers from several computers to the same network share!
Is it possible to run regibox as a Windows service?
There is a daemon/service version available as SDK (Software Development Kit). It's named regiboxd and is available for Linux and Windows (x64). It allows the unattended use of regibox including API for automated processing. This is not to be confused with a desktop version of regibox. It does not offer GUI. Please contact support(at)regify.com for getting access to this SDK.
If you like to run the regular regibox GUI version, there is no serviced option available. You may consider software like AlwaysUp, but we have no experience with it and can't support you on this. It may be needed to make sure that no second instance is ran at any time in the same user context. Eg for running regibox manager to handle the configuration, the service would have to become stopped previously. For sure, you may need to test this carefully before production!
If you are willing to auto-login a session on your Server, please note that if Windows starts to the Desktop directly, it normally also auto-starts the regibox Manager by default. At least, the setup already adds it to the users auto-start during installation. If this fails for you, you may want to run regibox manager by yourself on Server startup together with the comand-line switch -m for a minimized start.
By the way, you can find the possible command-line options by running regibox manager executable using -h (for help).
How to execute a silent regibox setup?
Simply call the setup with the /silent 2 switch (Windows only):
regibox-1.3.2-4433.exe /silent 2
How to create a logfile for the installation process?
You can call the regibox setup file with the /logfile switch (Windows only):
This will create a file "Logfile_[ProductName]_MSI.txt" in your system %TEMP% folder. You can also combine this with the /silentex switch, if you like to get more information about the silent installation.