VMM 2008 - 2012 Data collection
VMM ReproVMM 2012 SP1 and R2 - Data collection
SCOtrace - Orchestrator TracingAutomated data collection for SCO
VMM State Recovery ToolRepair Database state errors
SC 2012 VMM CAFirst line of defense in troubleshooting
VMM Networking Poster Illustrates networking for VMM 2012 SP1
VMM 2012 Technical Documentation, including Step-by Step Guides
VMM 2012 Official Cmdlet Reference
VMM 2012 TechNet Launchpad
VMM 2012 PowerShell Cheat Sheet
VMM 2008 PowerShell Cheat Sheet
2008 R2 Guides and Reference Downloads!
VMM 2008 Interactive Decision Flow
Jonathan's Virtual Blog
Virtual Machine Manager - Orchestrator - Solutions and Guidance
A friend and co-worker discovered an interesting fix for a failed SCVMM P2V attempt involving Windows 2000 SP4. We’ve seen this same type of issue when converting Windows 2000 systems for years, and WMI is often part of the issue. Mike has provided an article listing three WMI updates that overcome many of the challenges we have seen. In the first day of this article’s publishing we fixed two cases involving P2V of Windows 2000. I can’t suggest strongly enough that you read his post and apply the hotfixes. Thanks Mike! Great contribution!
Jump to the article here.
The specific hex we have seen this most applicable to is 0x80041001, but not limited to only this error.