I would like to better understand Symantec version naming conventions, and all Symantec products following the same one! When told me a version 6.1 SP7, I do not naturally guess the 6.4.1266 was the same one... All the same, I can understand not able to guess the 1266, I can tell you, I was expecting something like 6.1.4.1266 instead! e.g.: Currently Symantec Workspace Streaming Agent (SWS) 6.1 SP7 is: 6.4.0.68 Symantec Workspace Virtualization Agent (SWV) 6.1 SP7 is: 6.4.1266 Notice ...

Hi, I have seen something that can be usefull and powerfull if it will be added in the next release of SWS suite:   When I would like to stream an application who as pdf link and Adobe is not streamed too, it show me shortcuts without icons, not so fine. Is it possible to link the non streamed application directly to the icon of the application dependence steam? Example: Before any package are streamed: After the fist package is streamed it miss only the adobe reader package to ...

Hello, I would like to have some kind of SVSUser (a capped version of SVSAdmin) so "normal" users (i.e. not administrators) can do the following: - import, reset and delete layers In this manner we can deploy a computer with all the basic layers (office, acrobat and so on) and have a layer library in a network share. If the user want to "install" some software he can import itself the layer and use the software. When he is done with the software, he can delete the layer ...

Currently SWS is primarily tuned towards user based entitlements because in most instances it's the user who is going to use an application. As you may have seen in several of our presentations, the operating system, application, data and profile is meant to "follow the user". The reasoning for this is except for certain scenarios such as lab environments, task based machines, hardware dependent apps, all others are more suited for user based provisioning. Now there are ...