Best Practice for preparing packages for Virtualization and Streaming
You can use the following guidelines to determine what you can and should not virtualize:
What you can virtualize
Most applications can be virtualized. Typical applications include office suites, Internet browsers, media, and spyware utilities.
Applications function normally when virtualized by the Workspace Virtualization Agent.
What you should not virtualize
- Windows operating system components
- Windows operating system patches
- Most drivers that are low level kernel drivers
- Applications that have dedicated drivers (example: Client firewalls)
- All management agents including antivirus software, security scanners, encryption agents, or any Symantec Management Platform Agent
- Data files that you plan to encrypt
- Utilities that are designed to run only in safe mode
Best Practices for creating virtual applications
- Create virtual captures of MSI installations without advertised shortcuts (MSI Property: DISABLEADVTSHORTCUTS)
- Reset a layer before compiling the XPF package.
- Keep 'Active On System Startup' enabled only for the most common applications and applications with drivers. Otherwise disable 'Active on System Startup' and use the SLAM option of the streaming agent instead)
- Clean up layers - remove user data when possible
- Add application specific excludes for known file types
In addition, there are 2 clear, concise Connect articles on Virtual Packaging Best Practices: