Application Virtualization 4.5 Beta Standalone Trial Guide available

There is a new SoftGrid 4.5 Beta Trial Guide available. This one is about how to use SoftGrid in “Standalone” mode.

Download a PDF or XPS version of the document.

This document is stored on the SoftGridBlog documents page for future reference.

SoftGrid: 5 easy ways to look inside the Q-drive

Troubleshooting SoftGrid applications often includes taking a look under the hood and inside the Q:\ drive (or whatever drive letter you set it to). Obviously this cannot be done directly from Windows Explorer. Doing this will result in an error “Q:\ is not accessible. Access is denied.”            

Luckily, there are many ways to take a look inside the Q-drive, through explorer or command line, and successfully troubleshoot a SoftGrid package. In this post I´ll elaborate the most common ones I use.

1. Map a drive
The easiest one I´ve seen (and just recently found out through Aaron Parker’s techblog) is to just simply map a drive to the Q: drive.


This works for both the localhost as for remote computers. You can instantly browse the root of the mounted drive through a command line or through Windows Explorer. However you can only browse subdirectories of the applications that are actually running. This might an issue if you’re troubleshooting the application startup in the first place :-)

So that’s where the “advanced” stuff comes in.

2. Edit section in OSD
This section includes editing the OSD file(s). The best way to do this is by using an editor like Notepad++ or a designated tool like the OSD Editor from Login Consultants. If you’re confident enough you could also use good old Notepad.
For the steps below it’s important to create a copy of the original OSD. It doesn’t matter which one as long as it’s from the same (virtual) application. Editing the original one might break the application.

Instead of starting the original application we have to start another program (like cmd.exe) in which we can do our troubleshooting. To do this first make sure that you change the VERSION tag of the (copied) OSD. Also make sure that you are running in the correct environment and that the application is already loaded. Not changing the version key will overwrite the OSD in cache, making the original application(shortcut) starting the “debug program”.

<softpkg name="Example Application" version="1.0">
<softpkg name="Example Application" version="debug">

The “debug” setting above is arbitrary and can contain any text you like.

In the specific case of running a command prompt also be sure to change the SUBSYSTEM to console.

<subsystem value="windows">
<subsystem value="console"> 

The “console” value above is a fixed value and should contain either “windows” or “console”.
If you don’t change the SUBSYSTEM value and start cmd.exe you’ll get an error: “Cannot create a file when that file already exists”.

When the above settings are applied you need to change the FILENAME value in the tag to contain the program you like to start (in this example it’s cmd.exe).

<codebase filename="C:\SAMPLEAPP\APP.EXE">
<codebase filename="C:\WINDOWS\SYSTEM32\CMD.EXE">

Be sure to clear out the PARAMETERS value if it’s set.

Although you can basically start any program you like here, you have to make sure that the specific program is locally available (installed) and can be started in a separate memory space. If the latter is not the case the program can’t be started simultaneously in both a virtual and real environment. For example: this is the case for Regedit and Windows Explorer.

If you do want to run Windows Explorer from the section follow this article from Aaron Parker’s techblog. You’ll need to set a registry key for Windows Explorer to start each instance in a separate memory space. This can be done both in the real world as well as in the virtual environment.

3. Edit section in OSD
You can also run the custom command before the actual application is launched. To do this, locate the DEPENDENCY tag and add the SCRIPT tag with the following code:

   <script event="LAUNCH" protect="TRUE" wait="FALSE" timing="PRE">

The difference between editing the CODEBASE section and the SCRIPT section is that the first one will show up in your cache as a separate “application”. The second one will have to be edited in the original OSD where no other changes are made.

You can toggle the wait value to let the application wait for the custom command to finish (wait=”TRUE”) or to launch simultaneously (wait=”FALSE”). If you set the wait value to TRUE you might want to include the TIMEOUT=”0″ value to the SCRIPT tag if you are debugging. The TIMEOUT value tells the application how long it should wait for the script before exiting. The value of 0 (zero) tells it to wait indefinitely.

More information on the SCRIPT tag is explained perfectly here.

4. File Open from within the virtual application
If you have an application that has a “File -> Open” or similar menu, you could use it to locate the application that you want to run. As I said earlier, your application has to start in the first place.

