Link to home
Create AccountLog in
Avatar of Paul Walsh
Paul Walsh

asked on

Windows March update ldap hardening.

Hi all,

Ahead of the Microsoft update in March forcing ldap hardening, I have a few questions

1.Is the update actually making any direct changes (enforcing the settings), or is it simply making the necessary changes but the actual applying of the settings will happen later in the year in another update?

2. We are currently in the process of moving to ldaps however I have read that this may be not be necessary and that we can force the ldap signing settings via gpo and this will suffice (along with channel binding). Is this correct?

3. If we wanted to delay the changes I am assuming I simply don’t install the march update until we are ready on the DC’s. What about all the windows clients in the network. Will these simply carry on working even if the update is applied to them?

Avatar of Adam Brown
Adam Brown
Flag of United States of America image

Link to home
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of Paul Walsh
Paul Walsh



Cool. Just to clarify then, if we haven’t setup an internal CA before the update, clients will still be ok even after the update has been applied to them ( they will use Kerberos). If we don’t install the update on the DC, third party/ external devices will be ok.

So my thinking is get CA installed (2 tier) and install certificates onto dc.

Then enable ldaps and move external devices over to ldaps.

once done then install the March update.

Is my thinking correct?


That is a good action plan. Should work well. 2 tier CA may not be necessary (depends heavily on your compliance needs and physical security on the servers). Best practice says 2 tier, but best practices are recommendations only and don't apply to all situations.