SLMANAGER.EXE is installed when upgrading from SecureLogin 6.0 to SecureLogin 7.0

  • 7004453
  • 16-Sep-2009
  • 26-Apr-2012


Novell SecureLogin 6.0
Novell SecureLogin 7.0
Novell SecureLogin 6.1


When upgrading from SecureLogin 6.0 to SecureLogin 7.0, SLMANAGER.EXE is automatically installed.  There is no option or method available to keep SLMANAGER from being installed during the upgrade process.  If this is a concern, please refer to the Resolution section for one possible work around.  This same behavior occurs when upgrading from SecureLogin 6.0 to SecureLogin 6.1. 


To resolve this issue, SLMANAGER.EXE needs to be removed from the workstation manually.  An administrator can simply delete the shortcut for the application and the corresponding .exe.

The file paths on a default install are:

C:\Documents and Settings\All Users\Start Menu\Programs\Novell SecureLogin\SecureLogin Manager.lnk
C:\Program Files\Novell\SecureLogin\slmanager.exe


Reported to Engineering

Additional Information

SLMANAGER.EXE is an administrative tool used to manage SecureLogin.  In the SecureLogin 6.0 version this tool was made available to administrators via a "Tools" folder as part of the source installation files.  It was never installed as part of the SecureLogin client install.  In SecureLogin 7.0, SLMANAGER is no longer a part of the utilities located in the "Tools" folder and is now delivered through the .MSI.  If installing SecureLogin on a PC that has not had SecureLogin installed, you have the option to perform a Custom installation which gives you the option to install the Admin Tools.  On a PC with an earlier version of SecureLogin installed, the only installation option available is that of Upgrade, which installs SLMANAGER.EXE automatically.

This process can be automated by creating / deploying the following in a .BAT file:

@echo off
del "C:\Documents and Settings\All Users\Start Menu\Programs\Novell SecureLogin\SecureLogin Manager.lnk"
del "C:\Program Files\Novell\SecureLogin\slmanager.exe" 

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