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
Best Practices for creating virtual applications
In addition, there are 2 clear, concise Connect articles on Virtual Packaging Best Practices:
http://www.symantec.com/connect/articles/symantec-workspace-virtualization-packaging-best-practices-part-1
http://www.symantec.com/connect/articles/symantec-workspace-virtualization-packaging-best-practices-part-2
Just for information:
When you create a application package in Virtual Composer, it sets the Activate on System Startup on the layer. It do not matter if you select a allready existing layer or create a new.
You have to open virtualization admin from virtual composer and remove the tick from Activate on System Startup and then press save in virtual composer before you compile the package, or else the package will have the Activate on System Startup enabled.
Kind Regards Martin Ringblom Hunderup
@Jospeh_Carson,
Okie doke. Thanks for writing back so promptly and answering that question. I look forward to seeing that implemented!
Hi
@Palvaran,
At this time it is not possible to modify the Layer properties once provisioned on the Streaming Server, once provisioned it is only possible to modify the streaming layer properties like Offline, OS Plaltforms etc... To modify the Layer Properties you would need to do this via Virtual Composer and recompile.
That is a great idea for a future feature and I am currently creating that feature request for a future release. Many thanks for raising that .
@ateamrh,
That is a good point that for those who start with SMP before moving to streaming you would need to recompile anyway to creae the xpf which is used for streaming. As part of the next release of SMP Virtual Composer will now be included so the for future virtual application creation it would be good to start with Virtual Composer. I will be creating a few short video demo's for both New Packager and Advanced packager best practices.
Many thanks for the feedback thus far and please do keep them coming. It is greatly appreciated.
Joseph Carson - Product Manager
I would also like to know that, since a lot of customers uses both streaming and SMP to push out packages.
Normally they start with SMP and then move the package to Streaming, which means we have to recompile the package before upload to streaming.
Jospeh, that is great information. I just figured out that I was not consistently removing the active on system startup from all of our layers that we were publishing. Thanks for that tip.
On a side note, once a package has been imported into the Streaming Server, is there a way to modify that setting or is the only option to recompile and republish?