Sometimes you can’t just select for example cmd.exe en press Select in the dialog box. What I always do in this situation is right-click the desired program and select open or “run as”. Even when you don’t supply any additional credentials, the application just opens separately.

A trick to get Windows Explorer to run (without having to set the registry key as said earlier) is to kill the explorer.exe outside the virtual environment and to start it again inside using the File -> Open command.

5. SFT Explorer
Last but certainly not least is the tool SFT Explorer by Kalle Saunamäki. With this tool you are able to look inside an SFT without ever having to load it on a machine. You can actually see what the files/registry keys would look like if the virtual application was applied on the target machine. You cannot make changes to the application however.

Well, that’s it. These are the ways I use to get inside the SoftGrid applications to do my troubleshooting. If you know any additional tricks, feel free to let me know as long as you don’t tell me that I’ve missed the sequencer itself though :-0

SoftGrid 4.1 SP1 and 4.2 HFRU2 are available

Again newer versions of SoftGrid 4.1 SP1 and 4.2 are available. It contains some minor fixes and a new feature.

Fixes are:

  • The log level of the “Error reading from socket” message is now Debug. Therefore, the message does not appear in the Sft-server.log and the Windows event log at the default log level when you use SoftGrid Virtual Application Servers together with a hardware load balancer.
  • SoftGrid Sequencer now preserves OSD GUIDs when it opens SoftGrid v3.2 sequencings for a package upgrade.
  • Intermittent “0xBE” Stop errors that occur at system start on multiprocessor computers have been addressed.

New features are:

  • SoftGrid now supports deployment of Virtual Application .msi files that are generated by the MSI Utility for Microsoft Application Virtualization to SoftGrid clients that are running Microsoft Windows 2000 or Windows 2000 Server/Advanced Server and that have Terminal Services enabled.

New versions of the components are: 

  • SoftGrid for Windows Desktops (
  • SoftGrid for Terminal Services (
  • SoftGrid Sequencer (
  • SoftGrid Server (
  • SoftGrid for Windows Desktops (
  • SoftGrid Sequencer (

Remember version 4.1 is for Windows XP environments and 4.2 is for Windows Vista environments

Download 4.1 versions here. and 4.2 versions here.

News Source

Running Application Virtualization 4.5 on Windows 2008 Server

I’m running Application Virtualization 4.5 (SoftGrid) on a Windows 2008 RTM Virtual Machine. First off i’m pretty impressed with the performance of Windows 2008 running as a guest in Virtual PC 2007. It is “even” running on a Windows Vista SP1 Host. I really had the idea this was going to be slow, but it proved me wrong. Way to go Microsoft. Also Application Virtualization 4.5 is running quite smoothly.

So the virtual box is set up to be a Domain Controller, Web Server (IIS7), SQL 2005 Express is running on it and Application Virtualization 4.5. The only thing I ran into during installation of AppVirt was an error concerning IIS, “Error 25120. The installation program was unable to create the required IIS Virtual Directory”. This has to do with the fact that AppVirt was actually written to run on IIS6.

I found the solution on the Microsoft Technet Application Virtualization forum. Before installing AppVirt, add the following components through Server Manager to the Web Server Role in addition to the IIS7 default components.

  • IIS Management Scripts and Tools
  • IIS 6 Metabase Compatibility
  • IIS 6 Management Console

IIS Components screenshot

After this you are ready to install Application Virtualization 4.5!

System Center Configuration Manager 2007 R2 Beta available

And it includes “Application Virtualization management support”. Which will integrate Microsoft Application Virtualization with SCCM seamlessly.

Register and download at


How to sequence Visual Studio 2005

There is a new knowledge base article at Microsoft on how to sequence (virtualize) Microsoft Visual Studio 2005. I think it’s great Microsoft is starting to help people and support a set of applications on the SoftGrid platform. Of course it will start out being only Microsoft applications.

Check KB946343

MS Application Virtualization Hands-on Labs

The guys at the MS SoftGrid Team Blog posted a nice list of links to numerous online Technet Virtual Labs. So learn more about SoftGrid Application Virtualization by following these labs.

Click here to follow the Labs.

Sequencing Guide by Microsoft Consulting Services

There is another Sequencing Guide available. This time by Microsoft Consulting Services.

Download a PDF or XPS version of the guide.

This document is stored on SoftGridBlog Documents Page for future reference.