Starting Application Launcher/Explorer

The following sections explain how to manually start Application Launcher and Application Explorer and how to automate the starting of the applications:


Manually Starting Application Launcher

To manually start Application Launcher on a workstation:

  1. Make sure that the Novell ClientTM for Windows 95/98 (version 3.3 or later) or the Novell Client for Windows NT/2000 (version 4.8 or later) is installed on the workstation.

  2. Run NAL.EXE from the SYS:\PUBLIC directory on a server where you installed Application Management.

NAL.EXE copies Application Launcher files to the workstation and starts Application Launcher.


Manually Starting Application Explorer

To manually start Application Explorer on a workstation:

  1. Make sure that the Novell Client for Windows 95/98 (version 3.3 or later) or the Novell Client for Windows NT/2000 (version 4.8 or later) is installed on the workstation.

  2. Run NALEXPLD.EXE from the SYS:\PUBLIC directory on a server where you installed Application Management.

NALEXPLD.EXE copies Application Explorer files to the workstation and starts Application Explorer.


Automating Application Launcher Startup

To automatically start Application Launcher each time a user logs in to NDS:

  1. Make sure that the Novell Client for Windows 95/98 (version 3.3 or later) or the Novell Client for Windows NT/2000 (version 4.8 or later) is installed on the workstation.

  2. Enter the following line in the user's login script:

    @\\servername\sys\public\nal.exe

    where servername is the actual name of your network server.

    You can enter this line in a container, profile, or user login script. If the login script also contains an entry for the Automatic Client Upgrade (ACU), make sure the NAL.EXE entry is listed before the ACU entry.

    IMPORTANT:  You can also add Application Launcher to the Windows Startup folder. This enables Application Launcher to start when the workstation is disconnected from NDS. You configure this option in ConsoleOneTM and can have it apply to a single user, a group of users, or all users in a container. To do so, right-click a User, Group, or container object > click Properties > click the Application Launcher tab. On the Application Launcher page, click Edit > click the User tab > scroll to select the Auto-Start NAL When Disconnected option > set the option to Yes.


Automating Application Explorer Startup

To automatically start Application Explorer each time the user logs in to NDS:

  1. Make sure that the Novell Client for Windows 95/98 (version 3.3 or later) or the Novell Client for Windows NT/2000 (version 4.8 or later) is installed on the workstation.

  2. Enter the following line in the user's login script:

    @\\servername\sys\public\nalexpld.exe

    where servername is the actual name of your network server.

    You can enter this line in a container, profile, or user login script. If the login script also contains an entry for the Automatic Client Upgrade (ACU), make sure the NALEXPLD.EXE entry is listed before the ACU entry.

    IMPORTANT:  You can also add Application Explorer to the Windows Startup folder. This enables Application Explorer to start when the workstation is disconnected from NDS. You configure this option in ConsoleOne and can have it apply to a single user, a group of users, or all users in a container. To do so, right-click a User, Group, or container object > click Properties > click the Application Launcher tab. On the Application Launcher page, click Edit > click the User tab > scroll to select the Auto-Start NAL When Disconnected option > set the option to Yes.