These issues are the direct result of Microsoft’s changes to Windows. While we at VMware are dedicated to helping our clients navigate issues like these, we do ask that you please direct feedback about Windows changes and updates to Microsoft themselves. Configuring authentication assets in vSphere is a documented and supported activity that the professionals at VMware Global Support Services GSS can help with, but that includes the prerequisite that your authentication source is usable and cooperative. Please contact Microsoft Support for guidance with reconfiguring and and all elements of Microsoft Active Directory. The doc on allowing LDAP Signing in Windows Server 2008 suggests that you want to change the “Default Domain Policy” but in order for it to be effective for domain controllers you should also edit the “Default Domain Controllers Policy” or whichever policy applies to the domain controllers, if you’ve assigned a new one.
The manner in that doc also seems to be relevant to all models of Windows, not just 2008. Once the Group Policy edits are in place that you could wait until the Group Policy refreshes immediately or use an Administrator level shell to issue the “gpupdate /force” command. From here which you can test vCenter Server connectivity to Active Directory, witnessing the behavior seen firstly of this post. As mentioned in advance, VMware vCenter Server can have dissimilar Active Directory instances configured, so trying out with an isolated example of Active Directory is recommended. Similarly, deploying a test vCenter Server equipment is suggested. Take a photo of the environment and you may restore it if every little thing goes wrong.
Nested virtualization environments, in commonplace, are a superb way to check practical adjustments similar to this. William Lam has wide components on his private blog for nested ESXi. Being safety minded, making a call which can negatively affect protection can be tough. However, there’s a lot more to data safety than just altering registry settings. Information safety experts use the “CIA triad” — confidentiality, integrity, and availability – to thoughtfully weigh the risk of a configuration, and the quick timeframes and nature of these adjustments could seriously impact availability. If you’ve already been running in this configuration you likely have compensating controls in place, equivalent to isolation firewalls, separate networks, to offer protection to against a person watching authentication traffic.
It isn’t a good suggestion to considerably delay patching. Patching is the ONLY way to remove a vulnerability from a system, and it’s the 1 way corporations and individuals can secure themselves the 2 way is excellent passwords and account hygiene. Microsoft is making this big change for a reason, and we don’t yet know what has modified because the original 2017 vulnerability disclosure. It’s in all probability that, in a few months, we can learn more about what’s driving this. That won’t be good news, something it is. By delaying or omitting patches you delay the inevitable and also you increase your risk, both from hackers and from well intentioned humans by chance making use of cumulative updates.