UserLock^® History

UserLock 4.02

• Added: Windows Server 2008 compatibility
• Added: Ability to monitor logon denied by Windows (invalid password). These events can be displayed to users in the welcome message. Audit logon events policy needs to be enabled for failure events for all protected computers (doable through group policies). For more information click here
• Fixed: Some issues with Windows Vista and Windows Server 2008
• Fixed: Service wasn't stopping properly in case of a server shutdown/reboot
• Fixed: If a maximum session time was set immediately after the installation of UserLock all already opened user sessions could be logged off in some specific cases.
• Improved: Ability to use a localization mask with a naming convention that identifies building with letters (A,B,C,...). New wildcards to be used in the mask are: * = Building, % = Room, ? = Machine. Localization masks using the previous system will still work. For more information click here
• Fixed: A potential deadlock in the UserLock service
• Fixed: When trying to uninstall the agent from a computer without the agent installed a wrong error message was displayed

UserLock 4.01

• Fixed: The previous session logoff dialog was not fully translated in English
• Fixed: A memory leak in the backup server
• Fixed: A session with a local account was sending connect/disconnect notification to the UserLock server leading to an error event
• Fixed: In some cases the web interface was unable to display reports
• Fixed: The welcome message wasn't displayed after the logoff of a previous session
• Improved: UserLock service dependency to the workstation service
• Fixed: If the logon rate was too high, the transaction log (ulagent.log) was not regularly cleaned
• Fixed: If a protected account was based on a universal group, UserLock wasn't including members of other domains in the list of concerned users.
• Fixed: If a UserLock admin had only the right to administrate sessions he was unable to display reports because he was not allowed to retrieve the database connection string.

UserLock 4.0

• Fixed: Internal exceptions when the user session list was empty.
• Fixed: Crash of the session statistics report when the database was empty.
• Fixed: The ascending/descending order radio buttons were not working correctly in the session statistics report.
• Fixed: Some temporary files were not cleaned while generating report in a batch or in a scheduled task
• Fixed: When disconnecting a locked terminal session the UserLock service was sometimes thinking that the session was still active.
• Fixed: The permissions tab and the user sessions by computer view were not grayed on backup servers

UserLock 4.0 release candidate

• Updated: The help file was updated. The online version is available here.
• Improved: Button sizes in the web console
• Improved: Some internal improvements in the UserLock service
• Fixed: A bug was making crash the MMC console in some cases while refreshing the view
• Fixed: A bug in hours management when a session needed to be closed at 12:00 AM
• Fixed: A handle leak while sending E-mail notifications
• Fixed: Two memory leaks in the UserLock service
• Removed: The beta warning


Important! Existing customers with an up to date maintenance need to ask for their new UserLock 4 license key before installing this new version on their network.

UserLock 4.0 beta 2

• Fixed: A bug in the web console while displaying sessions by user.
• Added: The new license system was integrated. Current customers with an up to date maintenance can already ask for their UserLock 4 license key
• Fixed: A bug leading to users with empty names.
• Fixed: A bug while deploying the agent on Windows Vista computers
• Improved: All executables including the installation package are now signed
• Added: Ability to print the pages User sessions and Agent distribution from the web console.
• Improved: During a migration from UserLock 3 if the group UserLock Admins exists, UserLock administration rights are automatically added for this group.


Please also read comments of the previous beta version

UserLock 4.0 beta

For more information about all new features see the document What's new in UserLock 4


• New: Ability to define working hours for protected users
• New: Ability to define maximum session time for protected users
• New: Ability to define maximum group limits
• New: The administrator will have the possibility to enable an option allowing users to remotely close their previous session as they logon to another computer.
• New: Ability to define access rights to the UserLock administration console,
• New: Ability to breakdown the computer name syntax into a readable format in order to locate computers (building/room).
• New: Ability to customize the console’s User sessions view
• New: The web console can display the user session and agent distribution result in paged mode
• New: Multi selection in the User sessions view of the MMC console
• New: Ability to customize the agent distribution view
• New: The user display name is now displayed in the user sessions view of the console and in reports instead of the user account name.
• New: Terminal session connection/disconnection tracking
• New: Ability to enable a public Web interface (SysLocator) allowing users to locate free computers
• New: Ability to automatically generate reports at regular intervals
• New: Two new reports (printable version of what you see in the console) Agent Distribution and User sessions In order to avoid any misunderstanding the old “User sessions report” was renamed into “Session history”.
• New: Ability to display reports from the Web console
• New: The UserLock agent will send its status at each computer startup
• New: The agent will notify to the server any computer crashes to fix the session database.
• New: The UserLock agent will regularly try to send unnotified logon events to the server.
• New: Support of Windows Vista


This version will display a warning message to users saying that this beta version should only be installed on a test environment. If you want to install this beta version on your production environment please enroll to the UserLock 4 beta program by sending a mail to support@isdecisions.com
This beta version will expire end July.

UserLock 3.53

