How does the MicrosoftVolumeEncryption namespace get created?
I have configured my SCCM 2007 R2 SP2 site to inventory for Bitlocker encryption information. Everything has been working fine. I added a new section for inventorying the MicrosoftVolumeEncryption namespace, and I have 1200 laptops that have sent in their information. However, I also noticed that there were about 50 laptops that did not provide any information. When I checked out the cause I found the problem laptops did not have the root\cimv2\security\MicrosoftVolumeEncryption namespace. If I open the Manage Bitlocker gui it shows that Bitlocker is turned on. If I run the Manage-BDE utility it shows the namespace does not exist, yet every morning the user gets prompted for a key. Can someone explain how the MicrosoftVolumeEncryption namespace gets created and why 50 laptops would not have it? As always, your help is appreciated.
June 13th, 2011 4:30pm

I have found how to get the problem computers to re-create the MicrosoftVolumeEncryption namespace. There is a MOF file in the System32\WBEM folder named win32_encryptablevolume.mof that contains all the settings for the namespace. I ran the mofcomp.exe utility to compile the mof file and the namespace got created. I still do not know how or why the namespace was missing, but at least I can get it back.
Free Windows Admin Tool Kit Click here and download it now
June 14th, 2011 5:58pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics