Sample title

Safe AutoLogon Password Server

Version History

Version 2211 build 961
[+] Added more log information if a replication SALPS server could not be contacted
[+] All computer information is now replicated to other SALPS servers

Version 2211 build 944
[+] Clicking on a single username now populates the auto-gen fields
[+] Changed icon for restarting clients and refreshing SALPS servers
[!] Automatic password generation to a secondary SALPS server in some cases may not replicate the password

Version 2211 build 931
[+] Added the option to copy the username to clipboard
[+] When SALPS is unable to change passwords manually in the console, a balloon tip is now displayed instead of just the taskbar
[+] Misc optimizations
[!] When a 2nd SALPS is added to the console and the Replicate/Refresh is clicked, the console may stop responding if 2nd SALPS server’s firewall is enabled, it’s not found, or SALPS isn’t installed.
[!] ‘Run-time error 381: Incorrect array index’ when querying a computer’s status and the SALPS service does not have rights to query the remote computer
[!] If the firewall is enabled on the primary SALPS server, it cannot replicate changes to other SALPS servers

Version 2211 build 901
[!] Error 9 may prevent SALPS console from loading

Version 2211 build 891
[+] New command-line utility sutsalps.exe adds a user to a SALPS server (firewall does need to be turned off on the SALPS server)
[+] Change Usernames window is redesigned to show more column width for computer and username columns, and column widths are saved
[+] Finding computers now, by default, sorts the computers by name after querying
[+] Added icon for reloading AD users in ribbon bar
[+] If reloading console data and there are pending changes, a warning appears
[+] If replication server is online but the service is not running, or if there are other issues, the save window now shows the issue instead of a popup message box.
[+] Added client SAL version to the SAL CLIENTS tab listing
[+] Added option to copy computer names to the clipboard from the list or tree
[+] Saving Computers and Groups now has a completion %
[!] When sending .salset files from network drives, the settings may not copy to the destination SAL client
[!] Automatic password generation was giving error ‘No password in database’
[!] Reduced multiple entries in the log of ‘port 21801 seems closed’ to just once per SAL client

Version 2211 build 873
[+] Password generation settings are now replicated to other SALPS servers
[+] Added Password Age, Last Changed, and Next Change Date on AD Users tab
[+] In Reporting, added a progress bar, increased generation speed, column widths are saved
[+] Misc UI improvements
[!] Remote Computers/Add Computers dialog was not adding computers to SALPS
[!] Username was not getting written out to Reports when ‘Logon request from Safe AutoLogon client’ was logged
[!] The command-line program salpsset.exe was not adding computers to the remote SALPS server when using the -ac command
[!] Getting settings from a remote SAL client would incorrectly show “Safe AutoLogon is not running” and would not proceed.

Version 2211 build 809
[!] Read-only mode of SALPS would not load

New Version 2211 build 807
[+] A new Add Computers dialog streamlines adding computers to SALPS
[+] Adding users to SALPS is updated and easier to navigate and use
[+] Added more RDP resolutions, 1680x1050 and 1920x1080
[+] Passwords can now contain “, ‘, !, and *
[+] When replicating between SALPS consoles, the 2nd SALPS console does not require its display to be “Reloaded” – it does this automatically
[+] Misc console UI improvements
[!] Querying a computer would not properly display if a group in the tree was not selected, even if computers were in the list
[!] Replication between SALPS servers when not using port 21801 would not replicate users
[!] Replication server list was not resizing with console
[!] Moving a client between groups would get duplicated
[!] Last password changed date/time was not getting saved consistently and hence a report was not showing all users

Version 2207 build 719
[!] Fixed not saving with one SALPS server in list

New Version 2207 build 714
[+] Increased security by:
    (a) removed requirement to run service under username with Administrator rights on local and remote computers
    (b) removed requirement to have Remote Registry running on client SAL computers
    (c) removed requirement to use ports 135 and 445 for communications (or having to turn the firewall off)
