VMM ReproVMM 2012 SP1 and R2 - Data collection
SCOtrace - Orchestrator TracingAutomated data collection for SCO
Unsupported Cluster ConfigurationScript and post
VMM State Recovery ToolRepair Database state errors
SC 2012 VMM CAFirst line of defense in troubleshooting
Orchestrator Text Manipulation
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
Manage and Automate
VMM SCO SMA WAP - Solutions and Guidance
Two new updates have been released for System Center 2012 and for System Center 2012 SP1. There are many fixes in these rollups, so treat them as mandatory, not optional. Links below. Happy troubleshooting!
System Center 2012
Description of Update Rollup 7 for System Center 2012
System Center 2012 SP1
Description of Update Rollup 4 for System Center 2012 Service Pack 1
As a support engineer at Microsoft, I see almost daily some issues with Service Principle Names (SPNs). SPNs are as important to VMM communication as DNS. They are attributes on DNS entries that allow other services to find VMM. This is not a new issue, and this article covers how SPNs should be set up on your system. If everything is working well, please do not make changes. To see if you have SPNs registered correctly, at an elevated command prompt type ‘setspn –L <computername>’. This will list what is registered. You DO want to find SCVMM/Hostname and SCVMM/FQDN in the list. Below is only an example. Good luck with the article!
You may have problems with Virtual Machine Manager if some SPNs are missing http://support.microsoft.com/kb/2123063