Jose Barreto published very interesting article, which explains Step-by-Step how to create a Failover Clustering for Windows Server 2008 Hyper-V JUST with File Server Storage.
Enable CPU virtualisation assistance and DEP in the BIOS.
Install Windows Server 2008 Enterprise x64 (Core Installation).
Determine the NIC ID: netsh interface ipv4 show interfaces.
Set the IP address for NIC, let say for NIC #2: netsh interface ipv4 set address name=”2″ source=static address=192.168.1.3 mask=255.255.255.0 gateway=192.168.1.1.
Set the DNS: netsh interface ipv4 add dnsserver name=”2″ address=192.168.1.2 index=1.
Rename server: netdom renamecomputer %computername% /NewName:HyperSvr1.
Reboot for that to take effect: shutdown /r /t 0.
Join it to domain: netdom join %computername% /domain:admininfo.local /userd:administrator /passwordd:*.
Reboot for that to take effect: shutdown /r /t 0.
Copy CoreConfigurator onto the Core server and configured any users, groups, enabled RDP, firewall settings, etc…
Download and copy the Hyper-V update onto the server.
Install the Hyper-V update: wusa.exe Windows6.0-KB950050-x64.msu.
Install the Hyper-V role: start /w ocsetup.exe Microsoft-Hyper-V.
Download and install Remote Management for Windows Vista.
I have seen blog posts saying that there is no support for SCSI in Hyper-V. That’s not exactly true :). Microsoft said that you can use SCSI controllers for disks but not for your boot disk, the Boot disk must be on an IDE controller. But before making decision not to use SCSI controller, you should know that Hyper-V uses an emulated IDE controller. This means there is a little bit of overhead in processing disk operations.
For SCSI support, Hyper-V uses a SCSI controller that is not emulated. Instead it uses the virtual machine bus which is much faster and requires less CPU overhead.
As you probably know, the best practice is to separate your Data from your Operating System (OS). I always install the operating system is on C: and store the data on D: drive. In Hyper-V environment, C: will be a virtual disk on the IDE controller. D: should be a virtual disk on a SCSI controller. Just test this and you will see that it’s a not so bad idea ;).
At Jun, I’ve published article “Sorry, Windows Live programs cannot be installed on Windows Server 2008“. I want to show the other (pretty same) solution about how to get manage to use Windows Live software on64-bit OS. Here it is.
Additional new guide release from Microsoft, ADMT v3.1. This guide assists Active Directory administrators in performing domain migration through the use of the Active Directory Migration Tool. Download it here.
Few days ago Microsoft released doc file, that explains all about how to “Planning and Deploying Read-Only Domain Controllers“. A read-only domain controller (RODC) is a new type of domain controller in the Windows Server® 2008 operating system. You can download this document HERE!
It’s not a secret, that IPv6 has some “issues”. When I’ve been in Seattle, at last MVP summit, a lot of IT professionals said that, and all of them recommended to disable IPv6 on Windows 2008 or / and Vista machines. Kevin Reeuwijk from “Innovative Technology Weblog” posted a very good article; Outlook Anywhere is ‘broken’ on IPv6 in Windows Server 2008.
So, if you run Exchange 2007 on Windows Server 2008 and want to use Outlook Anywhere (aka RPC over HTTP) you probably get a problem. It would not work if the RPC-over-HTTP Proxy and the Exchange Mailbox installed on the same Windows 2008 Server.
To make the long story short, simply unselect IPv6 from the properties of your NIC AND (it’s very important) make a changes to the HOSTS file. Simply open up your hosts file and make the following changes:
<IPv4 address> <hostname of the computer>
<IPv4 address> <FQDN of the computer>
This will resolve all queries for your computer’s name to its IPv4 address, effectively disabling the use of IPv6 for self-communication. You can confirm that this works by doing a “telnet localhost 6004″.
The RTM update to the Hyper-V comes with KB950050 Update for Windows Server 2008. The KB 950050 update provides improvements to security, stability, performance, user experience, forward compatibility of configurations, and the programming model. Although Hyper-V is only available for x64 system, but the KB950050 with minimal components also applies to x86 (32-bit) Windows Server 2008 system.
The 32-bit Update for Windows Server 2008 (KB950050) package includes the release version of the following:
This 64-bit Update for Windows Server 2008 x64 Edition (KB950050) package includes the release version of the following:
The KB950050 RTM update for Hyper-V will be delivered via Windows Update from July 8, 2008. For system administrators who want to update their system now, download update package setup installer from Microsoft Download Center.
Hyper-V Update for Windows Server 2008 (KB950050) 32-bit Edition
Hyper-V Update for Windows Server 2008 (KB950050) 64-bit Edition