ha10

Testing 2008 R2, I learned that SysInternals NewSID breaks the VM.  Yuck.

My work around, run sysprep.  Start > Run > Sysprep

Doubleclick on Sysprep to run the application

Choose System Cleanup Action: Enter System Out-of-Box Experience (OOBE) and check Generalize.

If you miss the Generalize check, sysprep will not generate a new SID.

Click OK.  Sysprep will now prepare the VM and shutdown/reboot.

After rebooting, it takes quite a while to get to the OOBE.  But at least it works.  Besides, Microsoft stopped supporting OS’s that have been prepared with NewSID some time ago.  So I guess this is a good thing then.  Maybe.

I have found that Hyper-V is easily broken by any on access virus scanning software.  To make life easier, if you are running Hyper-V, or plan to.  Put these exclusions in your vurs scanner:

• Default VM configuration directory: C:\Program Files\Microsoft\Windows\Hyper-V
• Custom VM configuration directory
• Default virtual hard disk directory: C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks
• Custom virtual hard disk directories
• Snapshot directories
• C:\Windows\System32\Vmms.exe
• C:\Windows\System32\Vmwp.exe