SecureLogin does not work for Citrix Published Apps after Installation

  • 7015120
  • 29-May-2014
  • 05-Feb-2015

Environment

NSL8.0
NSL8.0.1 
Win2008R2
Citrix XenApp server
Windows Terminal Server

Situation

SecureLogin does not work for Citrix published applications after installation of NSL 8 or 8.0.1 on Citrix Server 
SecureLogin does not perform single sign on for Windows Remote Desktop Services (RDS) apps
Citrix Published App option not available in SecureLogin installation wizard
SecureLogin installer does not present the option to install Citrix published application support
SLWTS.exe and SLLauncher.exe are not present in C:\Program Files\NetIQ\SecureLogin directory, even if all visible Citrix options were selected during the installation.    

Resolution

Fixed with NSL 8.0.2 or newer

Additional Information

Workaround for versions prior to NSL 8.0.2:

1) Copy SLWTS.exe and SLLAUNCHER.exe to the SecureLogin installation folder.  By default this would be C:\Program Files\NetIQ\SecureLogin   These files can be downloaded from here:
ftp://ftp.novell.com/outgoing/citrix-files.zip
    
2)
a. Create the registry key
HKLM\software\Microsoft\Windows\CurrentVersion\App Paths\SLLauncher.exe

b. In that new key, create a string Value called (Default) with value data being the full path to sllauncher.exe.  For example:
 (Default)        REG_SZ     C:\Program Files\NetIQ\SecureLogin\sllauncher.exe

c. Still in the SLLAuncher key, create a new string value called  "Path" with value data being the full path to the directory containing the sllauncher.exe file.

For example
Path    REG_SZ    C:\Program Files\NetIQ\SecureLogin\


3) Add a Dword  SLWTS.exe with value of 0 under
HKLM\SYSTEM\ControlSet001\Control\Terminal Server\SysProcs
For example
SLWTS.exe    REG_DWORD    0

    

4) Modify HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Appsetup
to add the value
"SLLauncher.exe SLWTS.exe"
Note that there is a space in between the two entries SLLauncher.exe and SLWTS.exe.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.