Environment

This property page specifies the workstation environment that Novell^® Application Launcher^TM creates before running the application on the workstation.

Run
Select the application's initial window size: Normal, Minimized, Maximized, or Hidden.

In Hidden mode, the application runs normally without a user interface available. This is useful if you want the application to process something, then go away without user intervention. For example, you could use it for the ZENworks^® Remote Control agent if you don't want it to appear in the taskbar.

Some applications cannot be run in Minimized, Maximized, or Hidden mode. Depending on the application, the initial window size setting might be ignored. For example, calc.exe cannot be run in Hidden mode.

Windows NT/2000/XP
Use these options to specify how applications run on Windows* NT*/2000/XP workstations.

Run 16-Bit Applications in Windows on Windows Session That Is
If you are setting up a 16-bit application to run on Windows NT/2000, specify either a shared or separate Windows on Windows (WOW) session. To run on Windows NT/2000, 16-bit applications must run in a Virtual DOS Machine (VDM) that emulates Windows 3.1 functionality. 16-bit Windows applications can run in their own separate WOW sessions or they can share a WOW session with other 16-bit applications.

Sharing a WOW session saves memory and allows applications to use DDE or OLE to communicate with other applications in the same WOW session. Running an application in its own separate WOW session allows for more robust operation because the application is isolated from other 16-bit applications. Because some applications do not run properly in a separate WOW session, the default option is to run the 16-bit Windows application in a shared WOW session.

Executable Security Level
Select one of the following security levels for the application:

• Run Normal: The application inherits the logged-in user's credentials. For example, the application has the same rights to the registry and the file system as the logged-in user.
• Run As Secure System User: The application inherits the workstation's credentials and is run as a Windows NT/2000/XP process. For example, the application has full rights to the registry and the file system. No user interface is available and the application is only visible in the Task Manager. This option is useful when distributing applications that require full access to the workstation but require no user intervention, such as a service pack or update.
• Run As Unsecure System User: This option is the same as Run As Secure System User, with the exception that the user interface is available. This means that the application can display dialog boxes and prompt the user for information if necessary. In return, the user will have the ability to do whatever that application offers on the workstation. For example, if you specify regedit.exe as an unsecure system user, the workstation's user can edit any registry values.

In a terminal server environment, you should not use the Run As Secure System User and Run As Unsecure System User options if users are running Application Launcher in a terminal server client session. Doing so causes the NAL Service (running on the terminal server) to launch the application. Because the NAL Service runs as a System user, the launched application displays only in the terminal server's Task Manager (for Run As Secure System User) or on the terminal server's desktop (Run As Unsecure System User). It does not display in the users' terminal server client sessions.

Clean Up Network Resources
Check this option to remove network connections, drive mappings, and port captures that were established for running the application. If this option is not selected, the network resources remain in effect. If the resource is already in use when Application Launcher starts the application, it is not cleaned up until all other distributed applications are finished using it. If distributed applications are still running when Application Launcher is terminated, the allocated resources remain intact.

This option applies only if the Application object is configured to run an application, meaning that there is a file listed in the Path to File option (Run Options tab > Application page). If the Application object is configured to install an application (Run Options tab > Application page > Install Only option), this option does not apply.

Monitor Module Name
When an application is launched, Application Launcher monitors the executable of the application. When the executable terminates, the process of cleaning up network resources begins. However, it's possible that the executable filename is actually a "wrapper" that sets up environments, runs other executables, and then terminates. If Application Launcher monitors the wrapper executable, it might prematurely start cleaning up network resources before the application has terminated. Consult your application documentation about whether the application uses a wrapper executable. If it does, find out the name of the module that remains running. Type this name (without the extension) in the text box provided.

A trademark symbol (^®, ^TM, etc.) denotes a Novell trademark. An asterisk denotes a third-party trademark. For information on trademarks, see Legal Notices.