For part of our upgrade process, we decided that we wanted to give users the opportunity to complete a survey to give us their feedback on the upgrade process. We thought of an email but, figured that would be just as well ignored as any other bulk email. So, I thought we could just dump something in the run once, or startup for the user that initiated the upgrade. So, the first thing I needed to do was capture the user to a task sequence variable. Sounds easy but, remember, the task sequence runs as system.
Often I get access requests, especially for new employees, for setting up someone’s network permissions like Dan's in the marketing department. Dan is new to the Marketing team and his manager wants his account set up like Paul's account. So, normally, I would do a side by side comparison in ADUC and then fill in the gaps. That sounds a little tedious. So, I wrote a quick function to compare groups and output those that are common between each and unique to each. Here is a sample of the output from the function:
My coworker and I have recently had a little bit of fun with status messages, using them to trigger emails and other alerts to admins etc. In playing with them, I was curious on just how many there were, or could be rather. I then stumbled across this technet gallery post. So, yes you can do whatever you are trying to track and view all status messages that are sent to CM but, this may be useful in helping narrow that down ahead of time.
So, here we go.
For those that have used RegKeyToMof to create custom inventory MOF files to inventory registry keys, or export a mof from one environment and import them into another know that it is a fairly easy to do process. I have now seen on a few occasions now where the MOF file fails to import. No matter what you do, it will not import. You receive the following error:
With how easy it is to upgrade Configuration Manager now, it can be easy to forget about the most important component of your CM infrastructure, SQL. I'm guessing that a number of us are still running SQL 2012. Why? Because when we built our CM 2012 environment, that's what was the latest for SQL at the time. So, a number of CM environments are still running 2012.
Originally posted on the Cyber Advisors blog on May 7, 2018. Updated and expanded below.
Administration of Configuration Manager is more than a full-time job by itself. Maintaining some sort of documentation for the environment that can be given to management or stored internally can be an all together second job. So, why continue a manual task of creating documentation when you could automate it and have an extensive and detailed document created in minutes instead of hours.
I have borrowed stuff from the community for years and haven't given much back. I can blame it on being busy but, mostly blame it on being lazy. So, I've been wanting to start to give back. And, I thought for me a blog would be a great way.