On my Windows Server 2008 Enterprise x64 box, I just upgraded VMWare Server from 2.0 RC1 to 2.0 RC2 and everything seemed to work except for the following:
My Datastore for ISOs (mapped to a network share) was not working. To resolve this:
I disconnected all of the client CD rom drives that were using the store
Deleted the store
Re-created the store
Re-connected the client server's CD-ROM drives to the ISOs datastore images
I could not open a console session to a virtual server from the host OS's console. When I tried, I got the "Hostname could not be resolved for <vmwarehost>.<mydomain>. I could use another network PC to access the VMWare Server Home Page and open it successfully.
In troubleshooting, I pinged a network host and it responded with the IPv4 address. Of course, Windows Server 2008 (like Vista) will use the IPv6 address when referring to itself.
I opened C:\Windows\system32\drivers\etc\hosts and added an explicit entry to the IPv4 address for the server host to "trump" the default behavior of the OS.
The console now opens correctly.
Is there a better solution to the IPv6 thing on Windows Server 2008? I hate to leave this dropping on the server if there's a more elegant solution. I tried removing the IPv6 binding for the NIC but the system still resolves to the v6 address.
I found out how to have the VM starting in RC1 (after I uninstalled RC2 and re-installed RC1), instead of using localhost or the computer's name, I use the IP address in the shortcut that launches the VM.
I won't try RC2 and I'll wait for GA since it's working just fine for now.
FYI, the remaining "hostname could not be resolved" issues in RC2 are due to an incompatibility with IPv6 networking. The issue has been fixed and the fix will be in the next build. In the meantime, workarounds include using either the literal IP address or adding the host->IP address mapping to system32\etc\hosts.
Note that Server 2.0 GA will not truly support IPv6, in the sense that the management stack (hostd/web server) will only service incoming connections via IPv4 addresses.