User manual NOVELL ZENWORKS APPLICATION VIRTUALIZATION 8.0.1 8-20-2010

[. . . ] novdocx (en) 16 April 2010 AUTHORIZED DOCUMENTATION User Guide Novell® 8. 0. 1 August 20, 2010 ZENworks Application Virtualization www. novell. com ZENworks Application Virtualization User Guide novdocx (en) 16 April 2010 Legal Notices Novell, Inc. , makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. , reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. , makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. , reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. [. . . ] This comes as an add-on to Microsoft's Active Directory. The simplest way to deal with the virtual application management is by creating a logon script that registers the virtual applications for a particular group in the organization. You would do this under User Configuration > Windows Settings > Scripts in the Group Policy Object Editor. You might add the following logon script for the accounting group: \\VirtualAppServer\Tools\SpoonReg. exe \\VirtualAppServer\AllVirtualApps\Excel. exe \\VirtualAppServer\Tools\SpoonReg. exe \\VirtualAppServer\AllVirtualApps\Firefox. exe \\VirtualAppServer\Tools\SpoonReg. exe \\VirtualAppServer\AllVirtualApps\AcrobatReader. exe Whereas you might add the following for the graphic design group: \\VirtualAppServer\Tools\SpoonReg. exe \\VirtualAppServer\AllVirtualApps\AdobeIllustrator. exe \\VirtualAppServer\Tools\SpoonReg. exe \\VirtualAppServer\AllVirtualApps\Firefox. exe \\VirtualAppServer\Tools\SpoonReg. exe \\VirtualAppServer\AllVirtualApps\AcrobatReader. exe 6. 5. 8 Linking the GPO to the OU Once you have set up the OU and the GPO, you simply have to link them through the Group Policy Object Editor. After they are linked, any users that are put into that OU will have the linked GPOs applied when they logon. All of their virtual applications will appear when they logon to any machine on the domain where the GPO applies. Note: SpoonReg has many other capabilities that can be applied in the GPO logon script, such as unregistering applications or registering applications to a specific sandbox. 6. 5. 9 Scenario 2: Using Startup Scripts with GPO's to deploy virtual applications This section will describe using Startup Scripts to deploy virtual applications to the All Users profile on a host system. 6. 5. 10 Create a GPO with the Startup Script For the purposes of virtual application deployment we can configure the GPO to run the necessary SpoonReg commands to register a given set of virtual applications to the All Users Profile. This will allow any user who logs into a host system to have access to the registered virtual applications. 58 Novell ZENworks Application Virtualization Start by creating a new GPO with the Group Policy Management Console (GPMC): · · · · · · · · Open the GPMC Right-click on the OU that you want to link a GPO to Select Create and Link a GPO Here and give it a name Right-click the GPO and select Edit. This will open the Group Policy Object Editor Navigate to Computer Configuration > Windows Settings > Scripts Open the Startup item Click Show Files In the directory that is displayed by the Show Files button, create a . bat file. This file will serve as the Startup Script that will deploy your virtual applications to all the computers in the specified OU. Use these samples as a guide to create the startup script: Sample 1. Register virtual applications to the default sandbox in the All Users profile: \\VirtualAppServer\Tools\SpoonReg. exe /allusers \\VirtualAppServer\AllVirtualApps\Excel. exe \\VirtualAppServer\Tools\SpoonReg. exe /allusers \\VirtualAppServer\AllVirtualApps\Firefox. exe \\VirtualAppServer\Tools\SpoonReg. exe /allusers \\VirtualAppServer\AllVirtualApps\AcrobatReader. exe Sample 2. Register virtual applications to the specified sandbox in the All Users profile: \\VirtualAppServer\Tools\SpoonReg. exe /allusers /c sandboxname \\VirtualAppServer\Tools\SpoonReg. exe /allusers \\VirtualAppServer\AllVirtualApps\Excel. exe \\VirtualAppServer\Tools\SpoonReg. exe /allusers \\VirtualAppServer\AllVirtualApps\Firefox. exe \\VirtualAppServer\Tools\SpoonReg. exe /allusers \\VirtualAppServer\AllVirtualApps\AcrobatReader. exe Once the Startup Script is created, add it to the GPO: · · · · · · · · Navigate to Computer Configuration > Windows Settings > Scripts in the GPMC Open the Startup item Click Add Click Browse Select the Startup Script that was created Click Open Click OK Click OK 59 Novell ZENworks Application Virtualization 6. 6 DEPLOYING VIRTUAL APPLICATIONS USING MSI SETUP PACKAGES Novell allows virtual applications and components to be deployed using legacy MSI setup package technology. 6. 6. 1 Create MSI setup packages directly within ZENworks Application Virtualization ZENworks Application Virtualization can be used to create standalone MSI packages directly within the ZENworks Application Virtualization environment. Generated MSI setup packages can include Start Menu items, desktop shortcuts, file associations, and other custom shell integration behaviors. Deployment using generated MSI packages is appropriate in situations where existing MSI package deployment mechanisms are in place, or for deploying applications with shell integration without the SpoonReg Virtual Desktop client tool. Virtual application and component shell integration settings are shared between MSI- and Virtual Desktop-based deployment, enabling easy migration between deployment models. Refer to the section "Building MSI setup packages" for more information on the creation of MSI setup packages. 6. 6. 2 Deploy virtual applications into legacy MSI setup packages ZENworks Application Virtualization also supports deployment of virtual application executables into legacy MSI setup packages. 6. 6. 3 Import legacy MSI setup packages ZENworks Application Virtualization supports one-click import of legacy MSI setup packages into the ZENworks Application Virtualization environment. Following import, the application can be customized and deployed as a Novell-based virtual application or SVM. 60 Novell ZENworks Application Virtualization 6. 7 DEPLOYING VIRTUAL APPLICATIONS USING MICROSOFT TERMINAL SERVICES REMOTEAPP This section describes how to deploy Novell virtual applications using Microsoft Windows 2008 Terminal Services RemoteApp server. 6. 7. 1 Terminal Services RemoteApp Terminal Services RemoteApp is a server-side program that provides end-users remote access to applications on a terminal server. Applications configured with TS RemoteApp appear as though they are running locally on the user's machine. End-users can run RemoteApps side-by-side with local programs or other RemoteApps. To utilize virtual applications created in ZENworks Application Virtualization with Microsoft TS RemoteApp: · On the TS RemoteApp server, open the TS RemoteApp Manager and choose Add RemoteApp Programs by right-clicking inside the RemoteApp Programs list or through the Action drop down menu. Click Browse and select the virtual application executable. After the virtual application is added to the list, select it and click Properties. [. . . ] The verb attribute indicates the verb value. The arguments attribute indicates the arguments passed to the target of the verb at runtime. The default attribute denotes whether this verb is the default verb (True) or not (False). 103 Novell ZENworks Application Virtualization 10 TROUBLESHOOTING This section describes the most common configuration errors that occur when using ZENworks Application Virtualization. If you encounter a problem with a virtual application, please carefully read this section or query the online knowledge base before using other support options. [. . . ]