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.
I just thought up (without any RedBull, other energy drinks or Omega 3 supplements) a great new term on how to describe the patches that need to go on to a machine.Let's posit that The patches that need to be installed on a target machine are dictated by the applications installed ...
We all know that right, but have any of us verbalised it beyond saying "patches"?I have, and I call it the "Patching Profile"Yes indeed ... I Rob Marshall thought this one up, it will enter the ConfigMgr canon, the lexicon of terms to describe a patching state and may very well end up in the OED next week :-)Gather around, revere me for my ability to come up spontaneously with amazingly insightful and description terms :-)