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:


Rights for Windows NT/2000/XP/XP Users

Application Launcher/Explorer needs to be able to copy files to the workstation, write to the Windows registry, and so forth.

On Windows NT, users need to be members of the Users group to receive all the required rights

On Windows 2000, users need to be members of the Power Users group.


Manually Starting Application Launcher or Application Explorer

You can run either Application Launcher or Application Explorer on a workstation. Do not run both on the same workstation.

To manually start Application Launcher or Application Explorer on a workstation:

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

  2. To start Application Launcher, 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. For details about Application Launcher files, see Setting Up Application Launcher/Explorer .

  3. To start Application Explorer, 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. For details about Application Explorer files, see Setting Up Application Launcher/Explorer .


Automating Application Launcher or Application Explorer Startup

You can run either Application Launcher or Application Explorer on a workstation. Do not run both on the same workstation.

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 with SP4 or later) or the Novell Client for Windows NT/2000/XP/XP (version 4.8 with SP4 or later) is installed on the workstation.

  2. To use Application Launcher, 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.

  3. To use Application Explorer, 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.

You can also add Application Launcher or Application Explorer to the Windows Startup folder. This enables Application Launcher/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.