My SEPM server decided to do the BSOD the other night, at about 2:00am. Nice. Right when a few users from India were working on the server, which also happens to be our Terminal Server.
Thankfully, I didn't get a call.
I can't wait until MR2 comes out. Some of the touted improvements is a lighter weight processor footprint, fixed graphics (mine ALWAYS work at the console, just not remotely...), and I'm sure numerous other fixes.
I hope I don't have to run around the office yet AGAIN to use their sylink tool reconnect my clients. I had originally scripted it, but it doesn't work if you impose password protection on the UI...hmph...
I'd also found that logging on some of the clients was out of control. Saw many posts on Symantec's user forums to this affect, and my uninstalling and reinstalling seemed to fix that, for now.