If a password-protected application starts before SecureLogin is initialized, SecureLogin is unable to process the login request for that application. To solve this problem, change the startup order of the applications. Use one of the following options, according to how your application has been configured to autostart:
You can move application start commands from Registry Run to the Startup group. Move the start commands for password-protected applications from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Current Version\Run to the \Windows\Start Menu\Programs\Startup group.
Startup scripts are scripts that are executed during SecureLogin's startup. You can move application start commands from Run or the Startup group to a SecureLogin startup script. This option has the following possible drawbacks:
To resolve this issue, place a .ini file on each computer. This file would list the applications that are to start after SecureLogin has initialized.
To resolve this issue:
After users have added the list to the .ini file, they must restart the application, or log out and log back in to the workstation. (This is a one-time task.)
If for some reason SecureLogin doesn't detect an application when it is launched from the startup script, you can modify the startup script to call a batch file. The following example startup script launches Novell iFolder®:
Run "c:\Documents and Settings\administrator\desktop\ifolderlaunch.bat"
The batch file contains the following lines:
Sleep 1
Start "ifolder" /MIN /B "c:\Program Files\novell\ifolder\trayapp.exe"
Exit
Use the Icon Order and Wait on Force Run options in Novell Application LauncherTM. These options enable you to use Application Launcher to do the following:
One possible drawback with this option is that some users might not want to start an application that Application Launcher launches.