Chris Nackers Blog

ConfigMgr and MDT Deployment Solutions

Useful Blogs

User Groups

Microsoft Deployment Toolkit – Tattoo Information

Another great feature of MDT integration with SMS/ConfigMgr is the information that is tattoo’d into the system during deployment.  Through the use of a sms_def.mof extension, you can then report against this information and create a web report or reports to identify imaged systems and the relevant information you want to see.

In the MDT documentation and scripts you will see “Tattoo” spelt “Tatoo”.  It’s been that way for a long time :) Just be aware, i’m not mispelling it. 

What I’ve done is created a web report that can show me when the system was imaged, the deployment type used (ZTI Refresh or a Media/PXE boot), the OSD adv ID, and the OSD Program Name used.  The below screenshot samples are specifically from SMS 2003 and MDT 2008, however the information is still relevant with SCCM and MDT 2010 and I’ve provided information for MDT 2010 and SCCM. 

When a system is built using MDT integration, the ZTITatoo.wsf script embeds this information into the registry, then using your MOF extension you can then collect and report against this information.

The following properties are available to MDT 2008:

 

DeploymentMethod, DeploymentType, OSDAdvertID, OSDPackageID, OSDProgramID, OSDSiteCode, OSVersion, TaskSequenceID, TaskSequenceName, TaskSequenceVersion

 

The following properties are available to MDT 2010:

DeploymentMethod, DeploymentType, DeploymentTimestamp, BuildID, BuildName,           BuildVersion, OSDPackageID, OSDProgramName, OSDAdvertisementID, TaskSequenceID, TaskSequenceName, TaskSequenceVersion

This is the process that runs with MDT 2008 and MDT 2010 per the MDT Documentation:

1. Locate and copy the ZTITatoo.mof file to the %SystemRoot%\System32\Wbem folder. Any preexisting ZTITatoo.mof that exists at the destination will be deleted before starting the copy operation.

2. Mofcomp.exe will be run using the following command: %SystemRoot%\System32\Wbem\Mofcomp.exe -autorecover %SystemRoot%\System32\Wbem\ZTITatoo.mof.

3. These deployment details are written to the registry at HKEY_LOCAL_MACHINE\Software\Microsoft\Deployment 4:

· Deployment Method is set to DeploymentMethod.

· Deployment Type is set to DeploymentType.

· Deployment Timestamp is set to the current date in WMI date format.

· Task Sequence ID is set to TaskSequenceID.

· Task Sequence Name is set to TaskSequenceName.

· Task Sequence Version is set to TaskSequenceVersion.

4. If OSDPACKAGEID is not NULL, these deployment details are written to the registry at HKEY_LOCAL_MACHINE\Software\Microsoft\Deployment 4:

· OSD Package ID is set to OSDPACKAGEID.

· OSD Program Name is set to OSDPROGRAMID.

· OSD Advertisement ID is set to OSDADVERTID.

5. If OSDPACKAGEID is not NULL, these deployment details are written to the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion:

· CM_DSLID is set to OSDSITECODE:OSDPACKAGEID.

Sample Web Report for SMS 2003/MDT 2008:

image

SMS 2003/MDT 2008 MOF Extension:

// MDT 2008 Deployment Data, added by (name) (date)
// ----------------------------------------------------

#pragma namespace ("\\\\.\\root\\cimv2\\sms")
[ SMS_Report     (True),
  SMS_Group_Name ("Microsoft BDD Info"),
  SMS_Class_ID   ("MICROSOFT|MicrosoftBDDInfo|1.0") ]
class Microsoft_BDD_Info : SMS_Class_Template
{
    [SMS_Report (TRUE), key ]  
        string InstanceKey;
    [SMS_Report (TRUE)      ]  
        string DeploymentMethod;
    [SMS_Report (TRUE)      ]  
        string DeploymentType;
    [SMS_Report (TRUE)      ]  
        string DeploymentTimeStamp;
    [SMS_Report (TRUE)      ]  
        string BuildID;
    [SMS_Report (TRUE)      ]  
        string BuildName;
    [SMS_Report (TRUE)      ]  
        string BuildVersion;
    [SMS_Report (TRUE)      ]  
        string OSDPackageID;
    [SMS_Report (TRUE)      ]  
        string OSDProgramName;
    [SMS_Report (TRUE)      ]  
        string OSDAdvertisementID;
};

ConfigMgr MDT 2010 MOF Extension:

// MDT 2010 Deployment Data, added by (name) (date)
// ----------------------------------------------------

[ SMS_Report     (True),
  SMS_Group_Name ("Microsoft BDD Info"),
  SMS_Class_ID   ("MICROSOFT|MicrosoftBDDInfo|1.0") ]
class Microsoft_BDD_Info : SMS_Class_Template
{

    [SMS_Report (TRUE), key ]  
        string InstanceKey;
    [SMS_Report (TRUE)      ]  
        string DeploymentMethod;
    [SMS_Report (TRUE)      ]  
        string DeploymentType;
    [SMS_Report (TRUE)      ]  
        string DeploymentTimeStamp;
    [SMS_Report (TRUE)      ]  
        string BuildID;
    [SMS_Report (TRUE)      ]  
        string BuildName;
    [SMS_Report (TRUE)      ]  
        string BuildVersion;
    [SMS_Report (TRUE)      ]  
        string OSDPackageID;
    [SMS_Report (TRUE)      ]  
        string OSDProgramName;
    [SMS_Report (TRUE)      ]  
        string OSDAdvertisementID;
    [SMS_Report (TRUE)      ]  
        string TaskSequenceID;
    [SMS_Report (TRUE)      ]  
        string TaskSequenceName;
    [SMS_Report (TRUE)      ]  
        string TaskSequenceVersion;


};

Comments

No Comments