Category: Windows Server 2008

Linux Integration Services Version v3.3 for Hyper-V

Windows Server 2012 RC Logo

Yesterday Microsoft released the Linux Integration Services for Hyper-V Version 3.3. The Installation is pretty much the same as with version 3.2. You can check out my blog post about Install CentOS on Windows 8 Hyper-V for the installation.

Linux Integration Services Version 3.3 for Microsoft Hyper-V Features

When installed on a virtual machine that is running a supported Linux operating system, Linux Integration Services for Hyper-V provides the following functionality:

  • Driver support: Linux Integration Services supports the network controller, and the IDE and SCSI storage controllers that were developed specifically for Hyper-V.
  • Fastpath boot support for Hyper-V: Boot devices now take advantage of the block Virtualization Service Client (VSC) to provide enhanced performance.
  • Timesync: The clock inside the virtual machine will remain synchronized with the clock on the virtualization server with the help of the pluggable time source device.
  • Integrated shutdown: Virtual machines running Linux can be shut down from either Hyper-V Manager or System Center Virtual Machine Manager by using the “Shut Down” command.
  • Symmetric multiprocessing (SMP) support: Supported Linux distributions can use up to 4 virtual processors per virtual machine. SMP support is not available for 32-bit Linux guest operating systems running on Windows Server 2008 Hyper-V or Microsoft Hyper-V Server 2008.
  • Heartbeat: Allows the virtualization server to detect whether the virtual machine is running and responsive.
  • KVP (Key-Value Pair) Exchange: Information about the running Linux virtual machine can be obtained by using the Key-Value Pair Exchange functionality on the Windows Server 2008 virtualization server.
  • Integrated mouse support: The cursor is no longer bound to the VMConnect window when used with the Linux Graphical user interface.

Supported Virtualization Server Operating Systems

This version of Linux Integration Services supports the following versions of Hyper-V:

  • Windows Server® 2008 Standard, Windows Server 2008 Enterprise, and Windows Server 2008 Datacenter (64-bit versions only)
  • Microsoft® Hyper-V Server 2008
  • Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise, and Windows Server 2008 R2 Datacenter
  • Microsoft Hyper-V Server 2008 R2
  • Windows 8 Release Preview (NEW)
  • Microsoft Hyper-V Server 2012 (NEW)
  • Windows Server 2012 (NEW)

Supported Guest Operating Systems

This version of Linux Integration Services supports the following guest operating systems and virtual CPU (vCPU) configurations:

  • Red Hat Enterprise Linux 6.0-6.2 x86 and x64 (Up to 4 vCPU)
  • CentOS 6.0-6.2 x86 and x64 (Up to 4 vCPU)
  • Red Hat Enterprise Linux 6.0-6.2 x86 and x64 (Up to 32 vCPU when used on a Windows 8 Release Preview or Windows Server 2012 host)
  • CentOS 6.0-6.2 x86 and x64 (Up to 32 vCPU when used on a Windows 8 Release Preview or Windows Server 2012 host)

Other supported operating systems (including SUSE Linux Enterprise Server 10 and Red Hat Enterprise Linux 5) should use the version of Linux Integration Services available at f4b5b9b64551.

Michel Lüscher from Microsoft Switzerland made a blog post back in April 2010 about how you install a Linux Guest system with the Integration Services in der Version 2.1

How to add Disk Cleanup tool in Windows Server 2008 R2


Disk Cleanup option on drive’s general properties and  cleanmgr.exe is not present in Windows Server 2008 or Windows Server 2008 R2 by default.So in order to use cleanmgr.exe you’ll need to copy two files that are already present on the server, cleanmgr.exe and cleanmgr.exe.mui.

  1. Copy “C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.1.7600.16385_none_c9392808773cd7da\cleanmgr.exe” to “%systemroot%\System32”
  2. Copy “C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.1.7600.16385_en-us_b9cb6194b257cc63\cleanmgr.exe.mui” to “%systemroot%\System32\en-US”

Now you can launch the Disk cleanup tool (cleanmgr.exe) from the command prompt.

You could also install the “Desktop Experience” feature this would also work, but why install something if you don’t need it, specially on a server.

More on this on TechNet



PowerShell: How to export Windows Eventlogs with PowerShell

This is a little dirty Windows PowerShell script which exports or backups Windows Eventlogs. The script creates a .evt file which can be used with the Windows Eventlog Viewer.

And with the next code it cleans up older exported Eventlogs.

UPDATE: If you wanna clean the Eventlog after the export you can do that by using the Clear-Eventlog cmdlet. (Thanks to Michel from

And here the whole “script”

Also check out my blog post about deleting files older than a specific date using PowerShell.

Check NTFS Version

If you need to know which version of NTFS you are using you can do that with the fsutil.exe and the following command.

In my case I am testing my C:\ drive:


More on NTFS Versions on wikipedia.

In-place Upgrade Windows Server 2008 to Windows Server 2008 R2

I’m not really a big fan of In-place Windows Upgrades, specially in the Server Environment. But we had a Server with a small application running Windows Server 2008 so we decided to in-place upgrade this Server to Windows Server 2008 R2. Now guess what it worked. Basically if the Hardware and all applications are compatible with Windows Server 2008 R2 you can try to upgrade.

  1. Start Windows Server 2008 R2 DVD or attached ISO file.
    Windows Server 2008 R2 Upgrade
  2. Choose Operation System
    Windows Server 2008 R2 Upgrade
  3. Now choose Upgrade
    Windows Server 2008 R2 Upgrade
  4. Check the compatibly report
    Windows Server 2008 R2 Upgrade
  5. Upgrading Windows
    Windows Server 2008 R2 Upgrade
  6. After that Windows reboot and if everything worked, you have now a Windows Server 2008 R2
    Windows Server 2008 R2



In the last 2 months I passed my first two MCITP (Microsoft Certified IT Professional) Certifications. The first was the new MCITP: Windows Server 2008 R2, Virtualization Administrator and the second was the MCITP: Enterprise Administrator. I am really happy it was hard work but I think it was worth it.

Remote Disk Management with “RPC server is unavailable” Error

If you have a Windows Server 2008 R2 Core Server or a Hyper-V R2 Server, which is also managed like a Core Server, you are really happy if you can use the Server Manager for this Remote Machine. Basiclly I had the the Remote Setup done. I could connect to the remote Machine with the Server Manager but when I tried to use the Disk Management on a remote Server and I got the following error “RPC server is unavailable”. After checking it I found the solution. The Problem is that the Firewall blocks the remote communication to virtual disk service. So you have to open the Firewall on the Management Machine

  1. First make sure you activated all the Remote Management options on the Remote Machine. I had all done this but its good to check that.
  2. Now you can run the following Command in cmd on the Management Machine to add the a new firewall rule