20.6 Application Explorer Command Line Switches

The following command line switches can be used when starting Application Explorer.

Application Explorer can be started by using the nalview.exe or naldesk.exe files, located in the workstation's c:\program files\novell\zenworks directory. These switches work with both files.

Table 20-2 Application Explorer Command Line Switches

Switch

Description

/nd

EXAMPLE: nalview /nd

Skips the warning dialog box that appears when a dial-up connection is detected.

/ns

EXAMPLE: nalview /ns

Skips the initial splash screen.

/restrictonline=0|1|2|3

EXAMPLE: nalview /restrictonline=1

Determines the Application Launcher state (online or offline) as eDirectory connections become available. This switch is supported only when eDirectory authentication occurs directly through the ZENworks Desktop Management Agent; it is not supported when eDirectory authentication occurs through the ZENworks Middle Tier Server.

The switch’s four possible values are described below, with each value having both a startup behavior and a running behavior. The running behavior applies when, after initial startup, Application Launcher detects a change in eDirectory connections.

/restrictonline=0

  • At startup: Application Launcher goes into online mode if it detects an eDirectory connection, unless the connection is through dial-up. In that case, Application Launcher prompts the user whether to go online or stay offline.

  • Running: Regardless of the connection type (direct or dial-up), Application Launcher automatically goes into online mode if it detects an eDirectory connection.

    The /restrictonline=0 value results in the same behavior as Application Launcher’s default behavior. In other words, using the 0 value is the same as not using the switch at all.

/restrictonline=1

  • At startup: Application Launcher goes into online mode if it detects an eDirectory connection, unless the connection is through dial-up. In that case, Application Launcher stays in offline mode.

  • Running: Same as the startup behavior. Application Launcher goes into online mode if it detects an eDirectory connection, unless the connection is through dial-up. In that case, Application Launcher stays in offline mode.

/restrictonline=2

  • At startup: Value not used at this time.

  • Running: Value not used at this time.

/restrictonline=3

  • At startup: Application Launcher goes into online mode if it detects an eDirectory connection, unless the connection is through dial-up. In that case, Application Launcher stays in offline mode. Same startup behavior as /restrictonline=1.

  • Running: If Application Launcher started in online mode, it remains in online mode as long as an eDirectory connection is available. If Application Launcher started in offline mode, it remains in offline mode even if an eDirectory connection becomes available.

/singletree="tree"

EXAMPLE: nalview /singletree=nov

Reads the specified eDirectory tree only, regardless of any other trees the user might be authenticated to. This option applies only to user-associated applications, not workstation-associated applications. For example, assume that the workstation has a Workstation object in TREE1. The user authenticates to TREE2 and starts Application Launcher against TREE2 (nalview /singletree=TREE2). Application Launcher displays the user-associated application from TREE2 and the workstation-associated applications from TREE1.

NOTE:The quotation marks are required only if a space is used in the tree name.