Safe AutoLogon Password Server
Version History
Version 2403 build 193
[+] Misc 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
Version 2401 build 186
[+] More informative description of SALPS replicated server status if any issue
[!] Fixed when using port 21801, SALPS may not recognize it in the console interface
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
[+] Misc 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
Version 2401 build 186
[+] More informative description of SALPS replicated server status if any issue
[!] Fixed when using port 21801, SALPS may not recognize it in the console interface
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