BitLocker Report with SCCM 2007 R3

Hi Everyone,
I am in the process  of trying to get BitLocker status from client using Hardware Inventory in SCCM 2007. I customized the sms_def.mof with the following info at the end of the file:
//BitLocker Status - SMS_Def.mof
[ SMS_Report (TRUE),
SMS_Group_Name ("Bitlocker"),
SMS_Class_ID ("MICROSOFT|Bitlocker|1.0")]
class Bitlocker : SMS_Class_Template
{
[SMS_Report(TRUE), key]
string DeviceID;
[SMS_Report(TRUE)]
string DriveLetter;
[SMS_Report(TRUE)]
uint32 ProtectionStatus;
};
 
And for the Configuration.mof file:
//CONFIGURATION.MOF:
#pragma namespace("\\\\.\\root\\cimv2")
[Union,ViewSources{"select * from Win32_EncryptableVolume"},ViewSpaces{"\\\\.\\root\\cimv2\\security\\MicrosoftVolumeEncryption"},
Dynamic,Provider("MS_VIEW_INSTANCE_PROVIDER")]
class Bitlocker
{
[PropertySources{"DeviceID"},key]
string DeviceID;
[PropertySources{"DriveLetter"}]
string DriveLetter;
[PropertySources{"ProtectionStatus"}]
uint32 ProtectionStatus;
};

Here is the link I followed to perform these customizations:
"http://blogs.technet.com/b/configurationmgr/archive/2010/11/22/getting-bitlocker-status-from-clients-using-hardware-inventory-in-configuration-manager-2007.aspx"

My SCCM hardware inventory scan happens every 3 days. 
 
I have waited for a week and then created a query from the link above instructions. Every time I run the query in SCCM, I get the error beside the query saying that "*The ConfigMgr Provider reported an error*". Below is the query statement.
"select sys.Name0, BL.DriveLetter0, BL.ProtectionStatus0 from v_GS_BitLocker BL Join v_r_system sys on sys.ResourceID = BL.ResourceID"


In the InventoryAgent.log file on the SCCM client, I am also seeing the error "Collection:Class "Bitlocker" does not exist out."I have researched into this error but I am not getting any help from Google. 
Anyone knows how to resolve this issue?
Thanks in advance.
Tee
 

There are three different issues I believe. The first is that based on your error about provider, you are attempting to use sql... but asking wql. Your report is sql. If you are getting a provider error, you must be connecting/using a console query, which is wql. Not the same things. The second is that I doubt your view will be v_gs_bitlocker. The sql view will likely be v_gs_bitlocker0

The third issue is your real blocker though, does not exist out means that the wmi query you are attempting in configuration.mof, and then gathering via sms_def.mof... that wmi place in the client simply isn't there. Are you sure the client has bitlocker? Ie, it is win7 sp1?

Sherry,
 All the clients in my environment are Vista (SP2) machines and not Win7 with SP1. Does it mean that BitLocker have to be configured and turned on first before I configure the MOF files and then do the query? My understanding is that whether BitLocker is configured or not, the customization of the MOF files and the query I put in place should be able to tell me the the current status of BitLocker on all the Vista clients whether they're BitLocker enabled or not. Unless I am missing something here.
So how do I approach this issue from scratch if what I am doing now is not the right process based on the article I followed for my task?
Thanks in advance,
 
Tee
 

Well, start with this.  forget ConfigMgr for now.
When you run wbemtest or whatever wmi query method locally you like, do you get any instances at all on that vista client when you run  "select * from win32_encryptablevolume"  ?
That's what configuration.mof is using to query--if the client locally doesn't have win32_encryptablevolume, there's nothing that configuration.mof can magically do to make that namespace and populate it with information.
We skipped Vista completely at my company, so I literally have no idea where, or if, Vista even records Bitlocker info in WMI.

When I run wbemtest with the "select * from win32_encryptablevolume" in the Query box, I receive the error
"Number: 0x80041010
 Facility: WMI
 Description: Invalid class"
Any more ideas from anyone?
Thanks,
Tee
 
 

Did you ensure that wbemtest was pointing at root\cimv2 ?
If so then as per Sherry's comment if it's not there SCCM can't report on it. 

Look at this:  http://social.technet.microsoft.com/Forums/en-US/configmgrinventory/thread/5c9f9681-e665-4b3f-a83a-b554be65a921
 
which will point you to this:  http://www.buit.org/2010/08/18/howto-bitlocker-status-reporting-in-sccm-2007/
Looks like that person was able to get vista os to report, but they did have to run a script first on their vista boxes (likely as a recurring advert, to keep the data current) to essentially populate a wmi namespace so that they could pull the data out.

Sherry,
 I did look at both links before posting my issue. I'll test it again tomorrow at work to find out what I am doing wrong.
Thanks again,
 
Tee

So can we assume that you have found a system with Bitlocket? You didn't know any within your TechNet for post. http://social.technet.microsoft.com/Forums/en-US/configmgrreporting/thread/b6123941-e122-4e87-831d-2031deff1c34

My issue has been resolved by again following the steps in the article I posted earlier -> "http://blogs.technet.com/b/configurationmgr/archive/2010/11/22/getting-bitlocker-status-from-clients-using-hardware-inventory-in-configuration-manager-2007.aspx"
Thank you all for your help.
 
Tee