I'm Rob Marshall, a consultant who specialises in the Microsoft System Center Configuration Manager product. I like to share, i do so by blogging and helping out when I can in the MS SMS newsgroups and participating in the ConfigMgr MVP program.
I was awarded and joined the program in 2009. It'd be an understatement to say it has to be one of the best experiences an IT engineer can have, if they really enjoy specialising in a product.
My biggest weapon for troubleshooting is, my formidable knowledge, no, only joking, you, the community. I find if I cannot answer a question, then I can usually find the answer from using Bing\Google, pouring over the documentation, and if that doesn't work, tinkering in mine or someone elses virtual lab.
The blogs pretty much about ConfigMgr, but it is also a platform for me to express my random urges to display something I've stumbled across, and that I imagine would entertain you or what not as equally as it did me.
In July 2009 we started experiencing Print Spooler crashes on our W2K3 SP2 print servers.
Check the event log and you'll see something akin to this:
Faulting application spoolsv.exe, version xxxxxx, faulting modeul gdi32.dll, version xxxxxxx, fault address 0x00037453
This seems to have been induced by the July 2009 patch KB961371 - MS09-029.
This patch has been re-released to the public, and I can confirm it does indeed fix the problem. It can be found it here for W2K3 SP2:
http://www.microsoft.com/downloads/details.aspx?familyid=018ef53d-f78e-4084-940d-7c86bf59d83c&displaylang=en
The bulletin here:
http://www.microsoft.com/technet/security/Bulletin/MS09-029.mspx