User manual NOVELL ZENWORKS APPLICATION VIRTUALIZATION 8.0.2 11-2010

[. . . ] novdocx (en) 16 April 2010 AUTHORIZED DOCUMENTATION User Guide Novell® 8. 0. 2 ZENworks Application Virtualization November 30, 2010 www. novell. com ZENworks Application Virtualization User Guide TABLE OF CONTENTS 1 Legal Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. 1 2 Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2. 1 2. 2 2. 3 2. 4 2. 5 2. 6 What is a virtual application?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 ZENworks Application Virtualization features overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Do Novell virtual applications require any device drivers?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 How is Novell virtualization different from hardware virtualization?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [. . . ] If this parameter is specified and a sandbox with that name exists, the application will be registered into that sandbox. (See the "Sandbox management" topic in this section for additional details. ) SandboxSpec 6. 2. 6 Updating registration settings Application registration settings can be changed by re-executing the registration command with the desired options: SpoonReg. exe [Option] AppSpec[@SandboxSpec] Parameter /nocache Behavior Disable caching of the specified application (reverses the /cache setting) Enable caching of the specified application (reverses the /nocache setting) /cache 6. 2. 7 Unregistering a virtual application Unregistering a virtual application reverses the registration process, removing the virtual application, Start Menu icons, shortcuts, and file associations. To unregister a virtual application, use the following command: SpoonReg. exe /unregister AppSpec[@SandboxSpec] It is also possible to unregister all applications with the single command: SpoonReg. exe /unregisterall 53 Novell ZENworks Application Virtualization 6. 3 CLIENT PROFILES The SpoonReg command can be applied to the Local, All Users or Roaming Windows profiles. These profiles correspond to the user profiles available on the Windows operating system. It's recommended that the SpoonReg command is applied to the All Users profile whenever possible. 6. 3. 1 The Local profile Each user on a Windows device has a local user profile. Any changes to the local profile affect only that user on that device. The Local profile is the default profile used by SpoonReg if no profile is explicitly specified on the SpoonReg command line. 6. 3. 2 The All Users profile Each device has a single All Users profile. Any changes made to the All Users profile affect all users on the device. To register an application to the All Users profile, execute the SpoonReg command with the /allusers command line flag. You must have administrative permissions on the device to register applications to the All Users profile. 6. 3. 3 The Roaming profile Each user in an Active Directory environment can have a roaming profile which is mirrored to other machines according to directory policy. Typically, the roaming profile is stored on a network server and is available from all devices on a network. To register an application to the Roaming profile, execute the SpoonReg command with the /roaming flag. Therefore, the /roaming flag has no impact when used in conjunction with the /allusers flag. Note: Because SpoonReg is applied to specific user profiles, it cannot be used for the LocalSystem account (has no associated profile). 54 Novell ZENworks Application Virtualization 6. 4 SANDBOX MANAGEMENT The SpoonReg tool allows creation and management of one or more virtual environment sandboxes. A sandbox contains all of a virtual application's isolated data and settings as determined by the virtual application's isolation configuration settings. Applications registered to the same sandbox can view and modify each others' virtualized data and settings. By default, all applications are registered into a single default sandbox named Default. In some cases, it may be desirable to group related applications into a sandbox that can be treated as a single management unit. When a sandbox is reset, all of the application content and data stored in that sandbox is purged and reverts back to the default state. 6. 4. 1 Creating a sandbox If no sandbox is specified during registration, the application will be registered to the default sandbox (Default). To create an additional sandbox, use one of the following commands: SpoonReg. exe [Profile] /create [SandboxName] [SandboxPath] SpoonReg. exe [Profile] /c [SandboxName] [SandboxPath] If no path is provided, a default path is created under the AppData folder under the specified profile. 6. 4. 2 Resetting a sandbox Resetting a sandbox reverses all changes made to the sandbox, including any changes to data or settings made by the user. This restores all applications registered to the sandbox to their default state. To reset a sandbox, use one of the following commands: SpoonReg. exe [Profile] /reset [SandboxSpec] SpoonReg. exe [Profile] /r [SandboxSpec] If a SandboxSpec is not supplied, the default sandbox is reset. 6. 4. 3 Deleting a sandbox Deleting a sandbox removes all applications, data, and settings from the sandbox. [. . . ] ProgIds All sub-elements contain settings pertaining to the configuration of the ProgId. IconResource The IconResource sub-element contains an identifier of the icon that is used for the file association. Extension All sub-elements contain settings pertaining to the configuration of the file extensions for the ProgId. The extension attribute indicates the file extension that is associated with the ProgId. [. . . ]