You are browsing the archive for SccmAutoDoc.

Techdays 2010 Here we (The Scug team) come

1:48 pm in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, configmgr2007, sccm, SCCM 2007, SCCM 2007 R2, sccm2007, SccmAutoDoc, SMS by Kenny Buntinx [MVP]

Hi All,

160x600Just received confirmation that I will have a speaker slot again, for the 4th year in a row at the Belgian Techdays.

So me, and the rest of the Belgian SCUG team will be present to talk to you about System center configuration manager, system center operations manager and even system center service manager by then, as Kurt Vanhoecke our local service manager expert that even got referenced at the service manager product team blog, will most likely be there as well.

My session will be a pretty non-typical SCCM session this year. From my personal experiences, i.o.w. by authoring SccmAutoDoc, I believe I learned a few extra things on ConfigMgr and WMI. Even in the past I have considered knowledge of WMI an incredible asset for any SMS/SCCM admin, but deepdiving into it for SccmAutoDoc has only enhanced that belief.

So without further ado, here comes the session abstract:

Since its first debut System Center Configuration manager and its predecessors have been relying heavily on the Windows Management Instrumentation (WMI) architecture. WMI is omni-present is System Center Configuration Manager, from queries over dynamic collections, through hardware inventory and storing client and Management Point settings and policies, under the hood you will find WMI just about anywhere. Given this omni-presence it should come as no surprise that the stability of WMI at your Site Systems and clients is crucial to a stable System Center Configuration Manager implementation. Knowing WMI, by consequence, is a great asset to any System Center Configuration Administrator. In this session you will learn the ins-and-outs of the WMI architecture in general and how it applies to System Center Configuration Manager. You’ll learn about the available namespaces and classes and the extended WMI Query language (WQL) that is specific to System Center Configuration Manager. This session will cover the tools available to have a peak at WMI yourself as well as to the WMI-related tool called policy spy that comes with the System Center Configuration Manager toolkit. By the end of this session you’ll know what the WMI architecture looks like, how System Center Configuration Manager uses it, and how you can use that knowledge to your advantage, be it to be able to better troubleshoot System Center Configuration Manager issues, better understand the product, or to automate tasks through scripting or programming. In the end this session will make you a better System Center Configuration Manager administrator.


I sincerely hope to see you all there, and before I forget, best wishes to everyone reading this.

Kim Oppalfens

System Center Configuration Manager MVP

SccmAutoDoc by OSCC goes Beta 1

7:52 am in beta, ConfigMgr 2007, ConfigMgr 2007 R2, OSCC, SCCM 2007, SCCM 2007 R2, SccmAutoDoc by Kenny Buntinx [MVP]

What is SccmAutoDoc?

SccmAutoDoc is a command-line utility that documents a System Center Configuration Manager 2007 site in a human-readable format. Much effort has been put in making the document resemble closely to what you see in the Configuration Manager admin console. SccmAutodoc in other words documents your Site Configuration.

Additionally the goal is to document only relevant settings, and to not include items that are irrelevant. For example if the software inventory client agent is disabled, than it doesn’t make much sense to document the software inventory agent schedule.

What are the software requirements to be able to use SccmAutoDoc?

SccmAutodoc requires a machine with Word 2007 installed and access to the ConfigMgr site server and ConfigMgr Sms Provider. Word 2007 does NOT need to be installed on the Site server/SQL server or Sms Provider computer. The program can perfectly work from a remote machine running windows xp, Vista or Windows 7.

Word 2007 does need to have the primary interop assemblies installed, but these are part of a default word 2007 install. If you don’t have the primary interop assemblies for office 2007 installed, you can always download them here: <>

What permissions do I need to run SccmAutoDoc?

SccmAutoDoc requires a user with Read permissions on the site object of the Configuration Manager site to be documented. The commandline allows you to optionally pass a user and password as arguments to perform the documentation. If you don’t specify a username and password than the currently logged in credentials are used.

Where can I get SccmAutoDoc?

SccmAutoDoc beta1 can be downloaded from

How do I use SccmAutoDoc?

Just unzip the zipfile to a folder (the zip contains sccmautodoc.exe 2 dll’s and an xml file).

Then execute SccmAutoDoc from a command prompt, which will display the Usage statement.

Sample commandlines:

Ex1: sccmautodoc -sitecode S01 -server sccm01
     This command documents the site with sitecode S01 on server sccm01 with the user
     account that launched SccmAutodoc
Ex2: sccmautodoc -sitecode S01
     This command documents the site with sitecode S01 when running locally on the server.
Ex3: sccmautodoc -sitecode S01 -server sccm01
       -username Contosso\sccmadmin -password P@ssw0rd
     This command documents the site with sitecode S01 on server sccm01 with the user
     account Contosso\SccmAdmin and password



Where can I send bug reports/feature request/suggestions?

All comment/bug reports/suggestsions/feature request are more than welcome at .

Unless I am swamped with suggestions, I will do my utmost to respond to any inquires you might have.

If you send a bug report, please include the error you are receiving and a copy of the document created by the execution that errored out.

Is SccmAutoDoc freeware?

SccmAutodoc is not freeware, at present it is beta software, that eventually might end up as a reasonably priced documentation tool.

Preliminary plans around licensing are around creating a ConfigMgr Site, ConfigMgr hierarchy, Consultant/Consultancy firm license.

When does this beta Expire?

This beta version expires on the 15th december 2009. At which point a new version (Beta 1.5 of Beta 2) should be available.

What does SccmAutoDoc currently document?

SccmAutoDoc currently documents everything you see in the ConfigMgr Admin Console underneath the Site Settings node, with some small exceptions listed below:

  • Address schedule and Bandwidth limiting configuration.
  • Certificates node
  • Status Filter Rules

For a sample on what SccmAutoDoc documents have a look at SccmAutoDoc-1.125-Sample at:

SccmAutodoc currently has no plans to document “volatile” data. In other words, packages, programs, advertisements, … Will Not be documented. It is determined that this data changes to often, which would require SccmAutoDoc to run several times a day. Additionally the documentation would then become quite large making it lose its purpose as a Site Configuraiton document.

What are some of the known issues so far with SccmAutoDoc?

SccmAutoDoc errors out if you open up a focus-capturing box in Word while the program tries to write data to the document.

How does SccmAutoDoc work?

SccmAutoDoc works by querying WMI and parsing the results to look like they appear in the ConfigMgr Admin console. The main engine behing SccmAutoDoc is the included XML file which lists the queries that are executed.