MDT 2008 Tattoo mof edit
By request, and untested, the tattoo placed in the registry for the HKLM\software\deployment 4\Deployment Method string regkey.
//`'`*._.*`'`*-
// Reporting Class - for ConfigMgr, put this section in sms_def.mof
//`'`*._.*`'`*-
[SMS_Report(TRUE), SMS_Group_Name("MDT2008 Tattoo"),SMS_Class_ID("Microsoft|MDT2008_Tattoo|1.0")]
class MDT2008_Tattoo : SMS_Class_Template
{
[SMS_Report(TRUE),key] string KeyName;
[SMS_Report(TRUE)] string DeploymentMethod;
};
//`'`*._.*`'`*-
// Data Class - for ConfigMgr, put this section in configuration.mof
//`'`*._.*`'`*-
[DYNPROPS]
class MDT2008_Tattoo
{
[key] string Keyname="";
string DeploymentMethod;
};
[DYNPROPS]
instance of MDT2008_Tattoo
{
KeyName = "MDT2008 Tattoo";
[PropertyContext("local|HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Deployment 4|Deployment Method"),
Dynamic,Provider("RegPropProv")] DeploymentMethod;
};
NOTE: The above was formatted for ConfigMgr, if you are on SMS2003 remember to add in #pragma namespace("\\\\.\\root\\cimv2\\SMS") under the // Reporting class comment, and #pragma namespace(\\\\.\\root\\cimv2) under the //Data class comment. Under sms2003, those #pragma namespace entries are to inform WMI where the following lines reference. In ConfigMgr, sms_def.mof is only for stuff in root\cimv2\sms, and configuration.mof is only for stuff in root\cimv2, so you don't have to repeat yourself. It won't hurt it to put in it, but it's kind of redundant.