LDAP error codes

LDAP: error code 49 - 80090308: LdapErr: DSID-0C090400, comment: AcceptSecurityContext error, data 52e, v1db1 ​
525​ user not found ​
52e​ invalid credentials ​​
530​ not permitted to logon at this time​​
531​ not permitted to logon at this workstation​​
532​ password expired ​​
533​ account disabled ​​
701​ account expired ​​
773​ user must reset password ​​
775​ user account locked​

MBAM 2.5 sp1 - issue with reports after system update

MBAM 2.5.1100.0 (clear MBAM 2.5 sp1 - no fixes) issue with reports after installation of the following fixes:

KB4033369

KB4284878

KB4230450

System contains two servers - frontend and database server (with reporting services). Issue is after installation on database/report server.

Windows 2016 or Windows 10 - Check updates Install updates - grayed out

Strange error/configuration problem. Windows 2016 or Windows 10 (Enterprise, but it's probably connected with every SKU) - policies applied and as an administrator You can't check for updates and You can see this stupid message:
Some settings are managed by your organization

Very funny, I'm an administrator, the gpo works perfectly for Windows 2008/R2/2012/R2 but for 2016 not.
Multiple people have the same problem but for some unknown reason there are not too many solutions. The best one is here - Microsoft forum for Partners.
In a few words:
- change to Not Configured policy Remove access to use all Windows Update features;
- do two restarts;
It should work now.

Windows 2008R2 multi-homed Exchange server loses communication

Problem: Exchange 2010 servers lost communication with domain - with domain controllers
Scenario:

• multi-homed Exchange 2010 servers - with two network interfaces - 1st to communicate with domain controllers, the 2nd to communicate with users;
• default gateway is on the 2nd network card - to communicate with users;
• the 1st NIC hasn't got default gateway - communication with domain controllers is possible via static route;
• when some of domain controllers are disabled (restart or something) then some of Exchange servers are losing their connection with domain controllers;
• lost communication means everything available by routes on the 1st NIC is unavailable; static routes are present, but Windows 2008 R2 disallows communication; when I remove these routes and add it again then communication returns;
• important: firewall is enabled but whole communication is allowed.

Error is repeatable, customer is a big bank with many localizations, during this strange behaviour other systems are working fine - only some of these Exchange servers are losing communication, e.g. 5 of 10 Exchange servers can't communicate with domain controllers and rest of them still can communicate.

Error disappears when firewall is disabled, but company has got policy with requirement of enabled firewall.  

Solution: 
suspected service is Network Location Awareness (NLA) which comes to play when something in networks is changing. It discovers that domain is unavailable (missing domain controller used by Exchange services) and tries to switch network from Domain to... Public but probably it is not possible (error?). 
Similar problem is described here KB980873

We used information available in: Technet:
- in gpo for these servers
- in section: Computer Configuration | Windows Settings | Security Settings | Network List Manager Policies
- change  Location Type from Not configured to Public or Private, but not leave it in default Not configured.

After change from Not configured to Public problem disappears.

MBSA viewreport error

Microsoft Baseline Security Analyzer - ver 2.1 and 2.2
Error: Unable to get value of the property "text": object is null or undefined.





Solution: open mbsa file in your favorite editor and analyze the source - I've got in my mbsa files on the end of the file something like this:

    <Composite>42</Composite>
</SecScan>a3949b83a494d724b05812ac559a24c.exe</DownloadURL>< ... and it's not end!!!


Make a copy of your files and remove the whole text after the </SecScan>. It's a kind of damage inside this mbsa files.