@Lean
Thank you for posting in Microsoft Q&A forum.
Did you create the three groups in Active Directory: BitLocker help desk admins, BitLocker help desk users, BitLocker report users and setup bitlocker portals with the three parameters:
-HelpdeskUsersGroupName <DomainUserGroup>
-HelpdeskAdminsGroupName <DomainUserGroup>
-MbamReportUsersGroupName <DomainUserGroup>
For reference:
https://learn.microsoft.com/en-us/mem/configmgr/protect/deploy-use/bitlocker/helpdesk-portal#groups
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
@Lean
Check if the report server web service URL can access successfully.
yes the Web Service URL can be access successfully.
@Lean
And do you specify the -ReportWebServiceUrl <ReportWebServiceUrl> when you set up the BitLocker portals?
I rechecked the script I run in the PowerShell.
And noticed that I put the -ReportWebServiceUrl <CHSV001012019> , which is the SCCM server
Should I use -ReportWebServiceUrl http://CHSV001022019:80/RepotServer instead?
Is it okay to rerun the script? Will it affect the BitLocker portals?
@Lean
Yes, it's ok to rerun the script. Please rerun it with the correct URL.
@AllenLiu-MSFT
I've rerun the script.
There's no more warning at the end of the PowerShell
But when I click the Reports tab > Recovery Audit Report , nothing happens and I don't see any error logged in the event viewer,
If I click the Recovery audit Report on Edge, nothing happens.
and if I run it in IE, here is the error
@Lean
When I click Recovery audit Report, there is a prompt pops up like below:
And then click "show all content" and click "retry", the complete interface is displayed
no prompt pop up on my environment.
@Lean
IE works for me, there should be something wrong with your IE.
Here is the details about Error106:HelpdeskError
https://learn.microsoft.com/en-us/mem/configmgr/protect/tech-ref/bitlocker/server-event-logs#106-helpdeskerror
Sign in to comment
Activity