Try this:
#pragma namespace ("\\\\.\\root\\cimv2\\SMS")
#pragma deleteclass("Win32Reg_MBAMPolicy", NOFAIL)
[ SMS_Report(TRUE),
SMS_Group_Name("BitLocker Policy"),
SMS_Class_ID("MICROSOFT|MBAM_POLICY|1.0")]
Class Win32Reg_MBAMPolicy : SMS_Class_Template
{
[SMS_Report(TRUE),key] string KeyName;
[SMS_Report(TRUE)] UInt32 OsDriveEncryption;
[SMS_Report(TRUE)] UInt32 FixedDataDriveEncryption;
[SMS_Report(TRUE)] UInt32 EncryptionMethod;
[SMS_Report(TRUE)] UInt32 OsDriveProtector;
[SMS_Report(TRUE)] UInt32 FixedDataDriveAutoUnlock;
[SMS_Report(TRUE)] UInt32 FixedDataDrivePassphrase;
[SMS_Report(TRUE)] Uint32 MBAMPolicyEnforced;
[SMS_Report(TRUE)] string LastConsoleUser;
[SMS_Report(TRUE)] datetime UserExemptionDate;
[SMS_Report(TRUE)] UInt32 MBAMMachineError;
[SMS_Report(TRUE)] string EncodedComputerName;
};
What's different you ask? I took out all of the comment lines starting with //
and there was ONE other thing that looked "different", which I didn't think it
would be a big deal but maybe it is.
changed
Class Win32Reg_MBAMPolicy: SMS_Class_Template
to
Class Win32Reg_MBAMPolicy : SMS_Class_Template
simply put a space before AND after the :, instead of just after. If that
still doesn't work, then we can try changing the groupname and classid to both
say EXACTLY this:
"BitLockerPolicy" (and nothing else). I've seen it where just changing the
groupname and classid will let it go through.
On Monday, January 12, 2015 3:25 PM, Sherry Kissinger
<slkissin...@sbcglobal.net> wrote:
what does it say for an error?
On Monday, January 12, 2015 3:07 PM, Jimmy Martin <jimmy.mar...@bmhcc.org>
wrote:
It chokes on the second section… everything else imported
#pragma namespace ("\\\\.\\root\\cimv2\\SMS")
#pragma deleteclass("Win32Reg_MBAMPolicy", NOFAIL)
[ SMS_Report(TRUE),
SMS_Group_Name("BitLocker Policy"),
SMS_Class_ID("MICROSOFT|MBAM_POLICY|1.0")]
Class Win32Reg_MBAMPolicy: SMS_Class_Template
{
[SMS_Report(TRUE),key]
string KeyName;
//General encryption requirements
[SMS_Report(TRUE)]
UInt32 OsDriveEncryption;
[ SMS_Report (TRUE) ]
UInt32 FixedDataDriveEncryption;
[ SMS_Report (TRUE) ]
UInt32 EncryptionMethod;
//Required protectors properties
[ SMS_Report (TRUE) ]
UInt32 OsDriveProtector;
[ SMS_Report (TRUE) ]
UInt32 FixedDataDriveAutoUnlock;
[ SMS_Report (TRUE) ]
UInt32 FixedDataDrivePassphrase;
//MBAM agent fields
//Policy not enforced (0), enforced (1), pending user exemption request (2)
or exempted user (3)
[SMS_Report(TRUE)]
Uint32 MBAMPolicyEnforced;
[SMS_Report(TRUE)]
string LastConsoleUser;
//Date of the exemption request of the last logged on user,
//or the first date the exemption was granted to him on this machine.
[SMS_Report(TRUE)]
datetime UserExemptionDate;
//Errors encountered by MBAM agent.
[ SMS_Report (TRUE) ]
UInt32 MBAMMachineError;
[ SMS_Report (TRUE) ]
string EncodedComputerName;
};
From:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Sherry Kissinger
Sent: Monday, January 12, 2015 1:29 PM
To: mssms@lists.myitforum.com
Subject: Re: [mssms] adding the MBAM inventory classes to default client
inventory classes
Nope, I don't see anything. For fun, there are 4 different sections in that
to-be-imported .mof
What if you were to split them up into 4 different .mof files. Maybe it's only
1 of the 4 that it's choking on?
Divide and conquer. :)
On Monday, January 12, 2015 1:18 PM, Jimmy Martin <jimmy.mar...@bmhcc.org>
wrote:
Well crap
That doesn’t import either.
I tried on the server as well as my 2 workstations with the same result. I
went ahead and exported my hardware inventory classes to see if you could spot
something there that was ill defined and blocking this. It has something to do
with the sms_class_template definition as the file will not mofcomp
successfully unless I add the definition to the top of the mof. Wont import
either way
From:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Sherry Kissinger
Sent: Monday, January 12, 2015 1:05 PM
To: mssms@lists.myitforum.com
Subject: Re: [mssms] adding the MBAM inventory classes to default client
inventory classes
well, I dunno what you're doing. But the attached works just fine for me in my
lab; to import into default agent settings.
that's just for importing; the configuration.mof changes still have to be done.
On Monday, January 12, 2015 9:49 AM, Jimmy Martin <jimmy.mar...@bmhcc.org>
wrote:
http://technet.microsoft.com/en-us/library/dn237295.aspx
Jimmy Martin
(901) 227-8209
From:listsad...@lists.myitforum.com [listsad...@lists.myitforum.com] On Behalf
Of Sherry Kissinger [slkissin...@sbcglobal.net]
Sent: Monday, January 12, 2015 9:44 AM
To: mssms@lists.myitforum.com
Subject: Re: [mssms] adding the MBAM inventory classes to default client
inventory classes
"but the mof data on the Microsoft site absolutely will not import. I am
importing into the default settings…"
what's the .mof on the Microsoft site?
On Monday, January 12, 2015 9:36 AM, Jimmy Martin <jimmy.mar...@bmhcc.org>
wrote:
Hi Guys,
From the documentation, this seems so simple… but the mof data on the
Microsoft site absolutely will not import. I am importing into the default
settings…
If I check the mof syntax, it does not know sms_class_template
If I add the sms_class_template information to the top of the mof, it will
check out syntax wise but it still doesn’t import. I’m sure its something
simple I am missing here
Jimmy Martin| Engineer | Information Technology | BMHCC - CORPORATE
Phone: (901) 227-8209 | jimmy.mar...@bmhcc.org
Opinions expressed above are not necessarily those of Baptist.
This message and any files transmitted with it may contain legally privileged,
confidential, or proprietary information. If you are not the intended recipient
of this message, you are not permitted to use, copy, or forward it, in whole or
in part without the express consent of the sender. Please notify the sender of
the error by reply email, disregard the foregoing messages, and delete it
immediately.
PPlease consider the environment before printing this email...
This message and any files transmitted with it may contain legally privileged,
confidential, or proprietary information. If you are not the intended recipient
of this message, you are not permitted to use, copy, or forward it, in whole or
in part without the express consent of the sender. Please notify the sender of
the error by reply email, disregard the foregoing messages, and delete it
immediately.
PPlease consider the environment before printing this email...
This message and any files transmitted with it may contain legally privileged,
confidential, or proprietary information. If you are not the intended recipient
of this message, you are not permitted to use, copy, or forward it, in whole or
in part without the express consent of the sender. Please notify the sender of
the error by reply email, disregard the foregoing messages, and delete it
immediately.
PPlease consider the environment before printing this email...
This message and any files transmitted with it may contain legally privileged,
confidential, or proprietary information. If you are not the intended recipient
of this message, you are not permitted to use, copy, or forward it, in whole or
in part without the express consent of the sender. Please notify the sender of
the error by reply email, disregard the foregoing messages, and delete it
immediately.
PPlease consider the environment before printing this email...
