OMG, we had the exact same issue last week. Read the fix below.
We have multiple Hyper-V Hosts, all identical with 2008 R2 Datacenter. However, one of the Hosts has the WDS Role + MDT 2010 installed.
You won't believe what happened in a production environment, when a users asked me to reboot one of the VM's... after opening the Hyper-V console, there were no VM's listed! When I restarted the vmms service, I got an error saying "could not find the file
specified". WTF.
After examining the logs, in one of the Hyper-V Worker logs, I found an error that the InitialStore.xml file could not be found. First, I wanted to check the disk array using the HP ACU, but the shortcuts in the Start Menu were missing! Then I saw that the
Administrative Tools menu was completely empty. Right click on "My Computer"-> Manage didn't work either, so... here we are... a production machine, completely unmanagable.
Oh, and one other thing: when I wanted to use Remote Desktop to this host using my Windows 7 machine, I got an error saying that NLA is required! Win7 has NLA support, but I was unable to logon. Thanks to iLO I was able to change the RDP settings to "less
secure", and then I was able to connect using RDP again.
I started by examining the C:\ProgramData folder. This is where the InitialStore.xml file is stored, and indeed: it was missing, but it felt like A LOT of folders were missing in the ProgramData folder. I logged in on another Hyper-V Host, and compared the
ProgramData folder. I was missing 7 folder in ProgramData root and about 12 folders in ProgramData\Microsoft!
My solution was to use WSB (Windows Server Backup) and restore the complete ProgramData folder to something like C:\ProgramDataRestore. This is about 30 MB, so you'll have all the missing files within seconds. I made a backup of the
current ProgramData folder, and then simply copyed ALL files/folders from the restore folder to the ProgramData folder with NO OVERWRITE, just merge.
Log off -> Log on -> everything was fixed! Start Menu was ok, Administrative Tools are back, changed RDP settings to NLA and worked!, Started hyper-v vmms service and started, opened Hyper-V console and YES all VM's where there!
To make this fix permanent: first thing to do: move WDS and MDT 2010 to a VM, or a non-Hyper-V Host or whatever.
-
Proposed as answer by
MpDay
Friday, January 20, 2012 9:14 AM
-
Edited by
MpDay
Friday, January 20, 2012 9:17 AM