ZENworks Application Virtualization 10.1 Readme

December 2013

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:

1.0 What’s New in Version 10.1

This section describes new features, enhancements, and bug fixes that are part of the ZENworks Application Virtualization 10.1 release.

Direct publishing of applications from ZENworks Application Virtualization Studio to ZENworks Application Virtualization Server: ZENworks Application Virtualization 10 introduced the ZENworks Application Virtualization Server component, which provides a quick way to deliver your applications to devices securely over the web, using a very small plugin. With ZENworks Application Virtualization 10.1 you can use the Publish to ZAV Server feature to quickly publish applications that you build from ZENworks Application Virtualization Studio.
Updated End User Portal: ZENworks Application Virtualization provides an updated end-user experience for the application launch portal. Using the new portal, when you click on an application, you can see the description and versions available. This allows you to offer multiple versions of the same application while maintaining a clean, easy to use experience.
Updated Desktop Interface: The end-user plugin has also been updated to provide capabilities similar to the portal. This gives you the ability to interact with ZENworks Application Virtualization without having to access the web portal. This includes the ability to see the available versions of each application, when multiple versions exist.

The plugin continues to provide sandbox synchronization so that when a user makes changes to the applications they launch through the plugin, the changes are automatically synchronized with the server.
Web Tags: Web tags allow you to specify a simple name for the application so that it can be accessed quickly and easily from a browser. This makes it easy to point a user to a specific application when sending an email or posting a link to the application, rather than having the user access the main page.
Admin Enforced Desktop Registration: The administrator now has the ability to force an application to register or prevent the user from registering with the start menu and desktop. When the Desktop Registration option is enabled and the Register on launch is enabled, the application file extensions, start menu shortcuts, and desktop shortcuts are all registered with the desktop the first time the user runs the application. This makes it easier for the user to use the application going forward.
Shared Sandboxes: When shared sandboxes are enabled, all versions of a particular application share a common sandbox. This ensures that user customizations are available across all versions of the application. For instance, if you enabled this feature on the Firefox application, and had ten versions available, then, when the user changed the home page for one version, it would be the same for the others, as long as the newer versions look in the same location in the file system or register for the home page option.

2.0 Product Documentation

The following sources provide information about Novell ZENworks Application Virtualization 10.0.1:

3.0 Understanding the Upgrade Requirements

All application configuration documents and application certificates created with ZENworks Application Virtualization 8.x or 9.x must be re-created for application streams to work with the ZENworks Application Virtualization 10.x standalone components.

To generate a new certificate and regenerate the configuration files:
1. In the Advanced section of the ZENworks Application Virtualization Studio, click the App Config button to regenerate the application stream configuration files.
2. To generate a new site license certificate, click Advanced.
3. In the Application Certificates dialog box, click Request Certificate.
4. 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.
5. Click Request to request the site license certificate, then save the certificate to a desired location.
6. Click the App Config button to regenerate the application stream configuration files again.
ZENworks Application Virtualization versions 8.x, 9.x and 10.x always run side-by-side on a device. The ZENworks Application Virtualization 10.x installation does not change the ZENworks Application Virtualization 8.x or 9.x installations in any way. However, if you open a virtual application and save it in version 10.x, it should not be subsequently used with version 8.x or 9.x.

4.0 Known Issues

This section contains information about issues that might occur in ZENworks Application Virtualization:

4.1 An error message is displayed when you create a virtual application using ZENworks Application Virtualization Studio and try to publish it to ZENworks Application Virtualization Server

When you create a virtual application using ZENworks Application Virtualization Studio and try to publish it to the ZENworks Application Virtualization Server, you receive the following Publish Failed error:

An error occurred while uploading the virtual machine. There may be a network issue or you may require more storage on your Spoon.net account.

Workaround: Stop and restart the ZENworks Application Virtualization Server services. For more information, see the Troubleshooting section in the ZENworks Application Virtualization User Guide.

4.2 Running a 32-bit Microsoft Office Virtualized Application on the Windows 64-bit Platform Is Not Supported

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.

4.3 Virtual Applications Built with the Require ZCM Agent Option Might Not Launch

A virtual application might fail if you build it by using the Require ZENworks Configuration Management Agent to be installed on workstation executing the virtual application option 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 > Save Configuration.

4.4 Virtual Email Clients Do Not Work Together on a Single Machine

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.

Workaround: None

4.5 Virtualizing an iFolder through a Snapshot

When you are virtualizing the iFolder 3.8 through the snapshot method, make sure to include the Visual C (v9.0.21022.8) and .Net 2.0. For information on taking snapshots of virtual applications, see Section 2.7 - Snapshotting Applications in the ZENworks Application Virtualization User Guide.

After taking the snapshot and before building the application, make the following modifications in the Settings tab of the ZENworks Application Virtualization application.

Enable Always launch child processes as current user.

Child processes launched by the virtual machine have reduced privileges by default. Enabling the Always launch child processes as current user option provides child processes with the same level of privileges as the virtual machine’s root process.
Turn off Autostart for any Services (.NET).

For information on Run-Time Virtualization arguments, see Section 8.7 - Modifying Virtualization Behavior at Run-Time in the ZENworks Application Virtualization User Guide.

You might see the following error:

Unable to start xsp webservice, iFolder not able to work, restart the application.

Workaround: If you see this error:

Delete the following folders from the virtual file system:
- In Windows, delete pss.
- In Programs, delete Internet Explorer and iFolder3.
- In Local Application Data, delete simias.
- In Application Data, delete Downloaded Installations, Microsoft, and simias.
- In Application Data > iFolder, delete simias10, and set the iFolder to FullIso.
Save the configuration file.
Rebuild and then launch the virtual application.

For more information on the snapshot process and building an application, see Section 6 - Walkthroughs in the ZENworks Application Virtualization User Guide.

4.6 Issues Related to Web Browsers

The following issues in ZENworks Application Virtualization 9.0.1 relate to its use with various Web browsers.

4.6.1 Internet Explorer 9 might fail to launch on platforms other than Windows Vista and Windows 7

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.

4.6.2 Harvesting Internet Explorer 7 Is not supported on 64-bit Windows managed devices

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.

Workaround: None

4.7 Integration Issues with Microsoft Office and Novell GroupWise

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 SendTo, 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 the Default Programs Menu if 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.

4.8 Coexistence Issues with Microsoft Office 2007 and Microsoft Office 2010

Microsoft Office 2010 and Office 2007 cannot be registered in the same sandbox because they cannot share the registry.

5.0 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.

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-2013 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.