Windows Server 2008 R2 with SP1 Setup Issue


Recently I discovered a bug introduced in Windows Server 2008 R2 with SP1 integrated during installation while deploying a Hyper-V virtual machine.

When installing on a computer with multiple attached disks mixed between IDE and SCSI the setup process is unable to properly identify the boot disk as will install the MBR on the first SCSI disk rather than the first IDE disk. This is very interesting as Hyper-V will only boot from a IDE disk.

To resolve the issue simply detach the SCSI disk and reinstall, then reattach the SCSI disks after the install is complete.

Advertisements

Windows Server 2008 R2 Anytime Upgrade


It is possible to upgrade the installed edition of Windows Server 2008 R2 without having to reinstall the operating system. The Deployment Image Servicing and Management (DISM) tool provides the ability to perform an anytime upgrade using one of the following paths:

  • Windows Server 2008 R2 Standard upgrade to Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Enterprise upgrade to Windows Server 2008 R2 Datacenter
    Note: You can not upgrade a server while it is promoted as a domain controller.

Upgrade Guide

  1. To get started you need a command prompt with administrator privileges.
  2. Switch your current product key for a KMS Product Key found at, TechNet: KMS Client Setup Keys The following example switches your product key to the Windows Server 2008 R2 Standard KMS Product Key:

    slmgr.vbs /ipk YC6KT-GKW9T-YTKYR-T4X34-R7VHC

  3. Validate the current installed edition using the following command:

    dism /online /Get-CurrentEdition

  4. Check for upgrade options using the following command:

    dism /online /Get-TargetEditions

  5. Upgrade to target edition using one of the following examples using the target KMS client key:

    dism /online /Set-Edition:ServerEnterprise /productkey:489J6-VHDMP-X63PK-3K798-CPX3Y

    dism /online /Set-Edition:ServerDatacenter /productkey:74YFP-3QFB3-KQT8W-PMXWJ-7M648

  6. Now that the upgrade is completed you may need to change your product key volume or other type of product key, use the following command:
  7. slmgr.vbs /ipk {Product Key}