Additionally, the name of the NICs weren’t the same. Further looking into showed that the NICs were set to receive IP settings via DHCP. While I was attempted to see what was going on with DNS, I noticed that it appeared the DCs I was working with were not locatable in DNS.ĭuring our troubleshooting and investigation session, the customer found on the two virtualized DCs that they had an IP address on them that was not previously assigned (he was accessing via iLO). Nothing was available to the customer (i.e. All servers at that point showed as being “disconnected” in the vSphere client, even all of the ESX servers. Everything was smooth sailing until I attempted to complete the in-place upgrade of the only physical Windows 2008 R2 DC which failed and had to perform a rollback. Eventually, the customer performed a repair of the VMware tools.
Vmware tools for windows 2012r2 update#
With some spotty mouse and video response via the VMware console after the upgrade, the customer attempted to update the VMware tools but they would not update.
On two virtualized domain controllers running Windows Server 2008 R2 Datacenter, I successfully performed an in-place upgrade to Windows Server 2012 R2 Datacenter. If the following is a known issue, I was not aware. Two were hosted on VMware 5.x servers, and one was a physical server. On Friday, I ran into a little bump when performing in-place upgrades of three (3) Windows 2008 R2 domain controllers (DC) to Windows 2012 R2 and thought you would like to know of my experience.
0 kommentar(er)
