When SCVMM is not ‘cooperating’ and no amount of digging through event logs, support articles, and forums is helping… it’s time for a trace. (What happened to SCTrace?!? See bottom of this post.)
Don’t think of tracing as a first step. Think of it instead as a solid backup plan. When you’ve made it through these items and still are no closer to resolution you are ready for ‘the trace.’
Check event logs on all systems for possible clues
Verify the basics again: DNS resolution in all directions, permissions, services…
No luck? Grab a trace.
SCVMM Gurus (and those averse to reading instructions)
Download the tool below. Be sure to run it on all affected systems. Use an elevated command prompt.
Everyone Else (wanting to capture the right data)
Download the tool above, then identify your scenario and run the tool on the right systems at the same time. Use an elevated command prompt.
Console crash or unable to connect
Collect traces from both the computer where you run Admin Console and the VMM Server
Add Hosts issues
Collect traces from the VMM Server and the Host system
Host status or VM issue
Collect traces from both the VMM Server and the Host in question
Collect traces from a single Cluster Node and the VMM Server
What happened to SCTrace?!?
Frequent readers of this blog may be aware of a previous tracing tool called ‘SCTrace’. It has been retired as this new script is up to 8x more efficient* and 2x as enjoyable* to use. Also, VMMTrace is a cooler name. And, it has been rewritten to be region independent of date format and other improvements.
*Statements in no way verifiable, but sound impressive.
Quick link: http://tiny.cc/vmmtrace
Original post here.