Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrade.
Please accept our apologies in advance for any inconvenience this might cause.

Endpoint Virtualization Community Blog

Showing posts tagged with Workspace Virtualization
Showing posts in English
Admin | 02 Mar 2006 | 0 comments

"This all means you can do otherwise impossible things, such as run Microsoft Office 2000 and 2003 on the same PC simultaneously. It also keeps the operating system clean, so badly behaved applications don't conflict with it or each other - the 'DLL hell' familiar to PC support techs - and it allows an application installation to be fully reversed if it causes problems."

Read the Article.

Admin | 02 Mar 2006 | 1 comment

Can you please explain the process for installing new software with SVS?

Sure, thanks for the question. Here are the steps:

  1. The Virtual Software Package (VSP) is copied to the target desktop. This can be done using Altiris Software Delivery Solution, another software distribution tool, or through manual methods such as a CD, USB drive, or network connection.
  2. On the client, the archive is extracted to the isolated, hidden section of the file system that is managed by the Filter Driver. At this point, the VSP becomes a file system "layer".
  3. The layer is then activated, which makes it visible to the system and user - everything appears to be in it's normal location, as if the application had been installed conventionally. Activation is nearly instantaneous.
Admin | 02 Mar 2006 | 0 comments

"No messy installation scripts that break under tightened security; no troublesome "artifacts" in the Windows Registry; no leftover files lurking in obscure folders on the local hard disk, waiting to trip up the next deployment. In the software deployment world according to Altiris, applications would materialize and/or dematerialize with the flick of a switch."

Read the Article.

Jared Payne | 28 Feb 2006 | 16 comments

A feature in the SVS final release is the ability to configure SVS so certain applications running from the base cannot see virtualized applications. Jared Payne tells us how and when this is cool.

The final release of Software Virtualization Solution (SVS) includes a feature called Program Ignore. Program Ignore makes it possible for applications that are installed in the base to run and not see virtualized data. This feature is quite simple to use.

  1. Open regedit and go to HKLM\System\Altiris\FSL
  2. Create/Edit a new Multi-String Value named "ProgramIgnoreList"
  3. Enter the complete path for the executable that you want to ignore in "ProgramIgnoreList"
  4. Restart the computer (the ignore list is only read at system start up)

Antivirus software is one of the main reasons this feature was added. We recommend adding your antivirus scanner to ProgramIgnoreList. You only need to add the scanner executable to this list. It is important...

Brian Mann | 21 Feb 2006 | 1 comment

Many applications require at least one reboot during their installation. So, how does one successfully virtualize one of these hell-bent-on-rebooting apps? Brian Mann shares some pointers.

If you're trying to install an application into a virtual layer but your application insists on doing an automatic reboot during the installation process, you're in luck.

Unfortunately SVS doesn't handle this very gracefully yet (stay tuned), but here's what you can do to install these apps today.

  1. Start your capture as you would any other.
  2. When prompted, go ahead and reboot. The setup will not continue since the entries that would cause this are in the layer.
  3. Once the system is back up, re-enter capture mode (SVSAdmin, file, update, ...).
    • The easiest way to make sure that all of the correct information is captured by the layer when re-entering capture mode is to re-enter it in a global capture. The only downside is that you may have to do...
Jeremy_Hurren | 21 Feb 2006 | 1 comment

Here's a power tip from the tip master, Jeremy Hurren. In this gem, Jeremy shows you a quick way to make it easier to view sublayer information.

If you're a power user who needs to manipulate the information in your layers directly, you may find this useful.

Currently you may be using regedit to look at all the keys under HKLM\SYSTEM\Altiris\FSL to find which two areas match your layer.

Instead, set the following flag in the regsitry key to make SVSAdmin display this for you.

Modify This Key

Flags (DWORD) = 0x00000001

In the details view, you'll get an extra column of data showing "...

Admin | 14 Feb 2006 | 0 comments

"SOFTWARE from Altiris has the potential to revolutionise how software updates are pushed down to a user's desktop."

Read the article.

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.