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:
The primary focus in the ZENworks Application Virtualization 8.0.4 release is to address bug fixes.
Previously, administrators had to manually edit the XAPPL file to define the search paths for application components. As part of this release, the ZENworks Application Virtualization Studio includes new functionality that enables an administrator to define the search paths and the precise locations for SVMs to enumerate when launching the application. However, this is not the same as embedding the component into the application definition.
Some of the issues that were discovered in the original shipping version of ZENworks Application Virtualization have not yet been resolved. The Readmes for the previous releases have been updated to indicate which issues have been fixed in this release. The following sources provide information about Novell ZENworks Application Virtualization 8.0.4:
For details related to prerequisites for creating Microsoft Office 2010 virtual applications, see TID 7007402 in the Novell Support Knowledgebase.
When you upgrade from a previous version of ZENworks Application Virtualization to version 8.0.4, ensure that you also update the Spoon Sandbox Manager or Spoon plug-in.
You also need 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.
Generate a new certificate by selecting, then regenerate the application stream configuration files by using the button.
This section contains information about issues that might occur in ZENworks Application Virtualization:
There are several issues in ZENworks Application Virtualization 8.0.4 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 126.96.36.199 application is not supported on the Windows XP 64-bit platform.
The virtualized Citrix client application might not appear in the list of Configuration Wizard templates for a Windows 7 device if there are network issues, because the application template is dynamic.
Workaround: Relaunch the ZENworks Application Virtualization 8.0.4 Configuration Wizard to list the Citrix ICA Demo 188.8.131.52 application.
Use the instructions provided in this section while working with ZENworks Application Virtualization 8.0.4 and ZENworks Configuration Management.
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 > .
The following issues in ZENworks Application Virtualization 8.0.4 relate to its use with various Web browsers.
After you create a virtual application, Safari 4.0.4 or Safari 5.0 might fail. If the virtual application is not configured correctly, use the default template or follow the steps provided below to build the application.
Workaround: Make sure that you follow these steps when you build Safari as a virtual application:
Select(Option 2) in the Configuration Wizard.
Capture the Before Snapshot.
Install the Safari application.
Capture the After Snapshot.
Select the Startup file as @PROGRAMFILES@\Safari\Safari.exe instead of the default (Multiple Files).
Save the configuration, but do not build the virtual application.
In the saved configuration, modify the .xappl configuration file by setting the enhancedDEPCcompatibility attribute to True.
Build the virtual application file.
Close ZENworks Application Virtualization, then delete the Safari sandbox.
Run the virtualized Safari application.
The Silverlight virtual component in an Internet Explorer or Firefox virtual application might fail to work.
Workaround: Do the following:
Build the Internet Explorer or Firefox virtual application by using the Configuration Wizard template.
Build the Silverlight virtual component as an .svm file.
Copy both the Internet Explorer/Firefox virtual application and the Silverlight virtual component to a single folder.
In the ZENworks Application Virtualization file system, remove the ni.dll files and the agcp.exe file. Save the configuration before building the virtual component.
To load the Silverlight components, reopen the Internet Explorer or Firefox virtual application.
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.
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 64-bit 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 64-bit virtual application tries to load the 32-bit 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 64-bit 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-2011 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.