...
Last year my intern Joris Claassen has proved that it was possible to run a basic VMware Vsphere VSphere cluster on IPv6 only, and that included a Windows box as well. So things look bright.
...
Obviously, the first thing to do is to uncheck IPv4 in the interface configuration 
. For IPv6 addressing I choose autoconfigured EUI64, no privacy extensions. The reason is that this is a server, and it will not be used for any web browsing activities. Static addresses also help configuring the (empty) IP IPv6 ACLs. The idea is that during configuration and testing the IPv6 ACLs will be constructed, based on stuff that does not work. Eventually, when everything works, it might be an option to use privacy extensions.
...
The "Register this connection's addresses in DNS" option has been deselected, because this causes DNS registration requests to go out, which we do not want. Eventually things look like this:
NTP
At the time of writing, the default time server that is used by Windows 2008 R2 to sync its clock, time.windows.com, unfortunately unfortunately is not (yet) reachable over IPv6.
But again, SURFnet comes to the rescue, because several of their NTP servers are IPv6-enabled. I picked chime3.surfnet.nl, which, according to the web interface, appears to be a Meinberg NTP server. Windows digs it all-right:
...