• Fixed: The UserLock server no longer tries to deploy the GINA agent on Windows Vista computers. "OS not supported" is returned.
• Added: Support of the beta version of the new Windows Vista agent that can be downloaded from the following link:
  http://www.isdecisions.com/download/ULAgentVista.msi
  You need to install manually the msi file on each Windows Vista machine to protect. You will get more information about the setup in the following document:
  http://www.isdecisions.com/download/ULAgentVista.pdf
• Fixed: In some cases a communication problem was leading to display invalid characters.
• Fixed: In some rare cases the database insertion thread was crashing while connecting to the database.

UserLock 3.52

• Fixed: The protected zone was not configured correctly for domains with a NetBIOS name different than the hostname. Symptoms: Just the server itself was displayed in agent distribution.
• Fixed: The web interface configuration tool was changing the authentication mode on the root folder of the IIS site instead of doing it directly on the UserLock virtual folder.
• Fixed: A UserLock service installed on a Windows 2003 SP1 server was unable to deploy the agent on 64 bits computers
• Improved: User accounts are now sorted by name in the web interface
• Fixed: A problem while sending E-mail notifications to some specific SMTP servers
• Fixed: The UserLock service was hanging in some cases (Error 0x0000079 in the console)
• Fixed: A few bugs in reports
• Fixed: A bug in the LogonCleaner.


The version of the agent did not change.

UserLock 3.51

• Fixed: A bug in the communication between the web console and the UserLock server. The user sessions list or the agent distribution list were incomplete in some cases.
• Fixed: A bug in the policy.
• Fixed: In some rare cases if an internal exception occured in the UserLock service users were unable to logon (a service restart was needed to fix the problem).
• Added: Abitity to reboot computers through the MMC administration console (Already available in the web console).
• Fixed: A few bugs in the web console
• Improved: The user sessions report show up faster
• Fixed: UserLock was not working correctly on domains with an '@' character in the NetBIOS name.
• Fixed: Citrix presentation server 4.0 register now its GINA in a different way and this was leading after an upgrade of both products to the unability to open ICA sessions (the logon hang).
• Improved: When a computer is removed from the domain with a session registered in UserLock the session is now automatically removed.


Important! For existing customers, the upgrade procedure was updated in the FAQ. Please take a look.

The version of the agent did not change.

UserLock 3.5 final release

• Fixed: The database insertion thread was crashing in some case disallowing any new insertions
• Fixed: UserLock 3.5 beta 2 was unable to logoff/lock users with the administration console
• Fixed: Database connection string changes through the web interface were not applied immediately
• Fixed: The 404 web page was not correctly registered in the IIS virtual folder

UserLock 3.5 beta 2

• Added: Support of x64 workstations and terminal servers
• Added: The UserLock server can be installed on x64 servers in the following modes: Primary server, backup server and relay server. The standalone terminal server mode is currently not supported.
• Information: The x64 version of the agent is numbered 3.0.7.37 (instead of 3.0.7.35 for the x86 version)

UserLock 3.5 beta

New! A web interface in order to administrate UserLock through a web browser. The web interface is similar to the MMC based administration console.

New features only available in the web interface
• Ability to Logoff/Lock/reset several sessions at a time
• Ability to reboot workstations
• Ability to only display users with an active session


Features not available in the web interface (only available in the MMC console)
• Reports cannot be displayed
• The database wizard cannot be used to configure the database connection string
• You cannot browse for computers or user accounts
• You cannot start the Logon cleaner


If IIS is not installed while installing UserLock you can configure the web interface later by starting the UserLock Web admin configuration tool from the start menu.

All other components are exactly the same as in UserLock 3.05.

UserLock 3.05

• Fixed: A memory leak in the service when the network zone was an Organization Unit.
• Improved: If the service is unable to retrieve the computer lists from the network zone an error event is inserted only if the problem occurs during more than 30 min (e.g. DC unavailable)
• Improved: Error handling while sending E-mail notifications

UserLock 3.04

• Fixed: If the UserLock service was installed on a Windows server 2003 the console launched reports on the default database with a wrong connection string.
• Fixed: In the User sessions report the total computer time was wrong in some cases
• Fixed: Wild card characters were not working when using the User sessions report on a MS Access database
• Fixed: The configuration wizard was unable to display organizational units on domain with a NetBIOS name different from the DNS name.
• Improved: If the global catalog is too big the configuration wizard list only OUs in the local domain.
• Fixed: When the remote registry service was not running on workstations the agent status was false (Upgrading (Waiting for reboot)) and the deployer did not report any error while installing the agent.
• Fixed: Reports were printing the result on two US letter pages instead of one. If you still have the problem please contact us at suport@isdecisions.com.

UserLock 3.03

• Fixed: A bug in the database insertion. An invalid character was added at the end of strings for some databases
• Added: Ability to display a welcome message to the user with information about the last logon. You can configure this in protected accounts. You need to deploy the new agent for the feature.
• Improved: AD tree is displayed faster in the Configuration wizard.
• Improved: The service loads the computer list faster from organizational units
• Added: In the User sessions report. The ability to filter computers with wildcards (*,?). For example to only display the report for room (example ROOM10*).
• Added: The User sessions report can display the computer occupation percent during the report period and you can also specify the total number of computers for the calculation.
• Fixed: The uninstall link was not checking if agents were still deployed

