Your company's ad could live here and reach over 50,000 people a month!

Share This Post

Version 1.01: Document your Configuration Manager implementation

For those of you who have struggled with learning everything the hard way about a hierarchy that you “inherited,” you might find this utility handy.  Just double-click to launch it, enter the name of the server you want to know about and let it go.  It will pull in data about the server hardware config, SMS objects, and miscellaneous settings that might cause problems.  It will query Active Directory to look for stale computer objects and Configuration Manager client installation GPOs, and kicks off a copy of Russ Slaten’s overlapping boundary script found here:

* Since the questions answered by this utility are only of interest to Configuration Manager experts, error checking is minimal.  Post a comment if you find a bug.

** Querying a 64-bit OS from a 32-bit OS will bomb out when it can’t find the site code, but the opposite scenario works.  For best results, launch the utility from an 64-bit system.

Nothing is changed on the server queried.  Files are written to the temp directory and launching folder on the host system.  You should be a member of the local Administrators group on the server to read from the file system, and the SMS Admins group on the server (or parent server if it’s a secondary) to connect to the SMS provider.  More restricted rights are of course recommended, but look to permissions first when troubleshooting missing data.

Find the zipped executable file here:

[Edit: Thank you to Garth Jones for the reminder that there are several other tools that will ease your documentation, and his SCCM Documentation Script is a great example and a must-have for your toolbox. –  It will give you much greater detail on what you have, and even outputs to MS Word.]

[4/3/2012: Fixed a bug in reporting expired advertisements, added a check to run advanced features on demand.  These options query outside objects for overlapping boundaries, group policies, logon scripts and stale computer objects.  They can take a very long time to run, and thus make sense to run only when requested.  Thanks to Mike Schultz for identifying the expired advertisement bug, and to Greg Ramsey for his assistance in getting the lazy property to get off its lazy butt and do some work.]

Share This Post

Leave a Reply