Users are not able to take advantage of single sign-on (SSO) after Universal Type Server was upgraded
Verify your server configuration
If you have reconfigured or reinstalled your operating system, make sure that the IP address and hostname have not changed. If they have changed and cannot be restored, a new SPN and keytab file must be created.
Note: In Windows 7 and Windows Server 2008 R2, certain encryption types used by Universal Type Server for Kerberos authentication are disabled by default. For more information regarding this configuration change, refer to this article.
Verify your Universal Type Server configuration
If you made changes to the configuration options in the login-config.xml file then that file will be replaced by a fresh copy of the default version during the upgrade. You must make the same changes to the new copy, or make a copy of login-config.xml prior to upgrading.
Customers who are still having problems with Kerberos single sign-on where the above suggestions have not resolved the issue can contact Extensis support.