Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Virtualization Community Blog
Showing posts tagged with Workspace Virtualization
Showing posts in English
Randy Cook | 14 Feb 2006 | 3 comments

If you want to change the location of the fslrdr folder to something besides the c:\ default, you'll need to dig out your registry tools. Randy Cook shows us which wire to cut.

Like all things in the Juice, this is not strictly supported, but appears to work fine.

After installation and before you create/import any packages, modify the setting: HKLM\SYSTEM\Altiris\FSL\DefaultFileRedirect.

Editor's note: Read this article for a cautionary note about moving the fslrdr location.

Admin | 13 Feb 2006 | 0 comments

I have a couple of older systems in our organization. Will I be able to take advantage of the SVS technology?

Only Windows 2000, XP, and 2003 systems have the programmatic infrastructure to support "filter drivers" like the one developed for SVS. Earlier versions of Windows are not supported.

Admin | 13 Feb 2006 | 0 comments

Is SVS licensed per node? Where can I find out about purchase options?

SVS is licensed per managed "node", meaning a license is required for each system on which the SVS agent is installed. Volume pricing is available directly from your Altiris Sales Representative or through one of our many resellers and partners.

Admin | 07 Feb 2006 | 2 comments

Frank asked, "SVS appears to be an incredibly powerful tool. I'm thinking of using it to distribute applications to users on my network but what if an application requires a different license key on each computer I install to?"

Good question, Frank. Thank you. This same issue comes up with imaging and with other centralized application distribution technologies, not just with SVS. I believe that vendors understand the customer's need for standardization and manageability. In many cases, deployment with the same key on each machine is acceptable as long as, in the case of a compliance audit, the customer can produce proof that they own the correct # of unique license keys.

But in the case where a vendor really does require that a different key be put on each machine, most vendors that cater to business customers provide the correct command line options to enable automated distribution and to still...

Admin | 07 Feb 2006 | 0 comments

Al asked, "I have a definitive interest in my PC's best performance. Too much has gone wrong upon installing a new hard drive and few programs. Can SVS help?"

Al, thanks for downloading SVS. Performance improvement is not one of the core value propositions that we are talking about. But SVS could help in at least one regard, by eliminating "registry rot" and "DLL hell". One of the contributors to performance degradation over time is the repeated installing and uninstalling of software, when leaves behind all manner of potential problems.

Especially for the tinkerer who likes to collect and install every interesting-sounding piece of software they can find. ;) That would be me. I used to re-install Windows every six to nine months just to get back to a baseline. But with SVS, by installing everything into layers, you keep the baseline intact. Want to try Cool Software X? No problem. Install it into...

Brian Mann | 07 Feb 2006 | 0 comments

What happens if you create data layers on your computer's E drive and you make the move to a computer that doesn't have a E drive in its path scheme? SVS tester Brian Mann explains how to get yourself out of this pinch.

Evan Thomas shared some good advice about how and where to create layers in his "Saving Files in a Virtual World; Do You C:\ What You're Doing?" tip. If, however, you didn't read his tip until now, here's how to avoid one of the pitfalls he describes.

If you set up your layers on a machine with an E drive and you've been moved to a machine without an E drive, don't worry, your files are still saved in the layer. In order to get to the data, deactivate the layer and double click on it.

click to view

This will open the advanced layer editor. While...

Admin | 06 Feb 2006 | 0 comments

"Test Center engineers were able to put the most recent Beta (Beta 3) of the product through its paces and found that SVS has the potential to rewrite the rules of how software is pushed down to client systems."

Read the Article.

Jeremy_Hurren | 31 Jan 2006 | 0 comments

You can adjust the level of compression that SVS applies when it creates a Virtual Software Archive (VSA). By adjusting this level, you can find a balance between performance and size. Jeremy Hurren shows us how to find the perfect balance.

If you have data that needs a different level of compression, you'll be happy to know there's a way you can change that (either per-layer or machine-wide). A perfect candidate would be my MP3 data layer which holds many gigabytes of data. Since the compression on MP3 files is infinitesimal, I choose to have them simply stored and not compressed at all to speed up the process.

The following setting will set the compression level machine-wide:


CompressionLevel (DWORD) = 0-19 (5 is the default)

To set this for an individual layer, place the value under the following registry key:


(replace 1 with the...

Jared Payne | 31 Jan 2006 | 4 comments

The ability to apply a virtual patch to a software application is one of the exciting features we've been told to look forward to in a future version of SVS. Jared Payne has found a way to get this functionality today ... and he's given us the steps!

The ability to apply a virtual patch to a software application is one of the exciting features we've been told to look forward to in a future version of SVS. Here a few steps that will allow you to apply virtual patches using today's SVS.

  1. Start with an application installed to an SVS application layer.
  2. Reset the layer to make sure it is clean.
  3. Activate the layer.
  4. Run the application's update feature (do not enter capture mode).
  5. Create an empty layer (for this example, we'll name the layer "App_PATCH_1").
  6. Run WriteableSwap.
    WriteableSwap application App_Patch_1 -F
  7. Export App_Patch_1
  8. Send App_Patch_1 to all your client...
Admin | 30 Jan 2006 | 0 comments

Dean asked, "Does SVS resolve software conflicts differently than Wise Package Studio? If so, how are they different?"

Hi Dean. ConflictManager (a component of Wise Package Studio) provides functionality for detecting and resolving conflicts prior to deployment, by tracking all desktop components (applications, drivers, base images, etc.) in a database called the Wise Software Repository. Conflict Manager then compares all of these components to identify potential conflicts, and provides guidance on optimizing your software packages. For conventional installers like MSIs, that could mean changing packages so that each application uses the same version of any shared components.

With SVS, conflicts are avoided by running each application from its own virtual layer. Each application always uses its own versions of any shared resources -- both files and registry keys, thereby avoiding software conflicts...