Sherry Kissinger at myITforum.com

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.

McAfee 8.x Enterprise sms_def.mof Edit - ConfigMgr

I had a blog entry for SMS2003; but now that I'll be soon going to production w/ConfigMgr myself, thought I'd share some of the edits.

As you may or may not know, the main differences between SMS 2003 and ConfigMgr 07 are:

• No more need to mofcomp on the clients
• sms_def.mof is for the Reporting classes (what makes up the policy that the clients pick up from the MP)
• configuration.mof is for the Data classes (what the clients auto-compile when changes are detected, like this one)
• No more need to add the #pragma namespace("\\\\.\\root\\cimv2") or #pragma namespace("\\\\.\\root\\cimv2\sms"); because you are no longer switching between data & reporting classes within the same mof file.

With that in mind, below are what you would add to sms_def.mof and configuration.mof on your primary site servers' inboxes\clifiles.src\hinv in order to enable reporting on McAfee 8.x and EPO 3.x

Add to SMS_Def.mof, at the bottom

//  <:[-<>>>>>>>>>>>>>>>>>>>Start>>-Network Associates/McAfee Anti-Virus-<<Start<<<<<<<<<<<<<<<<<>-]:>
//`'`*._.*`'`*-
//  McAfee Reporting Class
//`'`*._.*`'`*-
[SMS_Report(TRUE),SMS_Group_Name("McAfee_Virus_Scan"),SMS_Class_ID("SMSExpert|McAfee_Virus_Scan|1.0")]
Class McAfee_Virus_Scan : SMS_Class_Template
{
  [SMS_Report(TRUE),key]  string  KeyName;
  [SMS_Report(TRUE) ]     string  szCurrentVersionNumber;
  [SMS_Report(TRUE) ]     string  szDatVersion;
  [SMS_Report(TRUE) ]     string  szEngineVer;
  [SMS_Report(TRUE) ]     string  szEngineVerMinor;
  [SMS_Report(TRUE) ]     string  szDatDate;
};
//  <:[-<>>>>>>>>>>>>>>>>END>>-Network Associates/McAfee Anti-Virus-<<END<<<<<<<<<<<<<<>-]:>
//  <:[-<>>>>>>>>>>>>>>Start>>-Network Associates/McAfee ePO Agent-<<Start<<<<<<<<<<<<<<>-]:>
//`'`*._.*`'`*-
//  McAfee ePO Agent Reporting Class
//`'`*._.*`'`*-
[SMS_Report(TRUE),SMS_Group_Name("McAfee_ePO_Agent"),SMS_Class_ID("SMSExpert|McAfee_ePO_Agent|1.0")]
Class McAfee_ePO_Agent : SMS_Class_Template
{
  [SMS_Report(TRUE),key] string  KeyName;
  [SMS_Report(TRUE) ]    string  szePOVersion;
  [SMS_Report(TRUE) ]    string  szePOName;
  [SMS_Report(TRUE) ]    string  szePOGUID;
  [SMS_Report(TRUE) ]    string  szePOInstallPath;
};
//  <:[-<>>>>>>>>>>>>>>>>END>>-Network Associates/McAfee ePO Agent-<<END<<<<<<<<<<<<<<>-]:>

Add to Configuration.mof, at the bottom

//  <:[-<>>>>>>>>>>>>>>>>>>>Start>>-Network Associates/McAfee Anti-Virus-<<Start<<<<<<<<<<<<<<<<<>-]:>
//`'`*._.*`'`*-
//  McAfee Data Class
//`'`*._.*`'`*-
[DYNPROPS]
Class McAfee_Virus_Scan
{
  [key] string  KeyName="";
        string  szCurrentVersionNumber;
        string  szEngineVerMinor;
        string  szDatVersion;
        string  szEngineVer;
        string  szDatDate;
};
//`'`*._.*`'`*-
// Instance of McAfee for Enterprise 8.5
// Contributed by Jane McLeish/Sherry Kissinger
//`'`*._.*`'`*-
[DYNPROPS]
instance of McAfee_Virus_Scan
{
  KeyName="McAfee Enterprise 8.5";
  [PropertyContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\McAfee\\AVEngine|EngineVersionMajor"), Dynamic, Provider("RegPropProv")] szEngineVer;
  [PropertyContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\McAfee\\AVEngine|EngineVersionMinor"), Dynamic, Provider("RegPropProv")] szEngineVerMinor;
  [PropertyContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\McAfee\\AVEngine|AVDatVersion"), Dynamic, Provider("RegPropProv")] szDatVersion;
  [PropertyContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\McAfee\\DesktopProtection|szProductVer"), Dynamic, Provider("RegPropProv")] szCurrentVersionNumber;
  [PropertyContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\McAfee\\AVEngine|AVDatDate"), Dynamic, Provider("RegPropProv")] szDatDate;
};
//  <:[-<>>>>>>>>>>>>>>>>END>>-Network Associates/McAfee Anti-Virus-<<END<<<<<<<<<<<<<<>-]:>
//  <:[-<>>>>>>>>>>>>>>Start>>-Network Associates/McAfee ePO Agent-<<Start<<<<<<<<<<<<<<>-]:>
//`'`*._.*`'`*-
//  McAfee ePO Agent Data Class
//`'`*._.*`'`*-
[DYNPROPS]
Class McAfee_ePO_Agent
{
  [key] string  KeyName="";
        string  szePOVersion;
        string  szePOName;
        string  szePOGUID;
        string  szePOInstallPath;
};
//`'`*._.*`'`*-
//  Instance of McAfee ePO 3x
//`'`*._.*`'`*-
[DYNPROPS]
instance of McAfee_ePO_Agent
{
  KeyName="McAfee ePO 3.x";
  [PropertyContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Network Associates\\ePolicy Orchestrator\\Agent|Installed Path"),Dynamic,Provider("RegPropProv")] szePOInstallPath;
  [PropertyContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Network Associates\\ePolicy Orchestrator\\Application Plugins\\EPOAGENT3000|Version"),Dynamic,Provider("RegPropProv")] szePOVersion;
  [PropertyContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Network Associates\\ePolicy Orchestrator\\Agent|ComputerName"),Dynamic,Provider("RegPropProv")] szePOName;
  [PropertyContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Network Associates\\ePolicy Orchestrator\\Agent|AgentGUID"),Dynamic,Provider("RegPropProv")] szePOGUID;
};
//  <:[-<>>>>>>>>>>>>>>>>END>>-Network Associates/McAfee ePO Agent-<<END<<<<<<<<<<<<<<>-]:>

MMS2008 - Thursday 1

Session:  Device Management on ConfigMgr.  It was interesting; but since we're 99.9% blackberries, and with SC Mobile Manager; I think if we're going to go with a management product, probably we'd go with Mobile Manager.  Although maybe (if time permits), deploy just the inventory piece, just so we know what's out there.

Session: SUS in ConfigMgr. 

Session: Case Studies Deep Dive.  Some good tips on log files to check, utilities to use (procmon) when troubleshooting an issue.  Pointed out a script for refreshingServerComplianceState if you happened to have accidentally deleted a record in the console--to get installed hotfixes reported correctly, you may need to deploy that to those clients.  A good walkthrough on what log files to hit when tracing a SW distrib. 

My favorite (because sms_def.mof/configuration.mof were mentioned, I'm such a geek): reporting stuff go in sms_def.mof, new classes go into configuration.mof.  I've actually seen that 2-3 times from people either in the forums or email to me; where they are trying a new mof snippet, and their Hardware Inventory Action disappears from the client's Agent listing.  That happens because technically the mof snippet added passes a mofcomp -check, so it is compiled successfully, but it confuses the client; so the client just gives up on HW Inv.

Another good one... when the firmware on the client computer isn't up-to-date, and the end user turns off their computer by holding in the power button for several seconds; the WOL magic packet "doesn't work".  The read-between-the-lines I got out of that was </sarcasm on> 'of course ConfigMgr is broken' </sarcasm off> :-) .  The fix was to update the bios firmware and/or change the BIOS setting of "when holding down the power button, go into suspend, not power off".    The presenter mentioned that other computers doing start/shutdown worked just fine in this company.  Apparently, the train-the-user how to click Start, Shutdown to politely shutdown their computer was not an option for this particular call. *shrug*  I'm guessing that the solution of 'problem is between the chair and the computer' wasn't a politically correct response.  :-)

Tonight: the closing party.  If I remember right it's "themed bars" (whatever that means), and Xbox Rock Band competitions.  Since the MyItforum booth had RockBand available for people to practice on for tonight... I'm hoping for a couple good "bands"!

MMS2008 - Wednesday 3

Session: Ask the Experts; and interesting solution by Rod K to a question; the question was sending out a wakeup, then a task (like anti-virus scan), then shutdown; but only shutdown those computers that had to be woken up.  Other than the obvious (1E / sccmexpert or other 3rd party tools to manage that), he mentioned scripting finding win32_computersystem.wakeuptype, and if value is 5, shutdown the computer after the virus scan is complete. (because 5 is wakeonlan, and 6 is the power button)

MMS2008 - Wednesday 2

Session: Console Extensions (right-click) for ConfigMgr

Greg pointed out Rick Houchin's existing toolset, as well as reminding everyone about KB932303.  Also http://www.myitforum.com/articles/42/view.asp?id=10801, for converting any existing right-click tools you may have for SMS2003 to ConfigMgr

Remember /sms:nodeinfo=1 for the old console?  Greg mentioned there are several switches for the new console that can assist you in scripting your own console extensions.  A few were sms:debugview, sms:verboseerrors, sms:namespaceview=1; there were 1 or 2 more, check out http://technet.microsoft.com/en-us/library/bb693533.aspx.

Some great powershell demos; Greg mentioned he'll blog the scripts he used for the demos, so I'll just wait for those.

MMS2008 - Wednesday 1

Keynote:  A few announcements (probably mostly known): ConfigMgr 07 SP1 in May, R2 (release candidate) in July.  An update to Desktop Optimization Pack in Q3 2008; as a subscription service anticipate updates every 6 months.

A demo of the R2 Out of Band Management Console to (for example) remotely look at bios and change settings.

A demo of in-development product, Asset Knowledge Service.  They announced that anyone can ask to join, so if anyone might be interested in participating--your company would need to be willing to forward data upstream to Microsoft (they didn't explain it like this, but I equated the process involved to be similar to that question you see when a driver doesn't load correctly, or a app crashes of "send this information to Microsoft yes/no").  If you might want to join, email knowledge@microsoft.com .