Softpedia >Windows >System >OS Enhancements >Safe AutoLogon >  Changelog

Safe AutoLogon Changelog

What's new in Safe AutoLogon 6.0 Build 480

Jul 9, 2014
  • Settings can be protected from another group residing in another domain. If the client running Safe AutoLogon belongs to domain "A" and it logs in as a user on domain "A", the settings can be protected by a user that is a member of group "C" in domain "B". This gives more control over changing settings on the client.
  • Windows 8.1 clients would not automatically logon after a power off/power on.
  • If a SALPS server is listed in DNS, but the SALPS server doesn't exist and Safe AutoLogon is set to use local credentials, Safe AutoLogon would not automatically logon.

New in Safe AutoLogon 6.0 Build 237 (Jul 9, 2014)

  • The local hosts file can be used to list a SALPS server, if DNS servers cannot be updated with the SRV record
  • A new command-line utility allows a previously-saved salset file to be saved on a local or remote computer
  • Querying remote SALPS servers is no longer dependent on the current user’s security rights
  • SALPS server order was not being saved

New in Safe AutoLogon 5.0.2184 (Dec 16, 2013)

  • Misc internal code updates.

New in Safe AutoLogon 5.0.2173 (Sep 5, 2013)

  • Updated licensing for more flexibility with the LAS, so the software doesn't check in with the LAS after each boot.
  • Added a 'Check for Updates' option.

New in Safe AutoLogon 5.0.1201 (Jul 12, 2013)

  • Updated for Windows Server 2012 R2 and Windows 8.1 compatibility.

New in Safe AutoLogon 5.0.1095 (Jun 28, 2013)

  • Fixed the "code expired" error after pasting in a valid evaluation code

New in Safe AutoLogon 5.0.1091 (May 4, 2013)

  • Added a Help file
  • Misc internal improvements

New in Safe AutoLogon 5.0.1064 (Apr 24, 2013)

  • Added new language (Chinese). 15 languages supported: Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Indonesian, Italian, Malay, Norwegian, Portuguese, Spanish, Swedish.
  • Changed Options button functionality.
  • Updated the menus for Arabic and Chinese languages; changed misc labels and times to display appropriate language.
  • Fixed Safe AutoLogon not logging on if a company shows a security message prior to logging on and it is not acknowledged by the user by pressing the OK button after two minutes.
  • Fixed the confirmation of removing a SALPS server may not be visible.

New in Safe AutoLogon 5.0.1044 (Mar 13, 2013)

  • Fixed issue with domain-joined XP and pressing the Shift key if Ctrl+Alt+Del were bypassed.
  • Fixed issue when receiving SALPS settings for security groups privileges.

New in Safe AutoLogon 5.0.1033 (Mar 12, 2013)

  • Added new languages (Arabic, Malay, Indonesian). Languages supported (14): Arabic, Danish, Dutch, English, Finnish, French, German, Indonesian, Italian, Malay, Norwegian, Portuguese, Spanish, Swedish.
  • Entire user interface is now shown in all supported 14 native languages.
  • Simplified evaluation start screen.
  • Certified for Windows 8.
  • Added discount option on Settings window.

New in Safe AutoLogon 5.0.919 (Feb 21, 2013)

  • Added the ability to use the SALPS server if automatic log-back-on is enabled when a user logs off.
  • New graphics.

New in Safe AutoLogon 5.0.801 (Feb 21, 2013)

  • Now compatible with Windows 8 and Windows 2012.
  • Added new capabilities to coincide with the release of Safe AutoLogon Password Server 5.0.
  • User configuration through security was not keeping its values.

New in Safe AutoLogon 4.1.1428 (Jan 30, 2013)

  • Fixed an issue with x86 Vista and x86 Windows 7 systems in a VM where the reboot would freeze the VM.

New in Safe AutoLogon 4.1.1265 (Jun 16, 2012)

  • On 64-bit systems, About was showing 32-bit.
  • Fixed minor auto-logon issue with Win7x64.

New in Safe AutoLogon 4.1.1263 (Jun 16, 2012)

  • Faster AES calculations.
  • Minor bug fixes, not logging on with some x64 computers.

New in Safe AutoLogon 4.0.505 (Jun 16, 2012)

  • If the trial expired, or had 15 days left, the window indicating this information could not be closed.

New in Safe AutoLogon 4.0.501 (Jun 16, 2012)

  • If there was no DNS server available or the SRV record's computer was unavailable, running the UI for the first time would show "Installation Date Unavailable".

New in Safe AutoLogon 4.0.491 (Jun 16, 2012)

  • Optimized SRV record querying from DNS.

New in Safe AutoLogon 4.0.424 (Jun 16, 2012)

  • Safe AutoLogon now looks for an SRV DNS record entry for the SALPS server by default, instead of storing the SALPS server locally on each SAL client.
  • Running the software for the first time no longer prompts to scan for SALPS servers. Users can Scan for SALPS servers when adding them using Settings.
  • Like on Vista/7/2008, the Safe AutoLogon graphic now appears on the "Welcome to Windows" page.
  • The Settings window has been simplified.
  • If the TLP license is expired and the user tries to run the software twice (within 15 seconds), a notification showing TLP expired is shown. This allows the program to end gracefully without notifying end users.
  • Main UI Shows the maximum encryuption of the operating system.
  • There now is always a fixed amount of asteriks in the Password field, regardless of the length of the actual password. This decreases the ability to guess the password based on the number of characters.
  • More menu options.
  • Fixed autologon issue happening on some computers.

