I wanted to connect to one of my Hyper-V virtual machines and got this error:
Checking the Internet, I found this article: http://support.microsoft.com/kb/967902/en-us
What should I say, it worked 
Recently, I wanted to test Microsoft Data Protection Manager 2007 on Windows Server 2008. My goal is to test backup and restore of MOSS and Exchange 2007.
When installing on Windows Server 2008, you can follow this instructions.
However, I experienced a problem during the population of the reports. The failure message did not say too much (“Report configuration failed. Verify that SQL Server Reporting Services is installed properly and that it is running.”), so I clicked on the link to see the logfile. Surprise: the complete HTTP response delivered from IIS was in the logfile as HTML text. So I copied the text to a new HTML file:
Okay, “Integrated managed pipeline mode”. Let’s take a look at IIS:
The “Default Web Site” is used for the Reporting Services and it uses the “DefaultAppPool”.
After changing the Managed Pipeline Mode to “Classic”, the DPM installation finished successfully.
When you use the IIS 7 FTP on Windows Server 2008, you may experience an application crash when using FTPS: 
Microsoft recently released patches to fix this.
FTP 7 Update (x86) Installation Package
http://go.microsoft.com/fwlink/?LinkId=122473
FTP 7 Update (x64) Installation Package
http://go.microsoft.com/fwlink/?LinkId=122474
Recently I got a comment how to locate duplicate SPNs when using Windows Server 2008.
Luckily, this is very easy, because the SETSPN command from Windows Server 2008 has this functionality builtin:
http://technet2.microsoft.com/windowsserver2008/en/library/39b7428a-2b45-4640-9bd7-46833007d38d1033.mspx?mfr=true
Remove the duplicate service prinicipal name
Each service principal name (SPN) must be unique. Without unique principal names, the Kerberos client is not able to ensure that the server it is communicating with is the correct one. You must identify the duplicate SPN, and then remove it.
To perform these procedures, you must be a member of the Domain Admins group, or you must have been delegated the appropriate authority.
To identify the duplicate SPN:
1. Log on to the computer referenced in the event log message. If this computer is not running Windows Server 2008, you must download and install the Windows Server 2003 Resource Kit, which includes setspn.exe.
2. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
3. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
4. Type setspn -X.
5. The output of this command will show the duplicate SPNs.
6. Use the following procedure to remove one of the duplicate SPNs.Remove an SPN
To remove an SPN:
1. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
3. Type setspn -D<SPN> <computer_name>, where SPN is the name of the duplicate SPN and computer_name is the name of the computer that is assigned the duplicate SPN.
Here is what to do if you use Hyper-V RC0 or RC1 and want to update to Hyper-V RTM. I did this recently with my server.
Done.
By the way: I did not need to reactivate my virtual machines.
You can download the update (final release) here: http://www.microsoft.com/downloads/details.aspx?FamilyId=F3AB3D4B-63C8-4424-A738-BADED34D24ED&displaylang=en
As usually, saved states and with that snapshots cannot be updated to the final release: http://support.microsoft.com/kb/950050/en-us/
I will update my Windows Server 2008 and give you some details about the process very soon.
I just heard from a colleague that Hyper-V RC1 is available for download.
You can get it here:
Windows Server 2008 x64 Hyper-V RC1 Update – KB950049
Windows Server 2008 x86 Hyper-V RC1 Update – KB950049
Attention:
The saved states made with Hyper-V RC0 do not work with RC1. The snapshots contain saved states, so they won’t work, too.
I will install the RC1 on my test notebook and share the experiences very soon.
See the Team Blog, too: http://blogs.technet.com/virtualization/archive/2008/05/20/hyper-v-rc1-release-available-on-microsoft-download-center.aspx
Okay, you have used Virtual Server for your virtual machines. Now you have Hyper-V and naturally you do not want to reinstall every machine from scratch.
Here is how you can migrate your old VHDs to Hyper-V:
1. Be sure that you backup your virtual hard disk files (VHDs)
2. Uninstall the Microsoft Virtual Machine Additions
3. If you have no Virtual Server environment to deinstall the Virtual Machine Additions, you can install Virtual Server on Windows Server 2008. Here is what you need:
(If you have uninstalled the Microsoft Virtual Machine Additions, you can continue with step 10)
4. Install Virtual Server 2005 R2 with SP1:
5. Because the Hypervisor of Windows Server 2008 makes the emulated drivers of Virtual Server virtual machines very slow, you should disable the Hypervisor as long as you want to use Virtual Server. This is not just a setting or driver, you have to boot Windows Server 2008 without the Hypervisor. You have to create a second boot entry:
bcdedit /copy {current} /d “Microsoft Windows Server 2008 – for Virtual Server”
bcdedit /set {Identifier} hypervisorlaunchtype off
The first command copies the current boot configuration to a new one called “Microsoft Windows Server 2008 – for Virtual Server”:
The second command turns the Hypervisor for the new boot entry off:
6. Now you have to restart your server, choose the new boot entry to boot it without the Hypervisor.
7. Okay, now as you are back we can configure the new virtual machine wit the old VHD in Virtual Server:
6. Turn the Virtual Machine Remote Control (VMRC) Server on:
7. Connect to the the running virtual machine with the Virtual Machine Remote Control Client:
8. Deinstall the Microsoft Virtual Machine Additions and restart the virtual machine:
9. After the virtual machine is rebooted, you can shut it down and restart Windows Server 2008 with the Hypervisor.
(You can continue here from step 2 when you have uninstalled the Microsoft Virtual Machine Additions)
10. Install Hyper-V, as mentioned in one of my earlier posts.
11. Create a new virtual machine in Hyper-V:
12. Start the new Hyper-V virtual machine.
13. Perhaps you have to activate Windows, because the Hardware has changed due to the Hypervisor:
14. Insert the Services Setup Integration Disk (If your virtual machine is Windows Server 2008 install Hyper-V RC0 or newer in it):
15. Update the Hardware Abstraction Layer:
16. After the HAL update and a reboot the device drivers are installed:
17. Reboot the Virtual Machine:
18. You have to configure the TCP/IP settings. This could be the reason why a migrated domain controller can take a very long time (15 minutes and more) to boot:
That was it, have fun with your migrated machines!
Yesterday I wanted to prepare a WSUS Server (http://technet.microsoft.com/en-us/wsus/default.aspx) for my virtual machines.
Naturally I wanted to use Windows Server 2008 as operating system. But what do do you have to install to support WSUS 3?
Here is what I found on the net:
Add the IIS Server Role with the Server Manager (always accept the required features):
Add these Role features:
After IIS 7 is installed, you can install WSUS as usual.
Summary
Install IIS 7 with the server manager and this role features:
- Common HTTP Features
- ASP.NET, ISAPI Extensions, ISAPI Filters
- Windows Authentication
- IIS 6 Metabase Compatibility
Some documentations state that the applicationhost.config XML file should be changed, but it does not make any difference in my WSUS installation.
Everyone is using Hyper-V for testing purposes and you want it, too? Read along!
Hyper-V, the new virtualization technique from Microsoft is a built-in component of Windows Server 2008 (not in Web and Itanium Edition, see http://www.microsoft.com/windowsserver2008/en/us/compare-features.aspx). So you cannot just install a program like Virtual PC or Virtual Server, you have to install Windows Server 2008 on a computer which supports Hyper-V.
There are two main hardware requirements for Hyper-V:
1. Processor with built-in virtual machine support (Intel VT, AMD-V)
2. Data Execution Prevention (DEP)
Just take a look into your BIOS if there is any virtualization setting. You have to enable it. Most recent systems have this feature, even notebooks.
Okay, you have the proper hardware and you want to dive into Hyper-V, so let’s start:
I assume that you have installed Windows Server 2008 already and therefore I will start with the installation of Hyper-V. At the moment, Hyper-V is RC0 (Release Candidate 0). It is not final yet and it is not supported by Microsoft at this time. But do not worry, a lot of people have made a very good experience with it, including me. You have to download and install the RC0 version of Hyper-V, because the version that is shipped with Windows Server 2008 is just a beta and you should not use that.
You can find the RC0 here:
http://support.microsoft.com/kb/949219/en-us
Update: In the meanwhile, Hyper-V RC1 was released:
Windows Server 2008 x64 Hyper-V RC1 Update – KB950049
Windows Server 2008 x86 Hyper-V RC1 Update – KB950049
After the installation of the RC0, you can add the Hyper-V Role with the Server Manager:
(on my PC the role was already installed)
After a reboot, you are ready to start.
The next steps, creation, migration and using virtual machines are covered in later posts.