Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Virtualization Community Blog
Showing posts tagged with Installing
Showing posts in English
JordanCClark | 11 Jul 2008 | 0 comments

Normally, I'd recommend installing SVS before the Novell Client, but if you goof (like I did), this workaround is for you.

I ran into a problem with a crashed PC, and decided to rebuild the file system from scratch, instead of restoring from an image (it was a slow day). After having the required prerequisite software installed, I tried -- and failed -- to install SVS, which kept telling me that there were pending file ops, even after a fresh boot.

I tracked the problem to the Novell Client, specifically dpmw32.exe, which is the Distributed Print Service Manager. This looks at your user account, and installs/updates the printer drivers to whatever printers you have access to. Great when it works, but usually a pain. I ended up disabling it through msconfig.

Hope this helps!

Swami | 28 Jan 2008 | 17 comments

If you are getting an error during installation of Altiris SVS this tip may be for you. In some old computers (not a clean machine - a machine that has been used for some time) you might get an error saying something like, "some files are in use" and it may ask you to reboot. If after several reboots, you are get the same error, try this tip.

STEP 1) Get the SVS installation EXE, execute it, provide the key, and check all the 4 check boxes when prompted. At this point, if you the error message, don't worry about it -- we'll take care of it.

STEP 2) Now you have an ".MSI" file in the same folder.

  1. Copy the line of code we've listed here:
    msiexec.exe /qn /i software_virtualization_agent.msi PRODUCT_KEY=[your license key, without brackets] D_FSLRDR="[Full path name without spaces and long name of the...
riva11 | 28 Jan 2008 | 0 comments

Se ottieni un errore durante la fase di installazione di Altiris SVS , allora questo trucco può esserti utile. In qualche vecchio computer (non un computer nuovo - ma una macchina usata gi&#224 da qualche tempo) puoi ottentere un errore simile a questo, "qualche file è in uso" e ti viene richiesto di fare un riavvio. Se dopo alcuni riavvi, viene visualizzato sempre lo stesso errore, allora prova il seguente trucco.

Passo 1) Preleva il file EXE di installazione di SVS, eseguilo, inserisci la chiave di licenza, e controlla che tutti i 4 check boxes sono visualizzati. A questo punto, se viene visualizzato un messaggio di errore, non preoccuparti -- vedremo come risolverlo.

Passo 2) Adesso hai un file ".MSI" nella stessa cartella.

  1. Copiare la linea di codice visualizzata di seguito:
tfronza | 27 Aug 2007 | 2 comments

Just a quick time saver... When doing an enterprise install of SVS it is waaay easy to run the command line install for it. Here's the command line I use:

msiexec.exe /qb? /i Software_Virtualization_Agent.msi REBOOT=ReallySuppress PRODUCT_KEY=xxxxx-xxxxx-xxxxx-xxxxx INSTALL_ADMIN=1 ALTIRIS_NS=1

I drop the file using a Deployment Server job. I also -- on another machine -- create my exceptions and find the place where they are located in the registry. I then export the Registry Key and I drop the registry Key file to the machine during setup. Here is where the Exception is located in the registry...


Export this WHOLE key and then import it after your install (Using a free Registry importer like REG.exe) and then you have a Customized install with all YOUR...

riva11 | 27 Aug 2007 | 0 comments

Un utile trucco per risparmiare tempo... Quando dovete fare una installazione di SVS in una ambiente di rete aziendale, la strada mooolto più semplice è di eseguire il programma di installazione da linea di comando. Di seguito il comando da eseguire per la installazione:

msiexec.exe /qb? /i Software_Virtualization_Agent.msi REBOOT=ReallySuppress PRODUCT_KEY=xxxxx-xxxxx-xxxxx-xxxxx INSTALL_ADMIN=1 ALTIRIS_NS=1

Avvio il comando tramite un job di Deployment Server. E -- da un altro computer -- creo le mie eccezioni e ricerco la locazione dove devono essere inserite nel registro. Poi esporto la chiave di registro e la copio nel computer durante la fase di esecuzione del setup. Di seguito trovate la eccezione inserita nel registro...


Passo successivo è quello di esportare l'intera chiave e poi importarla a installazione conclusa (Si consiglia di usare un importatore di registro gratuito come REG.exe...

Admin | 14 Jun 2006 | 0 comments

Brad asked, "The user guide indicates that SVS should preferably be implemented on a machine running no more than the operating system. I have recently had to do a full restore and have installed all my apps. etc. this was before becoming aware of SVS. Any problems in utilizing SVS now for future installs of apps? I would appreciate advice."

An OS migration or hardware refresh—or any roll out of a new image—is an opportune time to make the transition whole hog to virtualization. However, everyone has pain points that SVS can help with even on pre-existing "dirty" machines. Go ahead and start experimenting with SVS. Use it for new apps and apps that you are just testing or evaluating.

Admin | 27 Mar 2006 | 1 comment

Does the end user need to do anything special to run a new virtualized application?

The application appears to the end user exactly as if it had been installed conventionally. The end user runs the applications just as they would a normal application.

  • No system rights required by user for "install".
  • No reboot required on client.
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...

Jeremy_Hurren | 19 Dec 2005 | 0 comments

We were able to get Jeremy Hurren for a split-second (between coding SVS and snowmobiling) to show us a simple but nifty .bat file that makes installing the SVS Client Admin tool relatively foolproof. Give it a look.

Copy the line below into a text editor, change the PRODUCT_KEY to one you own, and save it a setup.bat in the same folder as your "Software_Virtualization_Agent.msi" file.

When users click the .bat file, the SVS Client Admin will be installed (your users won't have to type in the product key) and they'll be prompted to reboot their machine ... a necessary step in the installation process.

msiexec /i Software_Virtualization_Agent.msi PRODUCT_KEY=00000-00000-00000-00000 INSTALL_ADMIN=1 /qb!

riva11 | 19 Dec 2005 | 0 comments

Diamo spazio a Jeremy Hurren per qualche attimo, per mostrarci un semplice ma interessante file .bat file che crea una installazione di SVS Client Admin quasi a prova di errore.

Copiare in un editor di testo la riga mostrata di seguito , modificare la voce PRODUCT_KEY con quella in vostro possesso, e salvare tutto in un file denominato setup.bat nella stessa cartella dove si trova il file "Software_Virtualization_Agent.msi".

Quando gli utenti cliccano il file .bat , il programma SVS Client Admin verrà installato (senza nessuna richiesta agli utenti di inserire la chiave di registrazione della licenza) e saràinfine richiesto di riavviare la macchina ... passo questo obbligatorio per completare il processo di installazione.

[quote]msiexec /i Software_Virtualization_Agent.msi PRODUCT_KEY=00000-00000-00000-00000 INSTALL_ADMIN=1 /qb![/quote]

The original article Simplifying the SVS Client Admin Install with a .bat File submitted by lordjeb can be...