Video Screencast Help
Search Video Help Close Back
to help

Endpoint Virtualization Community Blog

Showing posts tagged with Workspace Virtualization
Showing posts in English
Simplifying the SVS Client Admin Install with a .bat File
Jeremy_Hurren | 29 Jul 2010 | 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!
Read more
Semplificare l'installazione di Client Admin Install con un file .bat
riva11 | 29 Jul 2010 | 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...

Read more
How can virtual applications that require integration work together?
Admin | 29 Jul 2010 | 1 comment

Q:
Elaine asked, "If applications are isolated, how can separate applications requiring integration work together? Do they have to be packaged as part of the same VSP?"

A:
Hi Elaine. Active Virtual Software Packages are visible system-wide. So virtualized applications interact normally with each other and with processes running from the base. "Isolation" refers to when there are duplications on the system -- e.g., two different versions of the same DLL at the same path, in two different VSPs. SVS ensures that each application sees only the version it needs to run correctly.

Read more
Saving Files in a Virtual World; Do You C:\ What You're Doing?
The_Snave | 29 Jul 2010 | 0 comments

There are a few things one needs to understand before saving files in a virtual environment -- especially if you export application layers for use on different machines. SVS pro Evan Thomas shows us how to avoid the sticky consequences of saving to a lettered drive in this new, virtual world.

When you're running a virtual application, changes you make -- including any documents you create -- are saved to the application layer, regardless of where (C:\ or D:\ or E:\ ...) you tell the changes or files to be saved. (The exceptions to this rule are if you have an exclude entry in the layer or a data layer capturing a particular directory or file type -- but that's another tip.)

click to view

When working with virtual applications, it's especially important to remember that drive letters are not...

Read more
Will I still need Wise Package Studio after I adopt SVS?
Admin | 29 Jul 2010 | 0 comments

Q:
Jim asked, "I'm currently using Wise Package Studio to package my applications. Will I still need this after I adopt SVS?"

A:
Good question, Jim. SVS includes a simple packaging tool for creating virtual software packages (VSPs). Wise Package Studio on the other hand includes a plethora of tools for quality assurance, package management, patch impact assessment, packaging project management, and much more. Whether you are virtualizing your applications or not, Package Studio provides a valuable solution for best practice software release management.

Wise Package Studio will soon provide the ability to create, customize, and manage virtual software packages in addition to the current package formats that are supported. Also, we'll give you the ability to convert existing MSI packages into VSPs so that you can leverage all of your previous packaging efforts. Ultimately, we believe that Package Studio will...

Read more
ZDNet Asia - Putting a new spin on virtualization
Admin | 29 Jul 2010 | 0 comments

"According to analyst firm Gartner, virtualization has the greatest potential to fix the woes of technology managers faced with managing a typical heterogeneous IT environment which includes multiple operating systems (OS), hardware and software applications."

Read the Article.

Read more
Note to Self ... Reboot After Install
BBishop | 29 Jul 2010 | 0 comments

Tech guy Brent Bishop explains why it's import to remember the all-important reboot step after you install SVS.

The Issue

If you've just installed the Software Virtualization Admin (SVS Admin) tool and it allows the import of VSA (Virtual Software Application) files but will not activate them, read on. Oh, yeah, to keep you scratching your head, no message boxes or error messages accompany the odd behavior.

The Details

You've just installed and can run the SVS Admin tool. All seems well until you activate an application layer.

The Cause and Resolution

Here's the Juice: SVS must be rebooted before the file system filter driver (which is at the core of SVS functionality) will operate. A logoff/logon will recache the local security credentials so that the SVS Admin tool can be run but this does not make the SVS filter driver fully operational. A reboot after install of SVS is necessary to get everything running as designed.

Read more
Do I need to create different Virtual Software Packages for each operating system I plan to deploy the applications to?
Admin | 29 Jul 2010 | 0 comments

Q:
Sara asked, "Do I need to create different Virtual Software Packages for each operating system that the package will be deployed to?"

A:
Hi Sara. Usually, the answer is no. SVS uses variables that take into account the different configurations of an application on different operating systems. These variables are automatically created and are used for file system paths, registry values and shortcuts.

For an example, go to SVS Admin, deactivate a layer, right click and select "Edit Advanced layer properties…" The display on the Files tab is shown by variable name. If you click on the "Variables" tab, you'll see the current values of all the variables, on the local machine where you are running SVS Admin. This can help you see what the variables "really" point to!

Some applications do require different files to run correctly on different versions of Windows. Currently, in that case, you would...

Read more
Press Release - Altiris selected as World Economic Forum Technology Pioneer
Admin | 29 Jul 2010 | 0 comments

The World Economic Forum selected Altiris as a Technology Pioneer for 2006. The WEF defines a Technology Pioneer as a company that delivers a highly transformational and innovative technology that has potential long-term impact on business and society.

Read the Article.

Read more
Teaching Acrobat New Tricks: Running Two Versions Simultaneously
Kevin M. | 29 Jul 2010 | 1 comment

If you're using SVS to run multiple versions of Adobe Acrobat at the same, this tip from Juice editor Kevin Millecam will help you pull it off.

There's a post in the SVS support forum where a user is having trouble launching two versions of Adobe Acrobat (5 and 6) at the same time. He's created a shortcut for each version of the program but after one was launched that version took control and it became impossible to launch the other.

When we squeezed the SVS development team for details, we found that this behavior is by design. After all, it would get particularly annoying if each time you opened a new PDF document, another instance of the application launched. There are cases (especially when using SVS) that one might want to override this default behavior. You might, for example, want to explore a beta version of a product at the same time you're running a production version of the same application.

Here's How

To change the default launch behavior,...

Read more