UserLock 3.02

• Fixed: A bug while trying to send a test E-Mail or while specifying a new database connection string in the console (Unable to read data & Permanent error)
• Added: Ability to only display user sessions outside working hours in the User sessions report
• Added: Ability to group logons by user, domain, computer, client name or client address in the User sessions report.
• Improved: During an administrative logoff or lock if the session was not found the session is removed from the database
• Improved: Auto reconnection to the database after a connection failure
• Improved: The deployer can detect IP conflicts to avoid the generation of events 3034:MRxSmb or 4:Kerberos (KRB_AP_ERR_MODIFIED). To enable this you need to create the following registry value: HKEY_LOCAL_MACHINE\SOFTWARE\ISDecisions\UserLock\CheckIpConflict = REG_DWORD:1 When done restart the UserLock service. The status of all faulty computers will display "Invalid address"
• Added: The Logon Cleaner allowing you to regularly delete old logons in the UserLock database to save disk space. You can schedule the logon cleaning.
• Fixed: The deployer was unable to update the agent on computers with a third party GINA installed
• Improved: the export button for reports is available directly in the viewer

UserLock 3.01

• Fixed: After registering the backup server client workstations were configured only after the next service start.
• Fixed: After a workstation reboot the UserLock server was not able to detect lost sessions on this workstation.
• Fixed: Client restrictions were not applied on terminal sessions during a session reconnection
• Added: Ability to specify a computer name (instead of selecting the computer in the browser) in client restrictions
• Fixed: A communication problem between the console and the server occuring only in rare cases (Symptom: incomplete computer and session list).
• Fixed: Crash of the USerLock service if not enough swap file was available on the server.
• Fixed: For workstations with a NetBIOS name with more than 15 characters the logoff was sometimes locking up the workstation.
• Fixed: In evaluation mode the lock/unlock activity was not inserted in the database
• Fixed: The export in CSV was not working in reports
• Fixed: A bug that was leading in some cases to a service hang
• Added: Abiliy to import automatically at the first service start-up settings of a previously installed copy of Userlock 2.x (except deployment settings)

UserLock 3.0 final release

• Fixed: a bug in the logon policy
• Improved: final version of the help file
• Added: Error events for helping to understand problems during synchronization, notifications, database insertions.
• Improved: Access denied directly at the connection to the service if the user is not allowed to administrate UserLock.
• Fixed: When locking terminal sessions from the console the session was closed instead of disconnected.
• Fixed: When a logon was denied for a terminal session a logoff was generated immediately after.


Information: This version is compliant with the agent of all versions greater or equal than 2.4. However if a UserLock 2.xx agent is deployed you should upgrade the agent as soon as possible to get all new features working.

UserLock 3.0 beta

New features:

• Ability to protect terminal sessions. RDP sessions (Microsoft) and ICA sessions (Citrix)
• Ability to protect standalone Terminal servers in a worgroup (using local accounts)
• Backup servers (one for each primary server)
• Ability to protect several domains with one primary server
• Ability to protect only 1 organizational unit in a AD domain
• Ability to log lock/unlock events on workstations
• Ability to insert logon/logoff/lock/unlock events in a ODBC database
• Two printable reports "User Sessions report", "User sessions statistics"
• Regular check on all workstations for unknown sessions
• Ability to logoff users in the UserLock console


Information: This version is compliant with the agent of all versions greater or equal than 2.4. However you should upgrade the agent as soon as possible to get all new features working.

UserLock 2.65

• Improved: Deleted account are automatically removed from the user sesssions report (when the service starts)
• Improved: Accounts with a last logon time older than 1 month are automatically removed form the user sesssions report (when the service starts)
• Fixed: a bug leading to a periodic service crash in some cases
• Fixed: The logons can be ordered according the logon/logoff time in the console
• Fixed: Displayed columns can now be customized in the console

UserLock 2.64

• Fixed: Bug in the policy settings

UserLock 2.63

• Improved: Use 10 times less CPU
• Improved: The agent doesn't display an error message during the logoff when the workstation is unplugged (for laptops)
• Improved: Ability to display variables (%sessions%) in denied messages.

UserLock 2.62

• Improved: If a user has exceeded the number of allowed sessions UserLock check that he's really logged on all computers before giving a negative answer. This feature require to upgrade to the new agent.
• Improved: The deployment thread ping all computers before trying to connect to them in order to avoid long timeouts. If needed the ping can be disabled with the following registry value: HKEY_LOCAL_MACHINE\SOFTWARE\ISDecisions\UserLock\NoPing = 1 (DWORD)
• Improved: The multiselection is now allowed when adding restricted/allowed workstations (Windows 2000).
• Fixed: Bug in the notifications. The already logged on computers were not displayed since the 2.6 version.


Information: This version is compliant with the agent of all versions greater or equal than 2.4.