To fix your problem it depends on whether your server subnet has DHCP scopes enabled (in which case your server was just given a new IP address and probably re-registered in DNS and you DON'T EVEN KNOW YOU HAVE A PROBLEM). If you don't have DHCP scopes you
server was given a 169.x.x.x IP address by the built-in resolver in Windows and you HAVE NO NETWORK CONNECTIVITY. You will need to launch a console session from vCenter to update the network adapter to the previously set static IP address, subnet mask, and
Hey Microsoft, when will you fix KB4088875?
6 people were helped by this reply
Did this solve your problem?
Sorry this didn't help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.