Video Screencast Help
Endpoint Virtualization Community Blog
Showing posts tagged with Performance
Showing posts in English
olliebean | 14 May 2008 | 2 comments

If you already have a number of applications virtualized as SVS layers, testing new unknown packages can be a tedious task. Testing a new piece of software means that all other layers have to be deactivated. Is there an easier way around this?

Read on to learn more.

Yes, there is. Create an empty scratch layer - I've called mine "!Scratch" (the "!" just ensures it gets sorted to the top of the layer list in SVS Agent). Then create a new shortcut, and in the box where Windows asks you to enter the location, type the following:

svscmd !Scratch a exec -p

If you put this shortcut on your desktop you can drag-and-drop a program file onto it (e.g. the installer of aa application you want to test), and the program will be run within the !Scratch layer. Or you can put it in your SendTo directory, and run a program in the...

Jordan | 25 Apr 2008 | 53 comments

Hey all. As many of you know I do a lot work with application compatibility with SVS and I'm working on a new list of applications to test. I want to know what you use with SVS or which applications you'd like to use with SVS but haven't been able to capture (that don't fall into drivers or system components).

The more info I get the better list I can create so even if someone else has posted something you're interested in post it again so I can judge popularity of specific apps.

Thanks

FrankB | 07 Mar 2008 | 12 comments

It took a while, but it is a lot of work, here goes; V2.0.0

V2.0.0
New: Fully Portable (Freeware Editions) / (USB/U3)
New: (Multi) Move Layer(s)
New: (Multi) Delete layer(s) with 100% registry removal.
New: File Progress on (Multi) Import
New: Automatically Check for Updates (See Options)
New: Added a Help Function
New: Changed Corporate edtion to fully functional for 30 Days.
New: Blue Edtion

Here Goes:

Activate Layer
Deactivate layer
Reset Layer
Rename Layer
...

Admin | 21 Sep 2007 | 4 comments

"The AT command is also an important tip for techs working with SVS layers!

Since SVS layers carry the ACLs from the machine where the layer was created, sometimes you may find yourself with stuff in a layer that you can't edit or delete locally on the client you're sitting at... "

SVS Product Manager Scott Jones just posted this cool tip as a comment in the Application Packaging group. We thought it worthy to post a link to it here, as we know that SVS Master Gurus do find the AT command invaluable!

Read the full comment.

fbuonvino | 16 Jul 2007 | 5 comments

I'll never forget a needlepoint carefully hung on the wall of a friend. It read, "Our Home: Clean enough to be healthy but dirty enough to be happy."

Juice contributor fbuonvino points out that the same philosophy should hold true when using registry cleaning tools to tidy up a machine that's housing virtualized applications.

Special care should be taken during registry cleaning on a machine using SVS. A program like Registry Booster or similar, normally used to clean a registry of errors, wrong paths, and open links could possibly mistake registry entries belonging to virtual applications as problems to be dealt with -- if the application is not currently activated.

You could easily verify the problem by making two scans, one with your virtual applications activated and another with those same applications not activated.

...
Heath Doerr | 25 Jun 2007 | 4 comments

Here's the scenario: Customer creates a VSA for App X -- it doesn't work. You create a VSA for the same application -- it works great.

Wouldn't it be nice if you could quickly compare the two VSAs to find out what the customer did differently that kept the application working?

Here's how I did it:

I've done this with two tools, the Wise Windows Installer Editor and a 3rd party tool called FileSync. (http://www.fileware.com/products.htm#FileSync)

Examining the Files

Import both of your VSAs, and find the Read Only directory name associated with each. (e.g. Customer Layer is "C:\fslrdr\1" and your layer is "C:\fslrdr\3")

Use the FileSync utility to identify differences by...

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

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

Jeremy_Hurren | 17 Jan 2006 | 16 comments

SVS CodeMaster Jeremy Hurren just threw another gem over the wall. If you want an SVS action (activate, deactivate, delete ...) to trigger an application, or send a message, or play a sound, here's the recipe.

Have you ever needed to run an external process when a layer gets activated, or deactivated, or deleted? You might, for example, have a third-party inventory system and want to re-evaluate the computer's inventory when layers activate and deactivate. (Send us your examples*).

Or maybe, like me, you just want to play a sound when layers activate. The following example plays the ding.wav file when a layer is activated and the chord.wav file when a layer is deactivated.

HKEY_LOCAL_MACHINE\SYSTEM\Altiris\FSL
OnPostActivate (MULTI_SZ) = "PlaySound.exe "C:\Windows\Media\ding.wav""
OnPostDeactivate (MULTI_SZ) = "PlaySound.exe "C:\Windows\Media\chord.wav""

In addition to a global setting like the one above, you can also change settings...

riva11 | 17 Jan 2006 | 0 comments

SVS CodeMaster Jeremy Hurren ha gettato un'altra perla oltre il muro. Se avete avuto la necessità di eseguire una azione di SVS (attivare, disattivare, cancellare ...) per dare il via ad una applicazione, per spedire un messaggio oppure per eseguire un suono, allora qui è possibile trovare la ricetta.

Avete mai avuto la necessità di eseguire un processo esterno quando un layer viene attivato o disattivato, oppure cancellato? Potresti, per esempio, avere un tool di terze parti per l'inventario e voler rieseguire la raccolta dei dati dei computer quando i layer sono attivati e disattivati. (Mandate i vostri esempi*).

O forse volete semplicemente, come mi succede, fare eseguire dal computer un suono quando un layer viene attivato. Nel seguente esempio viene suonato il file ding.wav file quando il layer è attivato e chord.wav quando il layer viene disattivato.

HKEY_LOCAL_MACHINE\SYSTEM\Altiris\FSL
OnPostActivate (MULTI_SZ) = "...