Good morning,
I've been struggling with Windows 2008 R2 VM running in a Esxi 5 cloud that was recently upgraded from Esxi 4.1. This problem existed in the 4.1 environement as well where it appears to be a "known" issue.
Basically, the server functions normally except that RDP and Console access via Vcenter both become unusable within 24 hours of a server reboot. I've been through all of the resolutions I could find on the boards here and at Microsoft but as of this morning, still can not connect to the server via RDP or Console without a reboot.
Our cloud runs on 3 IBM x3550 M3 systems, each configured with 64gb memory, dual 6 core Xeon X5650 processors.
Our storage unit is an IBM DS3512 with expansion unit.
The server in question is running Windows 2008 R2, 64bit with all current patches. It is a VM hardware type 8, 1 cpu with 2 cores, 12gb memory, and is hosting a SQL 2008 R2 enviromnent. It it slso running the most current version of VMTools.
So far I have
- updated the display adapter to VMWare SVGA 3D (wddm)
- Configured video memory to reserve 64mb
- Changed the network card to VMXNet 3
- disabled all unnecessary devices in the VM bios (serial ports, floppy drive, com ports.)
My next step would be to rebuild the VM from scratch, however I'm trying to avoid that as we have SQL replication running with a business partner and this is one of our busiest seasons.
I've seen this problem described on Esx 3.5 and 4 enviroments, but not on 5. Is there a fix that I've missed or does anyone have any suggestions on options I can try?
Thank you!