After a few minutes, my machine picked up the new policy and started encrypted silently. The query returned '0', so I figured this is why my BitLocker policy wasn't working.Īs a bit of a hail Mary, I decided to redeploy my policy with the plain text option for recovery keys selected. Unfortunately I couldn't follow through with his fixes because I don't have permissions on the SQL Server, but I was able to run a query to check for the BitLocker certificate talked about here. However, in the Event Viewer MBAM admin log I started seeing VolumeEnactmentFailed, which is the same issue /u/Gant_217 experienced in this thread (I probably wasn't seeing these errors before because the encryption wasn't trying to start due to using RDP). So I connect through SCCM remote control hoping this was all I needed to do to kick off the encryption, but no dice. I decided to read Niall's guide to see if it mentioned anything not in the videos, and I saw under 'Step 5' that the pop-up won't appear nor encryption start if connected through RDP. One difference between my machine and Niall's setup, however, is the second disk I've got.maybe I need additional registries for fixed data drives in addition to the OS drive?ĮDIT: To hopefully clarify a little more, I have the same problem as this post (except my cypher strength is set to XTS-AES-256) - Unfortunately that thread is a dead end. there's no PKI errors, which is one of the most vital components). Maybe I've overlooked something? Everything appears to be set up as required and I see no errors in the MBAM Event Viewer logs or in the individual BitLocker log files on the machine I'm trying to encrypt (e.g.
I can run manage-bde -on c: and reboot to start the encryption, but I wasn't under the impression that this was necessary when using the registry settings from Niall's part 4 video (he certainly doesn't mention it). So I've followed parts 1 and 4 of Niall Brady's 1910 MBAM videos and set up the SCCM side of things exactly the same, but the encryption isn't starting automatically like I hoped it would and I get no popup to start or postpone. As a general rule, if someone has flair, they almost definitely know what they're talking about. Microsoft employees typically have MSFT Official flair, and MVPs usually have MSFT Enterprise Mobility MVP with a link to their personal site/blog.Please send mod mail if you qualify and would like flair set for your account. Flair is reserved for Microsoft employees and MVPs.System Center Configuration Manager and Endpoint Protection.Listing of Local ConfigMgr-related User Groups (largely outdated) URL shorteners cause this almost every time, but so do strings of apparent gibberish like WSUS and PXE sometimes. It might have been caught by the spam filter. Post your SCCM tips and tricks, requests for help, or links others might find useful! Post not showing up?
0 kommentar(er)