New in Safe AutoLogon 3.6.306 (Jun 16, 2012)

  • Fixed a few integration issues with the LAS on Novell networks.

New in Safe AutoLogon 3.6.248 (Jun 16, 2012)

  • Integration with WM Software License Administration Server.
  • Added option to export files for WM Software technical support.

New in Safe AutoLogon 3.5 Build 1135 (Feb 18, 2011)

  • F1 was not working on main window
  • TLP customers with an expired trial running Windows 7 would not be able to login after registering.
  • When using a larger font size, the graphic was not resizing correctly.

New in Safe AutoLogon 3.5 Build 1081 (Feb 18, 2011)

  • Added automatic logon functionality and multi-Language support for Danish, Dutch, Finnish, French, German, Italian, Norwegian, Portugese, Spanish, and Swedish languages and their variants.

New in Safe AutoLogon 3.1 Build 4412 (Feb 18, 2011)

  • TLP notifications are now only for Domain Admins at 60/30/15/10/5 days before expiration, and only then if the TLP license has not yet been renewed.
  • Added an Update link on the About form to retrieve latest licensing expiration information.

New in Safe AutoLogon 3.1 Build 4306 (Feb 18, 2011)

  • If on a domain, the client can now auto-query for Safe AutoLogon Password Servers (SALPS) servers.
  • Removed requirement of ICMP having to be enabled on the SALPS server in order for Safe AutoLogon to use the SALPS server.
  • Removed warning about a blank password.
  • On TLP licenses, only Domain Admins are notified when the license expires.
  • Fixed pressing Enter while in the main dialog did not simulate clicking the OK button.

New in Safe AutoLogon 3.0 Build 4021 (Feb 18, 2011)

  • When the SALPS server is installed on a DC and the SAL client is set to look only at DCs, sometimes the SAL client could not find the DC.
  • Header graphic would remain even if the client could not logon.
  • When the SALPS password changed coupled with a very fast Windows 7 client and a very fast SALPS server, the logon would sometimes be attempted before the password was fully retrieved from the SALPS server.
  • Shield icon was showing up incorrectly.
  • Misc logon issues.

New in Safe AutoLogon 3.0 Build 3145 (May 28, 2010)

  • Enhanced: Added an optional delay for wireless computers before the software attempts to connect to a SALPS server. Sometimes the network starts after the Safe AutoLogon service, especially on wireless computers, and hence the SALPS server cannot be found.
  • Enhanced: Reduced load time of user interface.

New in Safe AutoLogon 3.0 Build 1306 (Aug 18, 2009)

  • New: Added ability to change passwords remotely, for Enterprise customers or for customers that want to change passwords without having to touch the Safe AutoLogon clients, or require the SAL client computers to be turned on.
  • New: New product, Safe AutoLogon Password Server (SALPS), that keeps track of the passwords for clients.
  • New: Software can be configured to use a SALPS or not, and what to do if a SALPS server can't be found.
  • New: Added feature to view the log file.
  • New: Security model extends to either Local or Active Directory groups that can change Safe AutoLogon settings.
  • New: Password Server settings can be exported for importing on another Safe AutoLogon client.
  • New: Customers with a Term Licensing Program contract can now choose to select alerts when the TLP time period will be expiring.
  • Fixed: About form for trial licenses was always showing 30 days, regardless of the eval days left.

New in Safe AutoLogon 2.1 Build 153 (Aug 18, 2009)

  • Fixed: About form for trial licenses was always showing 30 days, regardless of the eval days left.

New in Safe AutoLogon 2.1 Build 152 (Aug 18, 2009)

  • Enhanced: Substantially decreased the time waiting for the automatic logon to begin.
  • Enhanced: Large installations that use the same id/password on many computers can now export/import registry settings to other computers.
  • Fixed: On some computers running either Vista or Windows 2008 32-bit operating systems, an error would show that a file is corrupted. Consequently, the automatic logon would not take place and the computer would hang before reaching the logon prompt.
  • Fixed: Misc UAC/TLP issues/consistency with multiple logoffs/different users.

New in Safe AutoLogon 2.0 Build 135 (Aug 18, 2009)

  • Enhanced: Some timing issues resolved/removed that prevented an auto-logon on some computers.

New in Safe AutoLogon 2.0 Build 131 (Aug 18, 2009)

  • Enhanced: Better integration with Safe AutoLogon Management Console.

New in Safe AutoLogon 2.0 Build 125 (Aug 18, 2009)

  • New feature: Self-recovery for automatic logon in the event of a hard reset (blue screen, power outage, etc).
  • New feature: Bypass automatic logon by pressing the Shift key.
  • New feature: Delay the automatic logon for a period of time.
  • New feature: Force a user to stay logged on - if they logoff, they will be automatically logged back in again.
  • New feature: Option to prevent Standard Users from changing Safe AutoLogon settings.
  • Fixed: After an autologon and a desktop lock, if the user logged off, then logged back on, the desktop locked again.

New in Safe AutoLogon 1.5.81 (Jun 11, 2007)

  • New feature: Automatic login can be directed to the local computer or a domain.