What is the relation between SWV and CMS SP2 MP1?
Client Management Suite includes the Symantec Workspace Virtualization plugin for distribution to the Symantec Management Agent.
Features in the CMS product include the ability to distribute software into a virtual layer using both policies and tasks. Additionally, CMS includes tasks that can be issued to managed clients that can create, activate, delete, deactivate virtual layers.
SWV paired with User-based policies can give you a mechanism to deliver software easily to a user rather than to a computer.
In addition to what Jesse said above, the Symantec Enpoint Virtualization solution allows you to virtualize and distribute a package through the Symantec Workspace Streaming Server.
Hi Jesse A,
If I want to do virtualizations of any software then is it possible to do that with CMS?
Thanks & Regards,
Yes, you can create a software entry into your Software Catolog that will allow you to distriubute software to either the host of virtual layer.
Can you please share the step how I can create virtual setup file through Client management suit?
In CMS, you create a software catlog entry, which includes the MSI and the msiexec command line switches, or the virtual package and during the creation of the software delivery policy you specify whether the delivery is to the layer or to the host OS is the layer is not installed.
Hi Mark. Miller,
Thanks to response,
Can you please share any document which includes the entire Step to do the virtualizations through Client management suit 7.1 SP2 MP1.1?
Re: SWV paired with User-based policies can give you a mechanism to deliver software easily to a user rather than to a computer.
Can you show me the steps to create the User-based policies? Is it the same as creating the Machine-based policies?
Thanks to response but sorry my questions is different.
If suppose I have Client management Suit (7.1) on one server and I have installed Symantec WorkspaceVirtualizations and Symantec Virtual Composer on other system. Now we are able to create a virtual image of software.
My questions are:-
With the tools you have currently on you machine, yes you can go ahead and create virtual packages. The prerequisites are met.
1. Based on the suites, CMS is a different product from SWS. CMS, or rather NS7.x, has the ability to deploy and manage virtualization layers, but not stream it. SWS, or rather Workspace Streaming, has the ability to manage the exact same virtualization layers as well, but chopping the virtual package up into tiny bits, or streamlets, ala how Youtube delivers a video. In that regard, Youtube chops up a flash video into pieces and then delivers it to you as pieces.
Yes and no. You can use the same virtual packages, but Streaming requires an extra step as you have to use the Virtual Composer to create a wrapper or rather edit it so that it has meta tag information that the Streaming Server can interpret and deliver it out.
2. You can't... yet. NS 7.5 is being worked on at present and will have the ability to stream, but it is not slated to be released until the Fall. Until then, if you want to use Streaming, you must use SWS. Otherwise, you can use the same virtual package and deliver it via NS 7.x.
3. Yes, but you don't want to. While you can install the same product on the same server, there is really not a lot of gain there and can be harmful. SWS uses a seperate database from CMS so right off the bat you need two instances for your Databases. Also, if your NS is being hit with requests from agents and then your Streaming Server is being hit from the same network interface, you are going to saturate your bandwidth, IOPS, CPU, and RAM. I would recommend against doing it unless you are trying to setup a proof of concept to get funding for a project.
4. If you get Endpoint Virtualization, you automatically have all you need in order to create packages. The Admin tool has the ability to capture whatever is happening from a command window along with child processes as well as the ability to parse down and edit the registry. Heck, you can even download a trial of the old SVS product and start working from there.
Remember, "The happiness of your life, depends on the quality of your thoughts."
SWS is not integrated into SMP, so treat it like our Win32 DS product (this can also control SWV).
Both SWS and SW Mgmt Solution include the SWV Agent.
SWS controls SWV via its SWS Agent. CMS can control SWV via its SMA and/or CTA (SWV must be installed with its NS flag).
SWV can also be used as a standalone product.
SWV provides an Admin Tool that allows you to create layers. WPS can also be used to do this.
WVC is included with SWS and allows you to create layers via the SWV Admin Tool (it can also import existing layers), and also alows you to perform more configuration actions to the layer that can be utilised from within a SWS environment. WVC also includes templates for a number of aplications, to aid in layer creation. WVC finally compiles the layer into a SWS package which can then be uploaded to the SWS Repository for deployment via SWS. You can also deploy the raw layers created via WVC via CMS.
Thanks to response.
Please correct me if I am worng with fullform of below one to understand the above sentance.
SMP--->Symantec management Plateform(if I am not wrong then you want to say Client management suit)
SWV--->Symantec workspace Virtulizations
WVC--->Wise Virtual Composer(if I am not wrong)
SWS = Symantec Workspace Streaming
WPS = Wise Package Studio
You have correctly identifed the other three.
Thanks to response,
Can you please elaborate above statement which you have written with full form?
It’s difficult to understand?
Thanks to given the good information’s about both SWS and CMS.I have tried to elaborate the same thing which you have written above, there are still some word which are out of dictionary of mine which I have made in bold.
If I conclude with your statement then SWS and CMS are two different products and there are no relations between them. CMS Suit also having Symantec workspace Virtualizations plug in which are only useful when I have implement SWS
Symantec Workspace Streaming is not integrated into Client management suit, so treat it like our Win32 DS product (this can also control Symantec workspace Virtualizations).
Both Symantec Workspace Streaming and SW Mgmt Solution include the SWV (Symantec workspace Virtualizations Agent).
Symantec Workspace Streaming controls Symantec workspace Virtualizations via its Symantec Workspace Streaming Agent. CMS (Client management suit) can control Symantec workspace Virtualizations via its Symantec Management Agent and/or CTA (Symantec workspace Virtualizations must be installed with its NS flag).
Symantec workspace Virtualizations can also be used as a standalone product.
Symantec workspace Virtualizations provides an Admin Tool that allows you to create layers. WPS (Wise Package Studio) can also be used to do this.
WVC (Wise Virtual Composer) is included with SWS (Symantec Workspace Streaming) and allows you to create layers via the SWV (Symantec workspace Virtualizations) Admin Tool (it can also import existing layers), and also allows you to perform more configuration actions to the layer that can be utilized from within a SWS (Symantec Workspace Streaming) environment. WVC (Wise Virtual Composer) also includes templates for a number of applications, to aid in layer creation. WVC (Wise Virtual Composer) finally compiles the layer into a SWS (Symantec Workspace Streaming) package which can then be uploaded to the SWS (Symantec Workspace Streaming) Repository for deployment via SWS (Symantec Workspace Streaming). You can also deploy the raw layers created via WVC (Wise Virtual Composer) via CMS Client management suit.
Yes, SWS & CMS are two different products; however, both can be used to deploy and managed the SWV Agent. You could even use Run Script tasks to manage SWV without using the built-in tasks. DS 6.9 is also a standalone product which has the ability to manage SWV. SWV can also be used as a standalone product, by the user of the machine that it is installed on, if they have local admin rights to that machine.
CMS & DS 6.9 can both deploy layers, but it will be the complete layer.
SWS deploy's layers via packages that can either have initial blocks streamed and then further blocks when more of the products functionality is required (on-line mode) or all blocks streamed (off-line mode).
I have found for SWS, we have agent Call as SWSA, then what is the use of SWVA (Symantec Workspace Virtualization Agent which I can see in CMS?
SWS uses SWSA to manage SWV. SWSA streams the layers and then uses SWV to import and activate them, etc.
CMS (including DS 6.9 and ealrlier) can deploy SWV and also layers, as well as manage them via policies or tasks.
Deciding how you wish to deliver and manage the layer will determine if you wish to use SWS, CMS or DS.
So if I have to do the WinZip as a Virtualizations software through CMS then What Component I need to install it?
The way I would do it would be to use either SWV Admin Tool directly or via WVC if their is a template, or even WPS.
There is also a tool on Connect that provides templates for itself (not for WVC); however, I cannot remember what its called.
A Managed Software Delivery policy also provides the option to install into a layer; however, that action is run on every machine, and I personaly would not use it, as it is far better to create and test the layer first and then deploy to all machines that require it.
To deploy the layer, you could use DS, SW Mgmt Solution, Task Server or a 3rd Party product.
To stop deploying a layer, you can simply disable its associated policy (this will prevent future deployments and will not stop an install that is currently running).
To stop using SWV altogether, you would first diable all polices/tasks that deploy layers, disbale the install to layer option on any MSD#s that is configured with it, and then uninstall SWV. Obviously, whatever product you used to install SWV, you would need to disable their install policy.
For documentation, please go to our products web page, and select the product you are interested in, as it will give you access to its documentation, etc.
Finally,I have done Software Virtulizations with SWS but Can any one help me out to do that with CMS?