Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Virtualization Community Blog
Showing posts tagged with Configuring
Showing posts in English
Admin | 13 Mar 2006 | 0 comments

Richard asked, "What are the entry barriers to using Software Virtualization Solution in my environment?"

The main ones we hear about are concerns over supportability of commercial apps that are virtualized; and customers who require features we don't have yet in the initial release (support for terminal servers, for instance). On the other hand, Richard, the up-front learning curve is minimal and every customer we've spoken to has one or several pain points that SVS can help them alleviate (or eliminate) right now.

Jeremy_Hurren | 10 Mar 2006 | 0 comments

For security reasons, layers don't store passwords. So, how do you create a layer that starts a service on activation that requires a password? Jeremy Hurren takes us under the hood for this workaround.

Because of the way that SVS virtualizes services, it does not store the password information necessary to log on as a service. So if you are installing software that has such a service into a layer, it will work the first time you run it, but after deactivating it and activating it again the service won't be able to start. The underlying technical reason is that SVS has to delete and create the service repsectively during the deactivation and activation. Because SVS doesn't want to expose any password information, it doesn't store that information in the layer, and therefore cannot use it to recreate the service during activation.

There are two different solutions that can work here. First would be to change the service you are installing to log on as one of the built-...

Wm Jesse Foster | 09 Mar 2006 | 0 comments

If you've been faced with the task of capturing several programs into a single layer, this tip, from support guru Jesse Foster, should get you going in the right direction.

There is at least one way way to capture multiple programs into a single layer using Single Program Capture. Here's the method I use.

  • In SVS Admin select File > Create New Layer
  • Select Install application. Click Next.
  • Give the Layer a name. Click Next
  • Select Single program capture. Under Program name, type (or browse to) the path for cmd.exe (C:\Windows\system32\cmd.exe on my computer). Click Next.
  • Click Finish.

Capture mode will start and a command window will open. Anything done from this command window will be captured in to the layer. So, start your installers from this window and the program will be captured in to the layer. Capture mode will end only when the command window and any child processes from your installers have exited...

Jared Payne | 08 Mar 2006 | 1 comment

Jared Payne provides helpful details on the priority values assigned by Fslx.sys to shed some light on the Layer Prioritization section of the SVS White Paper.

One of our readers wrote us that page 9 of the SVS white paper was confusing, with the chart displaying a Base request twice -- for example, with 2 different Default Priorities but no explanation as to why they are different, as follows:

By default, Fslx.sys assigns layers the following priority values:

Read more
Admin | 07 Mar 2006 | 0 comments

Greg wrote: You know how when you do many current installations, at the end of the installation there is a checkbox that says "launch application"? Well, if you leave that checked, even though setup.exe, or whatever you used to do the installation, is done, SVS continues capturing system changes because you launched the program at the end. It still sees that as part of the setup.exe thread. Capturing doesn't stop until the application is closed.

You are correct, Greg, and that is by design. A Capture by Process (or "Single Program Capture"), by necessity, must capture the entire process tree -- not just the executable you specify, but also any process called by it as well. That's how we ensure the capture gets everything, since installers often call other embedded or external installers, executables, services, scripts, and even batch files.

By running the application at the end of...

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

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.