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.
One of the best tricks for us sms admins to use while troubleshooting access (amongst other things) is to use a CMD prompt elevated to SYSTEM context. A godsend for those of us that are permissions challenged, such as Secondary site servers that we the sms admins have no permissions to access, but the parent site server does, or doing diagnostic tests (such as running Internet Explorer in SYSTEM context etc).
Traditionally, we could pull this off on pre-Vista\W2008 OS's, but Microsoft have controls in place now to try to stop this kind of elevation from taking place (session 0 isolation).
Kim Oppalfens linked me to Ben Griswold (JohnnyCoders) blog on how to make it happen. Definitly worth a read.