Bitlocker and MBAM on Windows 10 1903

-




Recently our SQL servers broke.

Big time.

Totally unrecoverable.

This box "only" ran small infrastructure databases.

MBAM being the main one.

We only noticed when we needed to unlock a bitlocker locked machine and MBAM wasn't responding.  

Our backups we toast too as the SQL server box had been unusable for longer than our retention period and we now had backups of a broken machine.

Not great.  We now monitor this server.  Like a hawk.  Horse. Bolt. Stable.  Oh well.  We did have the data on separate disks so we were able to get the bitlocker database itself back and mount this on a new SQL box so not all lost.

We took this opportunity to upgrade MBAM and the MBAM client we delivered to the end points.

Then Windows 1903 was released and we began piloting this to certain users.  Due to the recent "interest" in MBAM we noticed that bitlocker was not enabling on these machine despite the GPO being in place.

This GPO worked flawlessly for previous versions so we wondered what was going on.

AFter a long time we realised that the AD version was different to the SYSVOL version...d'Oh!

DFSR between our Domain Controllers was not working correctly!

We fixed that and the GPO began deploying correctly and machines enrolled.

And yes - I am looking @ SCCM as MBAM is end of life :(

Comments

  1. Anonymous7 April 2022 at 10:29

    Bitlocker And Mbam On Windows 10 1903 >>>>> Download Now

    >>>>> Download Full

    Bitlocker And Mbam On Windows 10 1903 >>>>> Download LINK

    >>>>> Download Now

    Bitlocker And Mbam On Windows 10 1903 >>>>> Download Full

    >>>>> Download LINK ld

    ReplyDelete

Post a Comment

Popular posts from this blog

PXE booting, MDT and 802.1x

-
Image
Oh dear. We implemented site wide 802.1x when we moved. This has caused numerous issues which we are still tracking down and killing with fire. Again "only-when-we-needed-it" struck as we had a new starter and need to build a machine. Ah.   No PXE.  However thankfully we were able to make a bootable USB using 802.1x and get our build working again from MDT in our 802.1 environment. Here's how we did it.   Caveats:  I'm assuming you know MDT and how PXE works. We use Computer certificates as the 8021x auth method. 802.1x is working in our environment GPO is used to start the wired 802.1x service on built machines. GPO is used to configure the network profile to use 802.1x What you need Get a USB stick to take your WinPE 4GB may be enough Make sure you are running an up to date working MDT installation! Create a machine certificate which has a long expiry date, you don't want to be making USB WinPE images every month!! Export the machine
Read more

Intune installation requires a wire...or does it?

-
If you are using Intune (great!) it assumes you have a wired connection (not great) - this is more of an issue as some machine now no longer have built in ethernet ports. It is possible to connect to your wireless - albeit in a slightly awkward way.....here's how During the OOBE hit SHIFT+F10 to get a command window and type either; start ms-settings: To get the settings window or start ms-availablenetworks: To see the network fly outs. Thanks to  Using a wireless network connection with Windows Autopilot white glove – Out of Office Hours (oofhours.com)
Read more

Security Policy 1001

-
We had an annoying warning showing every 5 minutes on our Read Only Domain Controllers.  This didn't affect service but meant we were losing our logs of important events (should the have occurred) "Security policy cannot be propagated. Security Configuration Server (in services.exe) is not ready. This is probably in system reboot. Policy will be tried again in the next propagation." Source: SceCli Event: ID 101 We tracked this down to a GPO which was populating the local Administrators group. Obviously a Domain Controller has no local users or groups so this was causing the issue. Ensuring that the GPO did not apply to the Domain Controllers - yes the GPO was linked at the root! fixed the issue. It is strange that we did not see the warnings on our main Domain Controllers only on the Read Only DC's as this would have affected all DCs the same (I would have thought)
Read more