Re: Enable inventory of bitlocker drive status

Christoffer Bennerstedt wrote:
Hi Kim,

Sorry, i forgot all about adding my question :)
I wondered if i could run mofcomp on Vista, which you already answered. Well, when i try to mofcomp on my vista client, i get the following:

Parsing MOF file: sms_def.mof
MOF file has been successfully parsed
Storing data in the repository...
An error occurred while creating object 81 defined on lines 4085 - 4097:
0X80041002 Class, instance, or property 'SMS_Class_Template' was not found.
Compiler returned error 0x80041002

The lines 4085-4097 is the added code that i sent previously.

If i remove SMS_Class_Template, i get the following result:

Parsing MOF file: sms_def.mof
MOF file has been successfully parsed
Storing data in the repository...
WARNING: File sms_def.mof does not contain #PRAGMA AUTORECOVER.
If the WMI repository is rebuilt in the future, the contents of this MOF file wi
ll not be included in the new WMI repository.
To include this MOF file when the WMI Repository is automatically reconstructed,
place the #PRAGMA AUTORECOVER statement on the first line of the MOF file.
Done!

What does this mean? And, if i successfully compile the MOF-file, should it then be copied to the SMS server??

Thanks again!

"Kim Oppalfens [MVP]" <""Kim dot Oppalfen" wrote:

Hi Christoper,

Looks good to me at first glance.
I don't really know what you expect from me at this point, I failed to see a question in your post. :-)

Indeed the namespace is non-existent on windows 2003, so you would only mofcomp this on vista clients. There is absolutely no need to mofcomp this on your sms server.



--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx




Christoffer Bennerstedt wrote:
Hi Kim,

Thanks, i have tried adding the following to my sms_def.mof, but when compiling with mofcomp on my SMS-server i get Error Number 0x8004100e, description: Invalid Namespace
Which i understand, because on the SMS server, that namespace is non-existant since it's an Win2k3 server..

Added:

#pragma namespace ("\\\\.\\root\\cimv2\\security\\MicrosoftVolumeEncryption")

[ SMS_Report (TRUE),
SMS_Group_Name ("Bitlocker Info"),
SMS_Class_ID ("BITLOCKER") ]

class Win32_EncryptableVolume : SMS_Class_Template
{
[SMS_Report (TRUE) ] string Driveletter;
[SMS_Report (TRUE) ] uint32 GetProtectionStatus;
[SMS_Report (TRUE) ] uint32 GetEncryptionMethod;
[SMS_Report (TRUE), key] uint32 GetConversionStatus;
[SMS_Report (TRUE), key] uint32 GetKeyProtectors;
};

"Kim Oppalfens [MVP]" <""Kim dot Oppalfen" wrote:

Christoffer Bennerstedt wrote:
Hi,

How do i enable taking inventory from Vista-clients to see if their systemdrive is protected with bitlocker?
I guess i have to add the namespace to the sms_def.mof file on our SMS server and compile it?
Is this the namespace i should add: \\.\root\CIMv2\Security\MicrosoftVolumeEncryption

btw, we're running SMS SP3

Thanks
To take a look at bitlocker you need to use this namespace:
\\.\root\cimv2\security\MicrosoftVolumeEncryption
and the class is Win32_EncryptableVolume.



--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx

The warning means that if you rebuild your wmi, by deleting the wmi repository that you would lose the additions that were added through this file.

You can circumvent this by running mofcomp -AUTORECOVER sms_def.mof

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx
.

Relevant Pages

  • Re: Enable inventory of bitlocker drive status
    ... I wondered if i could run mofcomp on Vista, ... MOF file has been successfully parsed ... then be copied to the SMS server?? ...
    (microsoft.public.sms.inventory)
  • Error Number: 0x8004100e, Facility: WMI, Description: Invalid namespace
    ... - Unable to compile file SmsClient.mof ... Stopped the WinMgmt service, ... Parsing MOF file: SmsClient.mof ... mofcomp cimwin32.mof ...
    (microsoft.public.sms.setup)
  • Re: Remote Control Security Munger -SMS 2003
    ... For SMS 2003 adv clients this can be achieved using 'local policy'. ... just a .mof file which changes the WMI settings. ...
    (microsoft.public.sms.admin)
  • Re: Copy file to client and run command - SMS_DEF.MOF
    ... In that case a batch file that runs mofcomp should work for you. ... MOF file and the batch file in the same source directory and then add the ... SMS 2.0 Resource Page: ... SMS 2003 Resource Page: ...
    (microsoft.public.sms.swdist)
  • RE: Edited SMS_DEF.MOF File
    ... That way if wmi is ever corrupted and needs to be rebuilt the mof file ... MVP SMS ... > If its new Classses that were not in the SMS_Def.Mof you will need to Mofcomp ... > and also create an SMS Package distribution with the SMS_Def.mof then deploy ...
    (microsoft.public.sms.inventory)
Loading