The information in this Readme pertains to Novell ZENworks Application Virtualization, which lets you convert applications that run on Microsoft Windows into self-contained virtual applications.
The following information is included in this Readme:
This section describes new features, enhancements, and bug fixes that are part of the ZENworks Application Virtualization 9.0 release.
Application Harvesting through Recipes: ZENworks Application Virtualization 9.0 introduces a new method for packaging applications. After you install all of the applications that are to be virtualized onto a representative machine, Studio scans the machine and finds all the applications that match a recipe list. You can then select the applications for virtualization. Studio harvests the files on the endpoint to build the application.
Desktop Scan: You can scan the local machine for installed applications and match them to the current template list. An administrator can then select from the list of matched applications and virtualize one or more in a single step.
Juke-boxing Support for Streamed Applications: You can have multiple icons (ZENworks or standalone Web URLs) referring to the same streamed content with different triggers.
Offline Support for Streamed Applications: Applications can be launched offline if the application is registered to the desktop and fully cached.
Securing Applications Based on Active Directory Status: You can limit applications so that they run only if the current user is a member of a specified AD domain or AD User Group. This is very useful if you do not have ZENworks Configuration Management 10.x or ZENworks 11.x and you want to control application sprawl.
Custom Shims: ZENworks currently offers a built-in shim that limits applications so that they run only on devices managed by ZENworks. Similarly, ZENworks Application Virtualization 9.0 has introduced an option to limit applications based on user membership in Active Directory. In addition to these two methods, ZENworks Application Virtualization 9.0 now offers the ability to create custom shims and use them with virtualized applications to control application launch behavior. For more information on how to create a custom shim, see the ZENworks Application Virtualization User Guide.
Command Line Launch for Virtual Applications Registered with the Desktop: You can now launch applications registered to the desktop using SpoonReg via the command-line. When registering an application with the desktop using SpoonReg, an administrator can now specify a UID instead of a random one being created. The program creates a launch shortcut that allows for a ZENworks bundle to be created. The ZENworks bundle installs, registers, and launches the virtual applications. This is useful for administrators who need to use the features of SpoonReg that are not available when delivering applications using an MSI, such as custom sandboxes. For more information, see the ZENworks Application Virtualization User Guide.
New Look and Feel: The ZENworks Application Virtualization 9.0 Studio has a new look and feel, similar to ZENworks 11, Vibe, and Novell GroupWise.
The following sources provide information about Novell ZENworks Application Virtualization 9.0:
All application configuration documents and application certificates must be re-created for application streams to work with the ZENworks Application Virtualization 9.0 standalone components. To generate a new certificate and regenerate the configuration files:
In the Advanced section of the ZENworks Application Virtualization Studio, click thebutton to regenerate the application stream configuration files.
To generate a new site license certificate, click.
In the Application Certificates dialog box, click.
Specify the following information in the fields:
Organization: The organization name.
Unit: The user or unit name.
Allowed Portal Hosts: The allowed host names of the servers from which the application will stream.
Clickto request the site license certificate, then save the certificate to a desired location.
Click thebutton to regenerate the application stream configuration files again.
ZENworks Application Virtualization versions 8.x and 9.0 always run side-by-side on a device. The ZENworks Application Virtualization 9.0 installation does not change previous installations in any way. However, if you open a virtual application and save it in version 9.0, it should not be subsequently used with version 8.x.
This section contains information about issues that might occur in ZENworks Application Virtualization:
There are several issues in ZENworks Application Virtualization 9.0 regarding support for virtualized applications on 64-bit Windows machines.
Running a virtualized 32-bit Microsoft Office 2003 Professional Enterprise application is not supported on the following 64-bit platforms:
Windows Server 2008 64-bit
Windows 7 64-bit
Windows Vista 64-bit
The application has been removed from the default application creation template on machines running the 64-bit platform.
Running a virtualized 32-bit Microsoft Office 2007 application on a 64-bit platform also fails.
Application virtualization of the Citrix ICA Demo 188.8.131.52 application is not supported on the Windows XP 64-bit platform.
A virtual application might fail if you build it by using theoption on the ZENworks panel of the control console, then copy the application to a machine where the ZENworks Configuration Management Agent is installed. You see the following error when you launch the virtual application:
This application can only be run on devices registered with a ZENworks zone.
Workaround: To avoid this issue, make sure that you save the ZENworks configuration settings (that is, the changes made to the ZENworks panel of the console and stored in the *.xappl file) before you build the application. To save changes, click > .
If you are running virtual email client applications such as Novell GroupWise and Microsoft Outlook Express together on a single machine, they might not work properly.
The following issues in ZENworks Application Virtualization 9.0 relate to its use with various Web browsers.
Although you can build the Virtual Internet Explorer 9 on all versions of Windows, you might encounter errors while launching the application because it is supported only on Windows Vista and Windows 7.
If you are using a virtual Internet Explorer 7 browser, it can only be harvested from x86 platforms. Currently, harvesting Internet Explorer 7 is not supported on x64 platforms.
(Fixed in v9.0.1)If you are using SpoonReg to register Internet Explorer applications that are built by using the template wizard or desktop scan, the Start Menu entries do not include the version number of the browser.
Workaround: Use only the template wizard and not the desktop scan to build an Internet Explorer application. After the configuration is loaded into the ZENworks Application Virtualization Studio, update the Start Menu items to the desired values in the Setup section of the ZENworks Application Virtualization Studio.
There are some known issues with the integration of Microsoft Office and the Novell GroupWise mail client. These behaviors are in accordance with the design specifications for these applications.
On a Windows XP x64 device, when you right-click, the installer attempts to load Microsoft Outlook Express instead of GroupWise.
On a Windows Vista/7 (x86, x64) device an existing user will have GroupWise as the default mail client. All additional users need to go through theif they choose to make GroupWise the default mail client.
Virtualized Microsoft Outlook 2010 x64 crashes on startup when GroupWise is the default mail client, because the Microsoft Office x64 virtual application tries to load the x86 MAPI dll file to which GroupWise is already registered.
Microsoft Outlook 2003 displays the following error message on startup when GroupWise is the default mail client: unable to resolve recipient. You can ignore this error message and proceed.
GroupWise freezes on rare occasions during the MailTo process. GroupWise is launched in the task list, but the mail dialog box never appears. This issue is observed on Windows XP x64 devices.
Microsoft Office 2010 and Office 2007 cannot be registered in the same sandbox because they cannot share the registry.
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.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2009-2012 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.