okay, calm down. i'm totally sensationalizing the actual issue. had a domain controller go sour this morning, basically no longer advertising sysvol. here's a sample of the event:
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Time: 12:00:00 PM
Computer: <Computer Name>
Faulting application svchost.exe, version 5.2.3790.3959, faulting module netman.dll, version 5.2.3790.3959, fault address 0x0000000000008d4f.
it isn't immediately obvious, but this problem is actually caused by opsmgr (as in the blog title implies). to be absolutely fair, opsmgr isn't actually at fault. however, it pounds the crap out of netman.dll which exposes a bug, causing the failure of the server service. when you lose the server service, you lose any process running spawned from svchost. that's a lot of stuff.
here's the full article: http://support.microsoft.com/kb/2670298. it also links back to kevin holman's blog. ;-)