UserLock Frequently Asked Questions
UserLock disaster recovery.
You can install somewhere in you network a UserLock Backup server. This server needs to be installed on a server member of the domain and configured to use a different database than the Primary UserLock server.
If your Primary server meets an issue, UserLock agents will automatically switch to the backup server and maintain the protection enabled, which allows you to have time to install a new Primary server (or switch the Backup server to a Primary and install a new backup server).
Primary and Backup server will automatically be synchronized, without doing anything more.
From UserLock version 8
For disaster recovery, you have to include in your backup process of your Windows 2008 server and higher:
- The folders localized in C:\ProgramData\ISDecisions\UserLock\Config containing UserLock configuration files.
- The database, named UserLock.mdb if you use the default database given with the package, localized in C:\ProgramData\ISDecisions\UserLock\Database.
For Windows 2003 Server, you have to include:
- The folders localized in C:\Documents and Settings\All Users\Application Data\ISDecisions\UserLock\Config.
- The database, named UserLock.mdb if you use the default database given with the package, localized in C:\Documents and Settings\All Users\Application Data\ISDecisions\UserLock\Database.
For previous versions of UserLock
You have to include in your backup process:
- The 3 UserLock configuration files: "UserLock.cfg", "UserLock.old.cfg" and "UserLock.lastknowngood.cfg" localized in the UserLock installation folder (C:\program files[ (x86)]\ISDecisions\UserLock by default).
- The database which contains all session activity history.If you are currently using the default database provided with UserLock, then the database file is named "UserLock.mdb". Depending on the server Operating system, you will find it in the installation folder or C:\ProgramData\ISDecisions\UserLock\Database.
The UserLock Backup server doesn’t need to be added to your backup procedure, as its information is synchronized from the Primary server.
If you meet a physical problem on the Primary server and you have to:
- Install UserLock on the new server
- Start the configuration wizard but don’t click on Next in the Service account step. Leave the wizard on standby.
- From UserLock 8: Copy the folders containing UserLock settings from your backup system to C:\ProgramData\ISDecisions\UserLock\Config (W2008 and higher) or C:\Documents and Settings\All Users\Application Data\ISDecisions\UserLock\Config (W2003 only).
For previous versions of UserLock: Copy the 3 UserLock configuration files from your backup system to the UserLock installation folder (C:\program files[ (x86)]\ISDecisions\UserLock by default).
- Click Next in the UserLock configuration wizard on the new server. The new service is automatically started and is working.
- Register your license serial through the console on the UserLock server properties.
- Set the database connection string in the Server properties (log section) if you are not using the UserLock.mdb Access database file.
- Once everything is ready, you have to register on the Backup server this new Primary server (even if you use the same name on the new server). To do it, launch on the Backup server the Configuration wizard (Start menu/All programs/UserLock/Tools/Configuration Wizard). On the first step, choose the Backup server and specify the name of the Primary server, even if you have used the same name as before. Follow the Wizard next steps until the end to validate it.
As said previously, instead of reinstalling a new Primary server, you can switch the Backup server role. Be sure that the synchronization was working well.
Then launch on the Backup server the Configuration wizard (Start menu/All programs/UserLock/Tools/Configuration Wizard).
Choose the Primary server role and follow the next steps. Once finished, the Backup server will become the new Primary server.
You will have to install a new Backup server on another server member of your Protected zone.
If there is a general Network issue or if both Primary and Backup server are not reachable, Agents will automatically disable the session rules to allow users to logon. Every session events will be stored locally into specific agent logs for history and sent to the server when the connection will be repaired.
It will permit to check the session connections during this period through reports.