Geeks With Blogs
Thomas Canter

I’ve been running Windows 7 for only a short time now.

But in that, as a developer, I find that I avoid doing my development on my actual desktop.

Specifically, I have several customers today that run different versions of BizTalk Server from 2004 to 2009.

In addition, many of these customers require you to install VPN software that can wreck havoc with your most critical hardware asset you bring to the table, your personal laptop.


Let us examine a typical work flow that I have encountered several times.

I develop a clean bootable Windows Server 2008 Virtual machine on my Windows 7 Desktop

I ship the VHD to corporate, and they deploy it on our Hyper-V environment

Me and my team working remotely, share and update the system

I pull back the VHD and give it to the customer who is running Virtual PC 2007 SP1


For each of these stages, the migration process is the same.

  1. Uninstall the Integration Components (IC)
  2. At the command prompt, run the following command:
bcdedit /set {current} detecthal yes


What happened here?

The {current} value tells BCD to modify the currently running boot configuration.

The detecthal yes value tells to force a redetect of the of the hardware during boot

What will happen, is that at the next boot, the system will determine the best HAL to boot from and update the configuration to use it.

Thus, at boot, if the system has been moved from Hyper-V to Virtual PC, the HAL needed will change and the system will locate and update itself to use the new HAL.

This procedure should work for most optimizing Hyper Visors as they all require somewhat different HALs.

Posted on Monday, January 24, 2011 8:32 PM | Back to top

Comments on this post: Switching between Virtual PC 2007, Windows 7 VPC and Windows 2008 Hyper-V

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Tom Canter | Powered by: