Sherry Kissinger at myITforum.com

Mini Monster Mof Builder

Edit: Updated to v1.11 

For SMS 2003 SP2 and earlier, there were popular downloads available for what were known as "the Monster Mof".  They were great, but in my opinion could be bloated.  For example, it would contain edits for 3 different anti-virus vendors.  Most companies usually only had 1, or if they were really diverse, possibly 2.  As an admin, you either put in the entire monster and lived with the bloat, or edited the Monster anyway, and either removed edits or set them to FALSE.

Since SP2, edits have been accumulating.  Most of which have been blogged on MyITForum, but they are often difficult to find.  There's a zip file with all of the text snippets here, but even that could be daunting to the admin who rarely edits the mof.

So... here's another, different way to pick and choose which MOF extensions you might want in your environment.  Download the attached file, unzip it, and rename it from .txt to .hta, and double-click it.  You'll be presented with the below.  Please look at Misc Notes, and the specific instructions for SMS2003 vs. ConfigMgr.  You can use the ? to get more info on a particular snippet, which may lead you to additional blog entries.  Once you've decided which 1 (or 5) extensions you might want in your environment, check those items on, and at the bottom, click "Compile & Display".  You will then have 1 (or 2) text files with your own "mini monster" to add to your mof files on the server.  As useful mof edits continue to accumulate, the download will be updated; at least until a better method for sharing mof snippets appears!

Advertisements do not enumerate in a remote ConfigMgr Console

If you have a remote Administrative ConfigMgr Console (i.e., you install the console on a computer or server which is not the primary Site Server), you may notice that Advertisements do not enumerate.  The advertisement node is empty.

The hotfix KB955262 addresses this issue, and should be installed on any computer which hosts the Admin Console.

One of the files modified is AdminConsole.xml; which is often a file modified for any right-click console extensions.  If you've modified this file for right-click tools, you may need to re-do the modifications.  Note you will not want to just put back the old .xml; there are updates in this xml you need for this KB to fix the issues.

ConfigMgr MOF Hardware Extensions - a collection

Attached is a collection of MOF snippets for Configuration Manager.  A lot of them either need external scripts or have other considerations.  Please carefully read the "readme" included within each subfolder.  These are the same MOF snippets available at sccmexpert.com.

 As of 10/20/08, I'm calling it v1.4  As I discover new or unusual edits, I'll update the download.

Dell OMCI Configuration - Hardware Inventory Extension

By request, the Boot password settings out of the WMI Namespace created by Dell's Open Manage Client Instrumentation; the Dell_Configuration, specifically the Boot Password attributes.  Below is the mof edit; to be added to the bottom of sms_def.mof on your primary site servers, inboxes\clifiles.src\hinv.  Note most of the attributes are FALSE.  If you determine you would like those additional attributes, at any time you can change them from FALSE to TRUE.  Also below is a sample report for the WakeonLan returned results.  The results come back as an integer; so interpretation is needed at the report.  If you do want to turn on additional attibutes, in the attached is a text file.  If you follow the pattern of the BootPasswordVerification info, you'll see the other attributes' patterns, and be able to create your own Select Case... reports.

// Dell Configuration Settings
// These settings are available when the following optional application for
// managed Dell systems is installed.
// Dell Open Manage Client Instrumentation (OMCI)
// This edit was tested using v7.6 of Dell OMCI
// Note: the majority of options, changed from FALSE to TRUE, report an
// integer (0, 1, 2, 3, etc.)  Those integers would need to be correctly
// interpreted at the report level.

[ SMS_Report     (TRUE),
  SMS_Group_Name ("Dell Configuration Settings"),
  SMS_Class_ID   ("CUSTOM|Dell_Configuration|1.0"),
  SMS_Namespace (FALSE),
  Namespace      ("\\\\\\\\.\\\\root\\\\dellomci") ]

class Dell_Configuration : SMS_Class_Template
{
 [SMS_Report (FALSE)    ]     sint32 ACPowerRecoveryMode;
 [SMS_Report (TRUE)     ]     string BootPassword;
 [SMS_Report (TRUE)     ]     sint32 BootPasswordVerification;
 [SMS_Report (FALSE)    ]     string Caption;
 [SMS_Report (FALSE)    ]     string Description;
 [SMS_Report (FALSE)    ]     sint32 EnableDisableBIS;
 [SMS_Report (FALSE)    ]     uint64 ExtensionTokens;
 [SMS_Report (FALSE)    ]     sint32 ForcePXEonNextBoot;
 [SMS_Report (FALSE)    ]     uint32 GlobalDisplaySeverityLevel;
 [SMS_Report (FALSE)    ]     uint32 GlobalNTEventLogSeverityLevel;
 [SMS_Report (FALSE)    ]     sint32 GlobalStatus;
 [SMS_Report (FALSE)    ]     sint32 HDDMinimumCapacity;
 [SMS_Report (FALSE)    ]     sint32 HDDPercentageThreshold;
 [SMS_Report (FALSE)    ]     uint32 Infrared;
 [SMS_Report (FALSE)    ]     sint32 KeyboardErrorReporting;
 [SMS_Report (FALSE)    ]     sint32 ManagementApplication;
 [SMS_Report (FALSE)    ]     sint64 MaximumPasswordLength;
 [SMS_Report (FALSE),key]     string Name;
 [SMS_Report (TRUE)    ]     string Password;
 [SMS_Report (FALSE)    ]     boolean PasswordEncrypted;
 [SMS_Report (FALSE)    ]     sint32 PasswordStatusLockUnlock;
 [SMS_Report (FALSE)    ]     sint32 PasswordVerification;
 [SMS_Report (FALSE)    ]     string PropertyOwnershipTag;
 [SMS_Report (FALSE)    ]     sint32 RestartSystem;
 [SMS_Report (FALSE)    ]     sint32 SMBIOSSupported;
 [SMS_Report (FALSE)    ]     uint64 SystemIDByte;
 [SMS_Report (FALSE)    ]     sint32 VGADACSnoop;
};

And the sample report; but without columns for Password nor BootPassword, because in the quick lab test I did, I didn't actually create either a bios password nor a boot password. 

select case
when DellCS.BootPasswordVerification0 = 0 then 'Password not matched'
when DellCS.BootPasswordVerification0 = 1 then 'Password matched'
when DellCS.BootPasswordVerification0 = 2 then 'Not yet verified'
when DellCS.BootPasswordVerification0 = 3 then 'Password disabled by jumper'
when DellCS.BootPasswordVerification0 = 4 then 'Password not enabled'
end as 'BootPassword Verification'
from v_r_system as sys
inner join v_gs_dell_configuration_se0 as DellCS on sys.resourceid=DellCS.resourceid where sys.netbios_name0 = @compname

 With a CompName prompt SQL statement of

begin
 if (@__filterwildcard = '')
  SELECT DISTINCT SYS.Netbios_Name0 from v_R_System SYS ORDER By SYS.Netbios_Name0
 else
  SELECT DISTINCT SYS.Netbios_Name0 from v_R_System SYS
  WHERE SYS.Netbios_Name0 like @__filterwildcard
  ORDER By SYS.Netbios_Name0
end