because your AD is not connected via ldap you have nothing to do
If LDAP connections are present through port 389, you need to modify them with port 636.
This problem has an impact on any device, Micorsoft Servers, multifunction printers, vCenter, etc ... that queries LDAP or LDAPS using port 389.
What am I supposed to change? Would I not do anything right now? or what am I supposed to do and where do I change it? I can share other information about the infrastructure to be able to control. I am currently logging into vcenter with the AD user
Now don't change anything, as Microoft releases updates every second Tuesday of the current month. So there is time.
If you log into vCenter with an Active Directory user and why vCenter runs an AD query and allows you to log in. What you need to check is the way and the port in which vCenter has been linked to the AD domain.
Microsoft is currently looking for temporary solutions, or some workarounds to bypass the problem. We are waiting for news.
As written by Microsoft, in March it will be implemented but not activated, subsequently in the months to come (not yet decided) there will be other updates that will activate the change.