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
Jonathan's Virtual Blog
Virtual Machine Manager - Orchestrator - Solutions and Guidance
In the last few weeks we have seen a few cases with an unusual error code: 0x800704DD. If you run into this issue the fix is simple. Our fearless leader Michael has posted a blog explaining the problem and how to fix it. Definitely worth a visit.
Direct Link: http://blogs.technet.com/m2/archive/2010/03/03/error-800704dd-happening-during-a-lan-migration-or-deployment-of-a-vm.aspx
Another great find by Michael Michael. He has this written up beautifully, so I’ll just provide a link. You may be affected and need a resolution if you have these conditions:
Reason and Solution provided here. Thanks again M2.
VMM Administrator Console taking too much time to load http://blogs.technet.com/m2/archive/2010/03/12/vmm-administrator-console-taking-too-much-time-to-load.aspx
Here’s a tip I’d like to pass on that resulted solely from trial and error.
I regularly see Failover Cluster, Hyper-V, NIC Teaming, VLANs, iSCSI networks and so on as components of a complex environment managed by SCVMM. Each of these components can affect decisions regarding network design. In the process of implementing the desired settings there will often remain a network, or NIC, that goes unused – even if temporarily. This unused NIC may have had a cable plugged in at some time, but for now there is no cable and the NIC shows a status in Windows of ‘Network cable unplugged.’ This seems harmless enough, but I’ve found it to be a real problem generator. Luckily, this has a simple fix: right click and select ‘Disable.’
So, a NIC left enabled but without a cable plugged in can cause problems. Make this correction, then retry whatever issue you previously experienced. I have resolved cases involving WMI, BITS, WinRM and so on. You might see these jobs affected:
SCVMM is not in any way more affected by an unplugged network cable than are other Microsoft products. SCVMM just touches many of these products and therefore can be affected in the same way they are. I hope this helps a few of you out there!