What is the impact of attempting to manage a streamed SVS package using the Symantec Workspace Virtualization (SWV) – SVSCMD.exe and Symantec Workspace Streaming (SWS) Agent - AppMgrCmd.exe command line utilities?
Until SWS 6.1. packages were streamed completely to the streaming agent cache. From 6.1 the optimized layer alone is streamed to the cache where as all the application files reside in the re-direct area. Meaning, the files are directly streamed to the layer (i.e. inside C:\FSLRDR\).
For example, what happens with the SWS cache folder _AC when a streamed layer is deleted using the SVSCMD.exe command line?
While creating an SVS package the streaming composer will use the optimized layer residing inside the as_svsfiles_opt file system area. Once the package is ready and delivered through the streaming agent to the endpoints the SWS cache folder will have the following structure %ROOT%\_AC\<PACKAGEID>\. Here the _AC refers to the SWS Streaming Agent Cache folder which stores all the application executables and required files.
as_svsfiles: The actual layer.
as_svsfiles_opt: The optimized layer used by the streaming agent.
SVS_INSTALL: This will be empty.
All the files inside the package will be delivered to C:\FSLRDR\2\.
Once the layer is deleted using the SVS Admin Tool or the SVSCMD command line tool the contents of the _AC i.e. SWS Cache is still intact (actual and the optimized layer) but the contents of C:\FSLRDR\2 i.e. the re-direct area will be completely empty. This includes removal of application shortcuts and configuration files as well that are commonly shared.
The best practice is to remove any package from Application Manager GUI or the command line AppMgrCmd.exe, since all the streamed content across the file system, registry and re-direct area is completely removed .This results in a graceful streaming session in case a re-streaming is required.
Imported Document Id