May 27, 2016
Posted by on
Here is an elegant technique to automate Bitlocker protectors disable while Microsoft updates are installing.
This was shared by one of Microsoft Support Engineers.
Sometimes Microsoft updates can introduces changes locking the machine. To avoid that you can disable protectors for update time and re-enable them after.
To do that you can use Scheduler and monitor for Windows Updates event.
We need to create two scheduled tasks (either locally or using GPO):
First one is Suspend Bitlocker
It will start on Event
When MSInstaller starts Windows Updates it generates Event ID 1040
At that event we want to run a command to suspend protectors on C:
The second Scheduled Task is similar except Event ID we monitor and action.
When updates are installed an Event ID 1042 is issued
We are going to resume protectors at that event:
Note: The machine will have protectors in suspended state during Microsoft updates (they will be resumed after installation finish or after reboot), so it is a potential breach in your security. Use it on your own risk!
March 1, 2013
Posted by on
Microsoft Bitlocker Management and Administration server is installed in a single server configuration. Test machine is encrypted, but never reported its state back to the server.
It turned out you need to add a ‘MBAM’ registry key to MBAM server under HKEY_LOCAL_MACHINE\Software\Microsoft
as soon as the key as created, add a DWORD settings with name DisableMachineVerification and set it to 1
Restart mbamagent on a client machine and now report should pass.
Interesting enough – this ‘feature’ exists since v.1 of MBAM and is still around!
MS has a KB about that http://support.microsoft.com/kb/2612822?wa=wsignin1.0