Jump to content


Jonnwhite

1910 - Bitlocker manage Report Error

Recommended Posts

Hey, 

I've been following your guides for a while now and really appreciate your knowledge!

I have a question, I've got SQL reportigng services working okay I can run reports except for any of the Bitlocker ones.

I ge the below error message? MBAM seems to be working well, pops up on machines and also store recovery key in database however trying to work on a report that would all me to input a Pc number and it would return the recovery key number. However for that I need to get the reports working to start with. 

Any ideas? I assume I've forgotten to do something!

image.thumb.png.87a03d22abebbe50117a74d4ec84a7bc.png

Share this post


Link to post
Share on other sites

ok that's odd, so are you getting errors on all the 5 bitlocker reports ?

do all other non-bitlocker reports render correctly for the same user ?

 

lastly, have you looked at this post to see does it give you any pointers

https://www.niallbrady.com/2019/11/12/a-quick-look-at-reporting-in-mbam-integrated-with-microsoft-endpoint-manager-configuration-manager/

Share this post


Link to post
Share on other sites

I only have 4 bitlocker report avalible?

All other work fine. 

Just followed steps on the the link and it still doesnt work. 

One thing i did notice was i hadn't set the hardware inventory classes for bitlocker. I have no done this, i assume i need to wait for inventory to catch up for theview to be created perhaps?

Not sure if i need to make the MOF change or not.

 

Many thanks

JOn

Share this post


Link to post
Share on other sites

5 hours ago, anyweb said:

ok that's odd, so are you getting errors on all the 5 bitlocker reports ?

do all other non-bitlocker reports render correctly for the same user ?

 

lastly, have you looked at this post to see does it give you any pointers

https://www.niallbrady.com/2019/11/12/a-quick-look-at-reporting-in-mbam-integrated-with-microsoft-endpoint-manager-configuration-manager/

Scrap that, forced inventory and it now seems to be working!

 

image.thumb.png.51912a368b74ae3cd63780f64864083f.png

  • Like 1

Share this post


Link to post
Share on other sites

good to hear it, the 5th report is the one in the language specific folder, eg: en-us. for auditing of recovery keys.

to confirm you only did a HINV cycle on the client and the error above vanished ? can you also confirm that you had the up to date 1910 client installed on the client or was that also part of your problem ?

cheers

niall

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.