Windows XP Mode Limitations
Microsoft has released a release candidate of Windows XP Mode, their Virtual PC based solution to provide nearly 100% compatibility with XP. Sounds pretty good, right?
Well yes, it does.
This technology is especially promising to me at work. We have several tools that proved nigh impossible to run in Vista such that we have continued to use XP on many of our machines. Last week, I installed Windows 7 with the hopes the XP mode could iron some of these issues out.
The good news is that I haven’t found any mission critical applications that require it. The bad news is XP mode has some glaring limitations, at least the small-business single install license seems to.
First of all, installing Windows XP Mode on a multi-user machine does not work like one might expect. It seems only to be available for the user who installed it. For my application, this is not very useful. We have 4 shifts that use this machine 24/7/365. If XP mode offers us anything at all, it will only be able to do so if all users have the same access. I believe it may be possible to do this if seperate VMs are employed but this is also very inefficient as that would require 4 VMs, 4 installations of miscellanious XP tools, etc. Not very useful. For this reason, I have not attempted this method yet.
Secondly, the installed VM is a completely separate PC on the network. It does not piggy back the host operating system’s domain credentials. It is possible to join the underlying VM to the domain but there again, this is no help in a multi-user environment. This also creates additional computer objects in active directory.
Both of these limitations are very disappointing. Fortunately, for what it does, it does it well. Applications are very responsive and behave as expected.
Startup times are sluggish but can you really expect anything different?
Microsoft is releasing an enterprise version of XP mode that may address some of these issues. We’ll have to see.
