Endpoint Virtualization Ideas

Show:

idea RSS

Products:

Topics

Status: On Roadmap

Now that layer definitions have arrived I think that we should create a "Layer Definition Exchange" on Connect. It will be a one-stop place to find completed layer definitions. This will really help everyone find the information that they need to really get full use out of this great new tool. What do you think?

Suggested: 09 Apr 2010 by trb48 | 1 comment - last comment 20 May 2013 by Joseph_Carson

Hi all, I have some ideas for the SWS Console according to a best user control of the packages. 1) It would be good to know in a short view the server status of the package exemple on the first print screen modified. (SWS_Console capture) 2) It would be good to see the size of the package (.xpf) and the size after stream for exemple in the package details. (Details_Package capture) 3) It would be excellent that when you click on back button of a package view to go to the previous page and ...

Suggested: 22 Dec 2011 by gsalerno | 1 comment - last comment 20 May 2013 by Joseph_Carson

Hum, not sure for MSI this can be possible, and useful... As the interested is to start the program before the end all files local installed. But for portable EXE, Like ThinApp packages, it is full sense to support, and probably not a big difficult.

Suggested: 19 Sep 2011 by Pascal KOTTE

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 ...

Suggested: 14 May 2011 by Pascal KOTTE | 1 comment - last comment 28 Nov 2012 by ManelR

The idea here is to package the SVS runtime too along with .VSA Archive. Also instead of .VSA, make it as a single self-executable .EXE / .COM file where all the runtime/ temporary files are sandboxed. The biggest plus of this approach is you need not depend up the presence of SVS runtime in every client machines & need not worry about any traces / leftovers. This approach will make all the existing Applications truly portable. May be virus infections can be bloced if ...

Suggested: 05 May 2011 by Swami

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 ...

Suggested: 13 Apr 2011 by gsalerno

I'd like to see the Symantec Workspace Streaming Console improved so I can use it to push out agents to new PCs and also to control and update any settings on deployed agents. I also feel it needs a re-design, it's a very difficult console to naviagate, perhaps make it an mmc based console.

Suggested: 24 Feb 2011 by dpowell2 | 2 comments - last comment 21 Apr 2011 by emilioVRT

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 ...

Suggested: 23 Feb 2011 by ManelR | 1 comment - last comment 24 Feb 2011 by erikw

Hello, Sometimes, when you try to capture an application that uses some windows services to install something, there are files and registry entries that aren't captured in the layer. If you export this layer to another computer it won't work because of the missinge files/registry entries that has been created in the base in the capture workstation. Well, I have this idea. Why not having an option of creating an snapshot before of the installation and at the end of the capture process ...

Suggested: 23 Feb 2011 by ManelR

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 ...

Suggested: 18 Feb 2011 by SK | 2 comments - last comment 18 Feb 2011 by SK

Show Listings per page

Endpoint Virtualization Ideas

Links