[+] WM Software has been granted the use of port 21801 by for its software to communicate over an IP network. This allows firewalls to remain enabled on clients and servers.
[+] A utility to adding port 21801 to the firewall is included in both SALPS and SAL
[+] Option to dismiss when saving settings and there are other SALPS servers listed
[+] If a user is listed in the only SALPS server and the administrator adds another SALPS server (for redundancy), the user will be copied to the newly added SALPS sever. Previously this was a manual process.
[+] Changing the password change interval time to the same day but a later time will allow multiple password changes in the same day for testing purposes
[+] When installing .NET 3.5, SALPS now shows the Powershell progress bar instead of the DISM progress bar
[+] Status of client computers is now independent of the username running the console and only uses the privileges of the SALPS service username
[+] Gathering SAL client information is now multi-threaded, and status is retained until a refresh is done
[+] Added option of removing highlighted servers in the SAL Clients tab
[+] When refreshing computers, they can be checked or selected in the list with more descriptive message if it can’t find the computer.
[+] Added a count to show the number of computers in a group
[+] Pressing Delete or right-clicking on selected computers will remove them from the list
[+] Added option right-clicking on SAL Clients to get the status and to move to another group
[!] Fixed problem if NetBIOS computer name was > 15 characters
[!] Improved handling and decreased waiting time if a remote computer does not have SAL installed and the admin is trying to retrieve settings from it

Version 2203 build 357
[+] For enterprise customers who want to use a specific domain controller that might be faster, have less traffic, or is in closer proximity to the client, there is an option to enter a comma-delimited string of domain controllers manually instead of using the default domain controller that the operating system is using.

Version 2203 build 348
[!] If the console is not run with local Administrator rights, SALPS would not be able to write out data.
[!] ProgramData folder may not have sufficient privileges if the service username is not a local administrator
[!] SQL Server CE may not get installed if the service username was not a local administrator

New Version 2203 build 332
[+] If the SALPS console is running and the service stops, the notification and error message are not shown in the log file, and it is only written out to once, versus once every minute
[+] Improved searching for a LAS server, if one is listed in DNS
[+] For companies that cannot run the SALPS service as a local administrator, SALPS can now run under these security credentials
[+] Added a ‘Do not show message again’ if the service does not have sufficient rights
[+] Active Directory maximum password length is 256. Automatic password generation dialog updated to reflect this
[+] Right-clicking on a password now can be copied to the clipboard
[+] When sending usernames and/or the automatic logon state to client computers, if a few did not get updated, the rest proceed with the update. The client computers the did not get updated remain checked in the list.
[+] The Begin Evaluation dialog box can now get past, even if there is no Internet connection, by Shift+Clicking the Next button and sending the email to WM Software support
[!] Saving settings when rights aren’t elevated gave an access denied error
[!] Product page and WM Software website may not show up if only IE is installed as web browser
[!] At uninstallation by a non-admin, the UAC prompt was not showing the name of the software, only the .msi filename
[!] If the SALPS service is a non-admin, SQL Server CE was not getting installed
[!] Non-admins running the software had restricted permissions to write data to the Registry and INI files
[!] D911 error occurred if the SALPS Synch service was not running prior to starting the SALPS service at installation
[!] If the SALPS service is a non-admin, the service would not use the non-admin account
[!] The Sending User/State to Clients dialog boxes Check All and Uncheck All were not working
[!] Misc bug fixes and improvements

Version 2102 build 315
[!] Updated logging

Version 2102 build 313
[!] Misc bug fix

Version 2102 build 311
[+] If the SALPS console is running and the service stops, the notification and error message are not shown in the log file, and it is only written out to once, versus once every minute
[+] Improved searching for a LAS server, if one is listed in DNS
[+] For companies that cannot run the SALPS service as a local administrator, SALPS can now run under these security credentials
[+] Added a ‘Do not show message again’ if the service does not have sufficient rights
[+] Added a right-click and copy the password to the clipboard option
[!] Product page and WM Software website may not show up if only IE is installed as web browser
[!] Misc bug fixes and improvements

Version 2102 build 243
[+] In addition to the computer-joined domain DNS searches, Safe AutoLogon now also searches in domain suffixes if added manually, by local policy, or by group policy
[+] Can now right-click and copy the password to the clipboard
[!] If Insufficient Rights warning dialog appears because service runs under a non-admin account, the console is no longer ended

Version 2102 build 227
[!] Erroneous “Missing Data” message when SALPS starts

Version 2102 build 223
[!] Right-clicking on highlighted servers does not restart all of them; changed logic from checked to highlighted

Version 2102 build 218
[+] Ribbon bar items under AD USERS are highlighted when any adding to SALPS is chosen
[+] Right-click option to copy password to clipboard
[+] Display proper messages if the network is not connected or the workstation falls out of trust with the domain
[+] Right-click on computer in the list (or in the tree) and restart is now an option
[!] In the case of duplicate user entries in SALPS, the correct password is now sent to the client

