Safe AutoLogon Password Server
Version History
Version 2508 build 329
[!] Sending users and the state to clients was intermittently failing.
[!] Generating the passwords under ‘Auto-gen Passwords’ option was changing the 1st entry regardless if it was checked or not
New Version 2508 build 315
[+] Search boxes added for AD Users and SAL Clients tabs. The search box accepts wildcards such as PC*, *PC, PC*0, *PC*0*
[+] Replicating AD users to other SALPS servers is magnitudes faster. For approx. 750 users, the time went from 8 minutes to less than 10 seconds
[+] Multiple improvements to the console
[!] Paswords were not getting updated if the current day was past the interval days
[!] 0x8003, 0x374, 0x409 errors remedied
[!] Minor bug fixes
New Version 2502 build 173
[+] Querying SAL clients is significantly faster, regardless of the remote firewall state
[+] Improved interoperability for clients without RemoteRegistry or ICMP running/enabled
[+] Added a new way to enter a computer without having to first search for it in AD
[+] Localized text for common form buttons
[!] Manually entering passwords with leading or trailing spaces are not Active Directory compliant
[!] If .NET 3.5 was not installed before selecting an OU, the OU dialog would not appear, even if .NET 3.5 was installed
[!] For large quantities of clients in one group, the clients may not replicate to another SALPS server
[!] On non-US versions of Windows Server, SALPS may encounter incorrectly applied permissions on its required Registry keys
Version 2403 build 287
[!] Fixed any column widths equal to zero, are now sized properly
Version 2403 build 281
[+] SALPS can now send to a client even if SALPS is not using port 21801 and the client is using port 21801
[+] New progress dialog when retrieving settings from a remote SAL client computer to save into a .salset file
[!] Sending a .salset file to some Safe AutoLogon computers may take 15+ minutes
[!] Unable to send a .salset file to a client if the client is running 21801 and SALPS is not using 21801
[!] Saving settings warning is now shown and closed before Sending Users or State to clients
[!] When sending settings from the SALPS server to SAL clients, the SAL client may not have replicated certain entries in the Registry
Version 2403 build 204
[+] Added maximum log file size of SALPS logs
[+] UI improvements
[!] Replicated server settings may not get transferred to another SALPS server due to internal encryption settings
[!] In some circumstances, service would hang if manually stopped.
Version 2403 build 193
[+] UI improvements
[!] Replicated server settings may not get transferred to another SALPS server due to internal encryption settings
[!] In some circumstances, service would hang if manually stopped
New Version 2403 build 181
[+] Added an option to SAL CLIENTS tab to copy the table to the clipboard
[+] Redesigned interface for sending a .salset file to Safe AutoLogon clients, and added multi-threading so .salset files get sent faster.
[+] Improved reliability of sending .salset file to remote computer at installation
[!] If a client SAL was added without saving first, the status would indefinitely show “Querying…”
[!] There was a maximum amount of SAL Clients that could be replicated of 1024
Version 2401 build 219
[+] Sending .salset files to Safe AutoLogon clients can now be done without requiring the client and console both be on port 21801
[+] Sending .salset files to Safe AutoLogon clients is now shown in an active window
[+] More descriptive failure messages if SALPS and Safe AutoLogon clients cannot communicate
[+] Only the exe installation file for Safe AutoLogon can be remotely installed
[+] Get Client Status now shows the OS regardless if the remote computer has Safe AutoLogon installed or not
[!] The executable gadc.exe would crash if the local administrator (not the domain admin) logged in, ran SALPS, then queried for domain computers to add to SALPS
[!] On slow servers, the SALPS console would show an error about the Registry not being read correctly and the console would end
[!] Fixed discrepancy in showing the abbreviated product version vs the actual version and build (i.e. 2401 vs 24.01.165)
[!] Fixed issue where ProductName, ProductVersion, and WMSCommPort were overwritten when restoring a .salset file
[!] Misc UI improvements and bug fixes
Version 2401 build 207
[+] Sending .salset files to Safe AutoLogon clients can now be done without requiring the client and console both be on port 21801
[+] Sending .salset files to Safe AutoLogon clients is now shown in an active window
[+] More descriptive failure message if SALPS is not on 21801 but Safe AutoLogon client is
[+] Only the exe installation file for Safe AutoLogon can be remotely installed.
[+] Client Status now shows the OS regardless if the remote computer has Safe AutoLogon installed or not
[+] Updates to restarting clients and installing SAL software to clients with more informative text [!] The executable gadc.exe would crash if the local administrator (not the domain admin) logged in, ran SALPS, then queried for domain computers to add to SALPS.
[!] On very old/slow servers, the SALPS console would show an error about the Registry not being read in correctly and the console would end.
[!] Fixed discrepancy in showing the abbreviated product version vs the actual version and build (i.e. 2401 vs 24.01.165)
[!] Fixed issue where ProductName and ProductVersion were overwritten when restoring .salset file
[!] When sorting computers in a group, the console would show an error and end
[!] Misc UI improvements and bug fixes
[!] Sending users and the state to clients was intermittently failing.
[!] Generating the passwords under ‘Auto-gen Passwords’ option was changing the 1st entry regardless if it was checked or not
New Version 2508 build 315
[+] Search boxes added for AD Users and SAL Clients tabs. The search box accepts wildcards such as PC*, *PC, PC*0, *PC*0*
[+] Replicating AD users to other SALPS servers is magnitudes faster. For approx. 750 users, the time went from 8 minutes to less than 10 seconds
[+] Multiple improvements to the console
[!] Paswords were not getting updated if the current day was past the interval days
[!] 0x8003, 0x374, 0x409 errors remedied
[!] Minor bug fixes
New Version 2502 build 173
[+] Querying SAL clients is significantly faster, regardless of the remote firewall state
[+] Improved interoperability for clients without RemoteRegistry or ICMP running/enabled
[+] Added a new way to enter a computer without having to first search for it in AD
[+] Localized text for common form buttons
[!] Manually entering passwords with leading or trailing spaces are not Active Directory compliant
[!] If .NET 3.5 was not installed before selecting an OU, the OU dialog would not appear, even if .NET 3.5 was installed
[!] For large quantities of clients in one group, the clients may not replicate to another SALPS server
[!] On non-US versions of Windows Server, SALPS may encounter incorrectly applied permissions on its required Registry keys
Version 2403 build 287
[!] Fixed any column widths equal to zero, are now sized properly
Version 2403 build 281
[+] SALPS can now send to a client even if SALPS is not using port 21801 and the client is using port 21801
[+] New progress dialog when retrieving settings from a remote SAL client computer to save into a .salset file
[!] Sending a .salset file to some Safe AutoLogon computers may take 15+ minutes
[!] Unable to send a .salset file to a client if the client is running 21801 and SALPS is not using 21801
[!] Saving settings warning is now shown and closed before Sending Users or State to clients
[!] When sending settings from the SALPS server to SAL clients, the SAL client may not have replicated certain entries in the Registry
Version 2403 build 204
[+] Added maximum log file size of SALPS logs
[+] UI improvements
[!] Replicated server settings may not get transferred to another SALPS server due to internal encryption settings
[!] In some circumstances, service would hang if manually stopped.
Version 2403 build 193
[+] UI improvements
[!] Replicated server settings may not get transferred to another SALPS server due to internal encryption settings
[!] In some circumstances, service would hang if manually stopped
New Version 2403 build 181
[+] Added an option to SAL CLIENTS tab to copy the table to the clipboard
[+] Redesigned interface for sending a .salset file to Safe AutoLogon clients, and added multi-threading so .salset files get sent faster.
[+] Improved reliability of sending .salset file to remote computer at installation
[!] If a client SAL was added without saving first, the status would indefinitely show “Querying…”
[!] There was a maximum amount of SAL Clients that could be replicated of 1024
Version 2401 build 219
[+] Sending .salset files to Safe AutoLogon clients can now be done without requiring the client and console both be on port 21801
[+] Sending .salset files to Safe AutoLogon clients is now shown in an active window
[+] More descriptive failure messages if SALPS and Safe AutoLogon clients cannot communicate
[+] Only the exe installation file for Safe AutoLogon can be remotely installed
[+] Get Client Status now shows the OS regardless if the remote computer has Safe AutoLogon installed or not
[!] The executable gadc.exe would crash if the local administrator (not the domain admin) logged in, ran SALPS, then queried for domain computers to add to SALPS
[!] On slow servers, the SALPS console would show an error about the Registry not being read correctly and the console would end
[!] Fixed discrepancy in showing the abbreviated product version vs the actual version and build (i.e. 2401 vs 24.01.165)
[!] Fixed issue where ProductName, ProductVersion, and WMSCommPort were overwritten when restoring a .salset file
[!] Misc UI improvements and bug fixes
Version 2401 build 207
[+] Sending .salset files to Safe AutoLogon clients can now be done without requiring the client and console both be on port 21801
[+] Sending .salset files to Safe AutoLogon clients is now shown in an active window
[+] More descriptive failure message if SALPS is not on 21801 but Safe AutoLogon client is
[+] Only the exe installation file for Safe AutoLogon can be remotely installed.
[+] Client Status now shows the OS regardless if the remote computer has Safe AutoLogon installed or not
[+] Updates to restarting clients and installing SAL software to clients with more informative text [!] The executable gadc.exe would crash if the local administrator (not the domain admin) logged in, ran SALPS, then queried for domain computers to add to SALPS.
[!] On very old/slow servers, the SALPS console would show an error about the Registry not being read in correctly and the console would end.
[!] Fixed discrepancy in showing the abbreviated product version vs the actual version and build (i.e. 2401 vs 24.01.165)
[!] Fixed issue where ProductName and ProductVersion were overwritten when restoring .salset file
[!] When sorting computers in a group, the console would show an error and end
[!] Misc UI improvements and bug fixes