Using Windows Server 2008 or Vista SP1 with Virtual PC 2007...

by Rich Rousseau 31. December 2008 23:24
If you want to use Windows Server 2008 or Vista SP1 as a guest operating system with Virtual PC 2007, you'll need Virtual PC 2007 SP1. Updates for both x86 and x64 clients are available. Not sure if you could get either of these working using a different OS selection in VPC. I'm eager to try out the remoting feature in Powershell v2 and currently these operating systems are they only ones that support Powershell remoting.

SkiFree!

by Rich Rousseau 12. March 2007 11:18
Classic computer games never get old. People will always find a way to play their favorite games. If it's playing Quake I on your PocketPC, slinging bananas at each over in Gorillas, or firing up Windows 3.11 in VirtualPC to play SkiFree. Virtual PC Guy linked over to The Most Officialest SkiFree Home Page! where you can get a 32bit build of this classic game. I didn't have this game on my first windows machine (386SX - Windows 3.0), but if I recall correctly I first played it on my friend Tony's screaming fast 486DX (we both had Packard Bell's at the time...who didn't?)...

Scoot over World of Warcraft, I gotta see if I can outrun the Abominable Snow Monster this time.

 

Virtual PC 2004 Issue...

by Rich Rousseau 1. February 2007 08:34
I use virtual envionrments fairly regularly at work.  I mainly use them for app debugging in a clean environment,  permissions testing, and automated deployment testing.

I have a Virtual PC 2004 setup with my base OS installed on it's own virtual hard drive.  I create a new differencing vhd on top of that when I need a fresh environment to work in.  This has worked very well for me until today. 

I created a new differencing vhd and booted into it.  Everything was fine until I tried to login.  I received the following message box...

Windows cannot connect to the domain, either because the domain controller is down or otherwise unavailable, or because your computer account was not found.  Please try again later.

At first I thought that my domain wouldn't let me logon because I had a bunch of updates to install.  After letting the vm run for 20 minutes I restarted it, installing all the updates it downloaded.  (On a side note, I didn't know windows would download updates even when you're not logged in.).  Even after that, no luck.

Google to the rescue...An old newsgroup post hinted that it might be because my (virtual) computer already existed on the domain.  The solution, login as the local admin, take the computer off the domain and put it back on.  Success!

I'm posting this in hopes the answer will be more accessible to future generations of googlers.