I'm Robert Marshall, director and principle consultant at SMSMarshall Ltd, who's specialism is in the Microsoft System Center 2012 Configuration Manager product and all of its dependent products, covering all aspects from Architecture, Implementation, Migration to Break-Fix.
I've been in front of computers for over 30 years now, with my roots in programming 8 bit computers, I've taken an often exciting journey which has led to becoming an expert in an enterprise product. I consider my career as starting 17 years ago, when I began my first serious role as a deployment engineer. I've seen 8 bit through to 64 bit, the rise and refinement of the interface we take for granted now, the rise of the Internet from land-line based modem access for the few, to the powerful broadband connections we have today for the masses, I saw mobile phones come into existence, and I've seen Microsoft evolve from more than a handful of employees to the company it is now, while pretty much tinkering with every OS they have released, as well as seeing an industry that has evolved around those humble beginnings to become what we have today. I'm a keen technical puzzle solver, I love to solve gnarly problems around my area of specialism. And, I love to share when I have time. I hope you enjoy the blog.
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.