SecureLogin stops acting upon configured Windows applications
NSL no longer sees Windows executables
SecureLogin will not populate Windows login boxes that worked before
Solution 1. Make sure “Allow single sign-on to Windows applications” is set to “yes.” Look in either the workstation “Manage Logins” utility or in the directory management utility (iManager, SLManager or MMC) under “Preferences,” “Windows.”
Solution 2. Modify or delete the "include" section of exclude.ini found in c:\program files\ novell\securelogin.
The “Allow single sign-on to Windows applications” setting will be inherited by users in groups or container, or for whom a GPO applies. Setting this setting to “No” in any of those places could result in users not being able to single-sign-on into Windows apps. Note that the directory management utilities show where settings are inherited from.
Exclude.ini will only exist if it has been created. This file can be used to prevent SecureLogin from acting upon any listed executable. If an “Include” section has been created in the exclude.ini SecureLogin will ONLY act upon the executables listed. SSO to all other executables will be excluded. If the "include" section is to be used then ALL desired executables must be listed.
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.