Virtual PC .. Windows 7 ...Sigh...

Spent the day trying to debug an application for compatibility issues. As you would (I am sure you would), I created a virtual machine with a new Windows 7 build. For those less initiated in the fine arts of attempting to get recalcitrant applications to; install successfully, Start, Run, do something ... and then not crash

The last thing you want is to have a machine filled with applications installs that FAIL to do most of the above (I admit, the nature of the result of some of my work). So, I built a virtual machine, as you would, I am sure you would. Note: I am repeating myself - because I have just lost a significant part of my mind, and possibly my soul.

Here is why. Created a Virtual PC machine. Installed Windows 7 as a GUEST build. So far so good. Note: I am doing on this work on a Windows 7 host machine. On the guest (Virtual PC machine) I tried to install the Virtual PC tools and drivers. These are the tools that are shipped with Virtual PC to allow for increased functionality and little things like being able to work across Remote Desktop Session (RDP) and having the ability to Drag'n'Drop files onto a target Guest Virtual machine.

Well, Under Windows 7, installing these default tools, utilities and drivers generated a Blue Screen of Death. So, I did a restore ... Back to the original state . This worked OK.

Thinking about this for a while... I thought to myself... Hey, I should be using the latest Virtual PC software from Microsoft. This thought was also associated with vague hope that "a later version" would solve this issue and offer something new/better.

So, I downloaded the Virtual PC from the Microsoft website (look here: http://www.microsoft.com/windows/virtual-pc/download.aspx)

Hint: I didn't read the instructions.... Oh, now the tale of woe begins...

I rushed ahead and installed the new update (a MSU package) with the drunken glee of a techie with a new download.

Now, this is where life becomes difficult/interesting. As this update is not a MSI, the installation of this new Virtual PC application does not show in the Add Remove Control Panel Applet (ARP). So, wait for it.

You can't uninstall it. Yes, maybe you can - I am just not smart/informed/good-looking enough to bribe someone to help me.

I repeat - You can not Un-install this update. This is important. Besides, breaking all of the principles I hold true about application installations (i.e. Install/update/un-install) this just comes as a nasty shock.

Because, now I have read the instructions on the Virtual PC web-page. You need to ensure that your hardware supports virtualization. There is a simply (but, surprisingly large and complex) application from Intel that will let you know the good or bad news .

Look here for this Intel applet: http://www.intel.com/support/processors/tools/piu/

Does my machine support virtualization? Does it? No! It does not.

Too late...

That's OK, I can just run Virtual PC 2007. It ran before... Just slowly...

This is what I got...





So, with some hope, I clicked on the "Check for Solutions Online" button.

I got...




Meaning now... Both versions of Virtual PC do not work on my machine.

Luckily, I have an inkling on how the Program Compatibility Assistant (PCA) works. It identifies executables through a complex algorithm of filename, header information and file date/time/size data. Luckily, for me you can change the EXE name for Virtual PC and fool PCA.


A simple work-around for the simple minded

Moral: There are two morals to this story:

1) At least passing a wincing eye over the instructions. Especially, if they include words like "Important" or have big orange boxes around them.

2) Be very careful with MSU application installations. I suggest that you install them on a Virtual PC first. :)

XP Mode - More trouble to come

I blogged a while ago about some of the issues surrounding XP Mode under Windows 7.

For those of you who are not aware of this functionality recently introduced in Windows RTM; XP Mode provides a virtual PC version of Windows XP SP3 bundled in Windows 7. For more information on this windows 7 application compatibility functionality look here: http://www.microsoft.com/windows/virtual-pc/

The idea behind putting a virtual PC in a bundled Windows release is a good one. For many enterprise customers, this option will not be exercised as they will require more functionality offered by Microsoft's App-V or Med-V solutions. So, this option for support XP dependant applications is really targeted at the Small and Mid-Sized businesses.

There are a number of problems/issues surrounding XP Mode for Windows 7 though including; (and not in any particular order)

• Patching Issues (how do you ensure your XP mode version is up to date?)
• Distributing standardized application packages
• Hardware Support (see: http://www.pcpro.co.uk/news/265948/no-windows-7-xp-mode-for-selected-vaio-owners)

And, now Antivirus vendors are entering they fray:

http://www.pcpro.co.uk/news/enterprise/351016/microsoft-and-sophos-bicker-over-windows-7-xp-mode

And

http://www.theregister.co.uk/2009/08/21/win7_xp_compatability_row/

I am waiting to see how the Microsoft partner ecosystem responds to these issues. They should not be complaining - this could be a great opportunity for a new feature to their existing product sets (competitive differentiators) or even new products.

Vista - Virtualization for the masses

Well, you thought that virtualization was expensive, involved evaluating  and deploying complex new technologies and possibly new ways of thinking about deployment and maintenance (shock horror).  You may also not be aware that Vista offers a level of virtualization right out of the box. Not the VMWare kind of OS level virtualization or the SoftGrid (App-V) kind of application virtualization - but the simple kind called;

folder and registry re-direction or "Folder and Registry Virtualization".

 

Folder and Registry Virtualization attempts to address the scenarios where an application attempts to write to a "local machine" or security protected area - and Vista automatically redirects the write (and subsequent read) request  to a user portion of the registry or a folder location in the user profile.

 

If you are developer type, you can find out more here: http://msdn.microsoft.com/en-gb/library/bb530198.aspx

 

Virtualization is pretty painless under Vista and is a great technology. However, you need to be aware that you should not rely on Registry and Folder virtualization as Microsoft states;

 

"As virtualization is an interim application compatibility technology, Microsoft intends to remove this form of virtualization from future versions of the Windows operating system as more applications are migrated to Windows Vista. As a result it is imperative your application does not take a hard dependency on the presence of virtualization in the system."

 

Microsoft has outline a few scenarios where you may need to disable Virtualization - which can be found here: http://support.microsoft.com/kb/927387

 

I think the biggest "gotcha" is the packaging of applications on Vista . Virtualization may cause duplicate registry and file locations in your target package as part of the snap-shot process. Not a big issue - but you will need a mechanism to checks for these duplicate registry entries and files.

 

Symantec has some great  coverage and demos on Virtualization which can be found here:

http://www.symantec.com/community/article/2665/folder-virtualization-concepts-windows-vista

 

And

http://www.symantec.com/community/article/2665/folder-virtualization-concepts-windows-vista