Login to participate
Endpoint Management & Virtualization ArticlesRSS

How Our Company is Using SVS

jsjj01's picture

There are so many uses that we have formulated in using SVS. We currently have several test beds to see which way will best fit our environment. I have to say that SVS is so much easier to configure and manage than Softricity (which we have also tested). Currently we have about 2000+ apps that we have installed locally on our machines around the ministry.

We are an SMS shop so deploying apps has never been an issue, it is the conflicts that always give us headaches. My ideal scenario (which I am presenting to upper management) is detailed below:

  1. A complete overhaul of our AD structure to ensure that we can pinpoint SVS deployments based on user accounts and departments. We are currently checking into licensing agreements with software manufacturers but I do have workarounds just in case.
  2. Once the AD overhaul is complete we will deploy our SVS apps using SMS to general users' computers. Right now the plan is to virtualize and customize nearly 200 apps to start and continue to virtualize our apps until we have a complete virtual environment.
  3. To maintain activations, deactivations, imports, deletions, etc. we plan on using Scriptlogic objects based on the user account of the user. For instance if Joe Smith in Finance logs into a computer he will receive the apps that he needs to perform his job duties. Once he logs off the apps will be deactivated and deleted if necessary (unless it is his regular computer). This last detail is something we are still trying to figure out but we are getting extremely close to an ideal solution for this scenario.
  4. The end result will be a zero-touch desktop deployment scenario for our company. We receive the computer already containing a base image and when the user logs in the apps they require to perform their job functions will be imported and activated for their use. Some common apps, i.e. Adobe Reader, Quicktime, etc. will be maintained at the machine level and not at the user level.

It will be a wonderful day once all of this is implemented into our environment. While we do have some bugs to work out still the end of the tunnel is in sight.

k00tje@gmail.com's picture

User based software delivery

Hi we had a similar scenario and therefore i wrote a windows service providing this for me.
See http://juice.altiris.com/download/829/svs-roaming-...

Just add a user to a group which is related to a layer and he will get the app no matter which pc he is logged on to.

Meanwhile also Altiris made a solution for this which will be implemented in future versions of SVS.

Have no experience with it since we are using my own solution now for about 7 months and this still do the job for us.

jsjj01's picture

One Concern

Hi k00tje,

I am trying out your svs roaming tool (which is nice by the way) but still have one question. How did you get around licensing requirements by software manufacturers? I have never really gotten a straight answer if an imported vsa file that is not activated on a machine eats one of the licenses. We would love to be able to have apps follow around users but the licensing piece is stalling us at this time. Thanks.

John