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
fbuonvino | 09 Apr 2007 | 9 comments

Getting errors when deactivating your Google Earth layer? It's a problem that user fbuonvino has taken the time to troubleshoot and explain (for those of us who get cold chills when we see error messages).

You could have noticed that a request for Deactivation of some layers leads to Error like:

You could always deactivate the layer by choosing Yes, but it is not good practice, because it can lead to problems like losing data or worse.

I noted that the problem is often generated by the the fact that a program, although manually closed, continues to run in the background. To stop it, it is often sufficient to click the specific Exit command in the program icon located in the System Tray.


riva11 | 28 Feb 2007 | 0 comments

Una caratteristica della release definitiva di SVS è la possibilità di configurare SVS in modo che certe applicazioni in esecuzione nel computer, non vedano le applicazioni virtualizzate. Jared Payne descrive come e quando questo può essere un aspetto molto utile.

La release finale di Software Virtualization Solution (SVS) include una caratteristica denominata Program Ignore. Program Ignore rende possibile per le applicazioni che sono installate in un computer, di essere eseguite e di non vedere i dati virtualizzati. Questa caratteristica è molto semplice da usare.

1. Aprire regedit e andare alla voce HKLM\System\Altiris\FSL
2. Creare/Modificare una nuava valore Multistringa denominato "ProgramIgnoreList"
3. Inserire il percorso completo dell'eseguibile che vuoi escludere in "ProgramIgnoreList"
4. Riavviare il computer (la lista di esclusione è letta solo in fase di avvio del sistema)

Il software di antivirus è uno delle...

tfronza | 15 Dec 2006 | 10 comments

Tom says: I have a question for everyone. How many of you are actually going COMPLETELY SVS layered through your environment, enterprise-wide? We are and have hit a few road-blocks; I am just curious who else is going ALL SVS ALL OUT. I think SVS is a great product that can only get better and will make my life much easier as our Deployment Specialist on staff.

As we mentioned in this recent comment, most customers deploying SVS now are doing so to address particular pain points. But some are using it as their standard deployment method for all supported software. One of those is Cal State San Marcos, which we've already written up as a success story. A couple more will be written up soon. Next year, especially with Vista...

insession | 09 Dec 2006 | 8 comments

Peter asks: One of the things I have taken note of is that I cannot install a new layer as long as some layers are active - which would mean that if I have eighty apps installed thru SVS, I would have to deactivate eighty layers before I can install a new one?

Yes, you must deactivate all layers while doing a capture in SVS 2.0. It's a temporary limitation, but here's why we did it that way in the first release:

We took the perspective of the corporate repackager, who typically works on a "clean machine" in a lab to create and edit software packages, including VSP's. In that scenario, we did not want customers inadvertently creating cross-layer dependencies; Altiris doesn't yet provide detection, tracking or management of dependencies between VSP's. So SVS forces you to have no active layers while in capture mode.

Intentionally creating cross-layer dependencies: It's possible to...

bsuggs | 05 Dec 2006 | 17 comments

Have you ever spent a huge amount of time on a layer to tweak it just right but when you go to export it you get the dreaded error code 18?

You think to yourself, it launches fine why won't it export?

Well, here's a tip that will help you keep your sanity.

Error Code 18: 18--ZE_OPEN  // could not open a specified file to read.

Possible causes:

  1. The file can be in use. In this situation, make sure that there is not an open process holding the file open.
  2. You do not have permission to read the file.

Finding the file with the problem:

  1. When you are exporting your layer and you receive the error do not click OK! Leave it.
  2. Go to where the .vsa file is being created and rename it to .zip. This...
Wm Jesse Foster | 14 Nov 2006 | 1 comment

Even though the browse dialog in SVS Admin for Single Program Capture does not accept .bat as a valid file type, you can still use batch files. You can either paste or manually type the path to the batch you want to run into the Program name text field.


  1. Create a batch (.bat) file containing the command lines for launching each of the programs you want to capture to a single layer.

In Software Virtualization Solution Admin:

  1. Click File > Create New Layer.
  2. Select Install application.
  3. Click Next.
  4. Type in a name for the layer.
  5. Click Next.
  6. Select Single program capture.
  7. Under Program name type in the path and name of your batch file.
  8. Click Next.
  9. Click Finish.

Capture mode will start and your batch file will be launched. Capture mode will end after the batch file has been processed. If capture mode does not end after the batch file has...

AngelD | 19 Sep 2006 | 5 comments

Many users on the "Software Virtualization Solution Support Forum have stated (and you may also have noticed) that the path environment variable included in an Application layer is not displayed during layer activation.

The system Path environment variable which is stored in the registry key "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment" is included
in the Base (layer) by default. When an application search for an executable explorer.exe is called to resolve the Path variable (which specifies the search path for executable files). The explorer.exe resides in the Base and the Path variable in the Base will therefore be used due to SVS default priority order.

By default there is no User Path environment variable (stored in the registry key "HKCU\Environment") defined in the Base which...

Rootman | 04 Aug 2006 | 2 comments
paper clips

If you're like me you have plenty of layers in your SVS Admin list. Here are a few tips I'm using that may help you manage your list a tad better.

Managing Autostart Layers

I have a number of autostart layers that were scattered around the alphabetized layer list and wanted to indicate that they were autostart without having to check each one as well as force them to the TOP of the list.

Click to view.

Which layers are autostart?
What version of Adobe is which?
Which version of 7-Zip am I running, do I need an...

Adam Hall | 13 Jul 2006 | 7 comments

It is possible, and in some situations preferable* to run virtual platforms in a virtual layer.

I use a combination of Virtual PC and VMware Server to host my virtual instances, but I find that running these applications slows down my machine during boot up and log on.

So, I experimented with running these platforms in an SVS layer. In the case of both Virtual PC and VMware server, Global Capture successfully virtualised the applications. I had my lean-and-mean base OS, and could activate the virtual platforms only when I actually required them.

In addition, both of these platforms provides automation tools.

In the case of Virtual PC, a simple line of code in the startup folder or OnPostActivate key automatically launches my SVS layer-based virtual machine.

"Virtual PC.exe" -pc "Windows XP SP2 Altiris SVS" -launch

* Here's my rationale for capturing Virtual PC and VMware into SVS layers:

  1. It's portable. I can...
Adam Hall | 06 Jul 2006 | 6 comments

If you need to create a printer as part of an SVS Layer, you need to restart the Print Spooler service after the layer is activated.

I included a script in the Adobe Acrobat Professional layer I created, with a shortcut to this script in the StartUp folder. The layer activates, and runs the script (as it is in the startup folder) which restarts the Print Spooler service and makes the printer available.

My script is embarrassingly simple :) I'm sure this could be written in WMI or VBS to be invisible to the user.

@echo off
TITLE Adobe PDF Printer Creation
echo Creating Adobe PDF Printer ...
net stop "Print Spooler" >NUL
net start "Print Spooler" >NUL

Then I created a link to this batch file, put it in the CommonStartUp folder, and set it to run minimized.

Notes: Users may need elevated privileges to stop and start a service.

A Global capture is required to grab the printer, as it is created...