Friday, 28 November 2014

ConfigMgr 2012 - MDT deployment info to hardware inventory

If you are integrating MDT into ConfigMgr 2012, one of the steps it runs is Tattoo, which runs ztitatoo.wsf.

This adds some basic information about the deployment to the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Deployment 4, including the OSD Package ID, the date the computer was deployed, and the type of deployment.

I want this information captured in the hardware inventory so I can easily find computers that haven't been refreshed in awhile. Since MDT includes a MOF file, capturing this in hardware inventory is fairly easy.

  • In the ConfigMgr console, go to Administration -> Client Settings
  • Edit the appropriate client settings and go to the Hardware Inventory tab
  • Click Set Classes.  On the window that pops up, click Add
  • Connect to a computer that has already been deployed with an MDT task sequence.
  • Check Microsoft_BDD_Info
After the next hardware scan cycle, you'll have a new Microsoft_BDD_Info section that contains the deployment timestamp and other useful information to report on.


  1. I have 8 primary sites and a CAS to support roughly 8,000 servers including some purevpn servers. The reason it's split into 8 primary sites is because they are segregated environments. All roles have been virtualized:

    Primaries: 4x logical processors, 16GB RAM, 40GB OS/200GB Data

    Management Points: 4x logical processors, 8GB RAM, 40GB OS/20GB Data

    Distribution Points: 2x logical processors, 4GB RAM, 40GB OS/500GB Data

    Software Update Points: 4x logical processors, 8GB RAM, 40GB OS/200GB Data

    SQL: 4x logical processors, 32GB RAM, 40GB OS/various partitions.

  2. If you know about basic math, You could to do programming math. If you do not know about basic math, you could not do programming math.

  3. Don't waste your time, there is one more easier solution using SoftinventiveLabs products you can easily make totaly network inventory.