Wise Virtual Composer 6.1 SP4 known issues

Article:DOC2163  |  Created: 2010-05-28  |  Updated: 2010-09-29  |  Article URL http://www.symantec.com/docs/DOC2163
Article Type
Documentation


Description



Issue Workaround, if any
Office 2007 VSA displays the repair window when being loaded into Workspace Composer. This occurs in applications that have advertised shortcuts that are set to install when the installation is launched.

 

This does not impact functionality. The package can be used normally after the repair window closes.

Upgrade packages are often much larger than the original package. This occurs due to duplicate versions of the same file being stored. The package size is all that is affected; delta streaming will not send blocks unchanged between the versions contained in the package.
When Compiling an XPF that has either a postActivate or preActivate

Event, those events are launched during the compile process.

Check scripts for any tasks that might cause issues on the packaging computer. After the package compiles you can undo any changes on the packaging workstation.
Default.xpt template can’t be opened. The default.xpt template is a system template and cannot be edited. See the help for details on creating a template.
If an invalid file is passed to the command line interface for XPF conversion, a crash occurs. Validate the file format before passing to the command line interface for conversion.
Office 2007 VSA displays the repair window when being loaded into Workspace Composer. This occurs in applications that have advertised shortcuts that are set to install when the installation is launched.

This does not impact functionality. The package can be used normally after the repair window closes.

Upgrade packages created for Adobe Reader are twice the size of the original Adobe Reader package. The package size is all that is affected; delta streaming will not send blocks unchanged between the versions contained in the package.

This is expected behavior.

Templates are not added to the Templates tab by default when a package is created with the Package Wizard. Compile the package in order to save the template.
XPT template files are not associated until the application is launched for the first time. Start Wise Virtual Composer to register the file associations.
Adding a script to the Meta Folder results in the script consuming twice the disk space for some events. This occurs because Wise Virtual Composer makes a second copy of the script for the Meta folder. This increases the size of the package and the size of the initial

Streaming download, but does not impact functionality.

Streaming a Microsoft Project 2007 package to Windows 7 might require the creation of an additional folder. If the package was created on Windows XP you might be missing the following folder that is required on Windows 7:
C:\Program Files\Common Files\ODBC\Data Sources

This folder can be added directly to the virtual layer or created using a PreInstallation event script. Creating the package on Windows 7 also resolves this issue.

The refresh layer option on the compile page removes changes made to the application shortcuts page. This occurs because the values read when the layer is refreshed overwrite the values you selected on the application shortcuts page.

If you need to update the shortcuts and refresh the layer, compile once with the refresh layer option selected. Then, update the shortcuts and compile the package again with refresh layer not selected.

Compiling a new package from an existing XPF generates a new application GUID. If you intend to use the XPF you imported as a starting point for a new package, you might want a new GUID generated. However, this process cannot be used to create upgrade packages. The original package folder is required to retain the package GUID to create upgrade packages.
Upgrade packages require the package folder for all previous version to be available in the original location during compile. You can verify the original locations using the package path and original package path values. We recommend backing up the entire package folder for each package to ensure you can successfully create upgrade packages at a later time.
Certain applications require packaging to occur on same operating system version as the target operation system. If you encounter errors when streaming to a different operating system than what was used for packaging, you should create a package for each operating system in use in your environment.

On the supported OSs page in Wise Virtual Composer, select the operating system for each package. Workspace Streaming can automatically filter the list and show only version supported on the operating system in use on the endpoint.

 

 


Legacy ID



53153


Article URL http://www.symantec.com/docs/DOC2163


Terms of use for this information are found in Legal Notices