I got error 0xc00000e9 when attempting to boot into a new guest Hyper-V image, using an ISO image as my boot CD. Using the real CD in the host worked fine.
So I downloaded the ISO again and all was well this time - must have been a dodgy download - now to go play with Windows Small Business Server 2008.
Labels: hyper-v, sbs 2008, server core, virtual server, windows
permalink posted by Brian Reid : 6:08 PM
0 comments 
This rather imposing message is found if you try to force replication between to Active Directory Domain Controllers when one of the controllers machine account password is out of sync with the password as stored on the other domain controller.
I have seen this a number of times on Virtual PC or Virtual Server Active Directory deployments with more than one DC in the virtual environment.
So, how do you fix it:
- On the DC that is broken (the one that when using replmon reports the error above) set the Kerberos Key Distribution Center Service to manual and stop the service.
- From a command prompt on the broken DC enter the following:
netdom resetpwd /s:name_of_working_DC /ud:domain\user /pd:*
where domain\user is an administrator of the domain in the domain_name\user_name format. You will be prompted to enter your password. - Upon pressing Enter, if the command fails then restart the broken DC and repeat the above command (this restart clears the Kerberos ticket cache and so clears the broken credential attempts that it has stored).
- Upon successful completion of the command in step 2 restart the broken DC. You must do this even if done already in step 3.
- Check that replication is working, and if so restart the Kerberos Key Distribution Center Service and set the service back to automatic.
This is a summary of Microsoft Knowledgebase Article 325850, with some more specific detail mentioned.
Labels: 2003, 2007, active directory, error, exchange, kerberos, virtual pc, virtual server
permalink posted by Brian Reid : 4:06 PM
0 comments
Today I booted a virtual machine that was provided for me by a client so that I could prep a training course, but I could not log into the virtual machine because it blue-screened with a driver called intelppm.sys failing (and supposedly processr.sys can cause the same problem, but I have not experienced that one yet). Note that the virtual machine might just reboot rather than blue-screen because that is what it is configured to do.
The blue-screen is due to the virtual machine running on an AMD K8 or Centrino platform and the above device driver attempting a unsupported command that was supported on the platform that the virtual machine was originally created under. You can disable these drivers without issue in the virtual machine - just you cannot login to disable them!
So you need to use Safe Mode. Press the F8 key repeatedly as the virtual machine boots and then choose Safe Mode from the on-screen menu. Once you have logged in run these two commands from a command prompt (note that where the spaces are is important):
sc config processor start= disabled
sc config intelppm start= disabledYou should get a SUCCESS message returned. Once you do you can shutdown the virtual machine (and commit changes if you are have undo disks enabled) and then start the machine up normally.
This problem has been fixed under Virtual Server 2005 R2, but is still an issue with Virtual PC 2004 and Virtual Server 2005.
Labels: virtual server
permalink posted by Brian Reid : 10:19 AM
0 comments
Archive
March 2005
July 2005
February 2006
May 2006
November 2006
March 2007
May 2007
June 2007
August 2007
April 2008
May 2008
June 2008
September 2008
October 2008
November 2008
January 2009
February 2009
March 2009
April 2009
May 2009
June 2009
July 2009