Version 2102 build 217
[+] Local and remote installations now detect if a firewall is up
[+] If a long wait process while examining the remote computer prior to SAL installation occurs, or in general, installation can be canceled
[+] Redesigned remote installation window with more feedback while installing
[+] If there is no _wmssalps in DNS setup for the client computers, the console notifies the admin
[+] Admin is notified if the SALPS service is running without administrative rights
[+] Admin is notified if the domain firewall is on
[+] Restructured internal code for improvements reducing CPU
[+] Right-clicking on users now has an option to change the password for checked users
[+] Install/Uninstall dialogs user can now right-click on list of computers to check/select
[+] Updated Proof of Concept document
[!] Uninstall banner was not changing when uninstalling SAL from clients
[!] Change password was showing up when right-clicking on some lists
[!] Updating password manually would do it multiple times
[!] The console shows a Not Responding while querying the remote computer
[!] Numbers and symbols, if included, were never at the beginning of the password
[!] Remote installations would not occur if the admin chose to keep the default hiding of file extensions
[!] Updated fonts to match Windows Server 2008 and 2008 R2 default fonts

Version 2102 build 205
[+] Changed add computer dialog that finds a computer instead of using an intermediate dialog

Version 2102 build 201
[+] Added an uninstall dialog window
[+] Clicking on the ribbon button Install Safe AutoLogon brings up all the computers in SALPS without having to click on a group first
[+] More verbose logging when remote installing, like if a remote client does not allow installation because of possible anti-virus interference, SALPS is notified
[+] Installation log can now be saved
[+] Installation now shows a copy progress and if the setup file was copied to the target computer
[!] Remote installing from SALPS now shows a progress of copying the setup file to the target computer
[!] After uninstallation of SAL from a client, the SAL information still showed in SALPS
[!] Pause on installation would not stay paused

Version 2102 build 197
[+] Saving settings now sends the replication server list to the other replication servers
[+] Password read-only or password hide options for help desk operators
[+] Redesigned and optimized installation window and process
[+] Internal optimizations
[!] Viewing password column was not showing enough of column until the column was resized
[!] Console may lockup for a few seconds at startup
[!] Spurious error 32 was getting logged for the settings.ini
[!] Pressing Refresh on the Replicate tab would give a false positive of SALPS running on another server
[!] User auto-password generation settings were not replicating over to other SALPS servers
[!] Remote installation would show an error and not complete

New Version 2102 build 185
[+] Internal speed optimizations for password generation, loading users, saving users, starting program
[+] New right-click popup menu for lists of users and clients
[+] User passwords can now be generated by right-clicking on a user
[+] Enlarged maximum database sizes from 128MB to 4GB
[+] More informative dialogs
[+] More exhaustive password complexity testing
[!] Fixed error 70 on the SALPS console
[!] Fixed message box not dismissing incorrect SALPS logon name for the service
[!] Settings from .salset files may not be sent to remote computers during remote installation
[!] Settings from .salset files did not include security group type and name
[!] Spurious error showing settings could not be replicated when previous replication servers are removed

Version 2011 build 465
[+] Added a way to get the LAS server name, without having to change DNS, by manually adding an entry in the Registry. More information on how to do this is in our kb.

Version 2011 build 435
[+] Added a confirmation for saving/replicating
[+] Improved importing speed of users from Active Directory
[+] Improved speed of setting passwords in SALPS for users
[+] More efficient checking of password complexity requirements with Active Directory with progress
[+] New splash screen shows loading users when starting console, and saving users
[+] New status dialog shows progress when saving passwords manually
[+] Added a ‘Check/Uncheck Selected’ and a ‘Select/Unselect All’ for all user lists
[+] Indicator of total user count
[!] Replicating to other servers with their SALPS console running, their SALPS console was not getting notified
[!] In some instances, replication did not complete, leaving an incomplete database on target SALPS server
[!] Reduced CPU usage when generating user passwords
[!] Importing of users from Active Directory showed incorrect total amount when importing
[!] Sorting by AutoGen column produced an error in the console

New Version 2011 build 431
[+] Updated proof of concept to match new version
[!] On some systems, the Remote Administrator would not complete a password update
[!] The automatic password generation may end the SALPS service

New Version 2006 build 306
[+] Misc UI improvements

New Version 1910 build 283
[+] A new dialog sends usernames that exist in SALPS to Safe AutoLogon clients, if a company has many usernames/clients they need to change them quickly
[+] A new dialog sends enable/disable automatic logons to Safe AutoLogon clients
[+] Password automatic generation is now greatly expanded by using Mersenne Twister and dictionary words with or without numbers and symbols.
[+] The Autogenerate passwords for checked users now does not automatically save to AD, but instead just places the auto-generated passwords for each user into the list - this avoids forcing passwords to be saved to AD without the administrator reviewing them