For the link that I provided, the answer is yes. Essentially, you need to have a SHA (client side) and SHV (server side) that can monitor (client) and validate (server) bitlocker. The bitlocker client service talks to the SHA, which in turn reports to the enforcement client that communicates with NPS for validation.
There can be other SHAs written to perform this function, but I'm not aware of these yet. Others may know, and more might be written in the future.
I know that Forefront does much more than just monitor Bitlocker, so you're getting a lot more than you asked for here. I wish the WSHA monitored this, but it doesn't have this capability yet.
For the link that I provided, the answer is yes. Essentially, you need to have a SHA (client side) and SHV (server side) that can monitor (client) and validate (server) bitlocker. The bitlocker client service talks to the SHA, which in turn reports to the enforcement client that communicates with NPS for validation.
There can be other SHAs written to perform this function, but I'm not aware of these yet. Others may know, and more might be written in the future.
I know that Forefront does much more than just monitor Bitlocker, so you're getting a lot more than you asked for here. I wish the WSHA monitored this, but it doesn't have this capability yet.
