Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.
Endpoint Virtualization Community Blog
Showing posts tagged with Workspace Virtualization
Showing posts in English
Admin | 03 Jan 2006 | 0 comments

"Altiris's Software Virtualization Solution could reshape the PC landscape at the IT level."

Read the Article.

Admin | 30 Dec 2005 | 0 comments

"Simply put, for 2006, solution providers will need to keep an eye on the evolution of products from companies such as Altiris, Acronis, Microsoft and VMware."

Read the Article.

Admin | 28 Dec 2005 | 0 comments

James asked, "Does SVS support operating system patches?"

Not yet James. The current release does not allow for virtualization of OS patches, but this functionality is planned for a future release.

BBishop | 22 Dec 2005 | 0 comments

Technical wizard Brent Bishop sheds some light on an inventory problem caused by invalid characters in application layer names. The juicy truth is that SVS is still being tuned to speak perfect XML -- the language spoken by the inventory engine in Notification Server.

The Issue

Here's a problem that raises its ugly head when a Software Virtualization layer inventory does not appear in Notification Server (or does not appear to be complete).

The Details

As layers are imported into SVS on a NS Agent machine, application information is inventoried to the NS server that the NS agent reports to. There is currently an issue with missing or incomplete inventories being reported to the Notification Server.

The Cause and Resolution

SVS does not properly escape some characters for XML. So if the following characters are used in the name of an SVS layer, the layer inventory data becomes inaccurate or missing.

quote (")

Admin | 22 Dec 2005 | 0 comments

Matt asked, "What would happen to my systems if the SVS filter driver fails?"

Hey Matt, thanks for the question. Computer systems depend on drivers every time they boot. What would happen to your system if its video card or hard disk driver were to fail for some reason? Like any driver, there is always the possibility, however unlikely, that an unrecoverable error could occur. In that case, the most likely result would be that the system would be rebooted. Any data that was written to the hard drive during that session would still be preserved in its corresponding layer. Any data that was hosted in system memory and hadn't been committed to the hard drive (saved) would, of course, be lost.

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

Admin | 15 Dec 2005 | 1 comment

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

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.

The_Snave | 14 Dec 2005 | 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 the same on every...

Admin | 13 Dec 2005 | 0 comments

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

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