Category: Lync Server 2010

This download will allow you to continue using the Windows Server Technical Preview and Hyper-V Server Technical Preview from October 2014 without interruption until the next preview is available in May 2015.

To install to continue using Windows Server Technical Preview and Hyper-V Server Technical Preview.

• You can either run the installer from the Download Center website, or save the download package to a local computer or share. If you save the download package to a local computer or share, double-click the installer program, Windows6.4-KB3056022-x64.msu.
• When you are prompted by the Windows Update Standalone Installer dialog box to install the update, click Yes.
• Read and accept the license terms. Click I accept. Installation requires a few minutes to finish.
• Reboot after installing. System may require up to 5 minutes to respond.

Important Notes: If you installed HyperV server from ISO, you cannot use the .msu package to patch it. You will need to use DISM. Example: dism /online /add-package /packagepath:Windows6.4-KB3056022-x64.cab

http://www.microsoft.com/en-us/download/details.aspx?id=46447

UPDATE:

For DC GUI versions, needed to activate with the key from http://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-technical-preview .

Installation Guidelines

Upon installation, you will be prompted to activate. A product key is not required for the ISO installation.

VHD installation requires the following product key:

JGNV3-YDJ66-HJMJP-KVRXG-PDGDH

Sometimes a reactivation is needed too (slmgr /ato)

Microsoft has released the most important KB for Hyper-V related with VMQ,LBFO and LM

—

Consider the following scenario:

• You have a Windows Server 2012 R2-based computer that is configured for one or more NIC teams by using Windows NIC Teaming (LBFO).
• You have implemented Windows NIC Teaming (LBFO) in Switch Independent teaming mode by using Hyper-V Port or Dynamic Load Balancing mode. Additionally, you have correctly configured the NICs to use non-overlapping processors. (For more information, see Knowledge Base article 2974384).
• A Hyper-V virtual switch is bound to one of the LBFO teams.
• You start a virtual machine on the Hyper-V server, or you live migrate a virtual machine from one server to another server.

In this scenario, you experience one or more of the following issues:

Log Name: System
Source: Microsoft-Windows-Hyper-V-VmSwitch
Date: <DateTime> 
Event ID: 113
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: Server1.contoso.com
Description:
Failed to allocate VMQ for NIC EDCED345-4C96-4C75-92A0-0C4FC5688F73--35BEB899-5BE9-4128-900A-6FE0BBFC7B22
(Friendly Name: Network Adapter) on switch DE4F3664-68D9-4781-825B-882A540FAB08 (Friendly Name: VM Switch).
Reason - The OID failed. Status = {Operation Failed} The requested operation was unsuccessful.

Additionally, the Hyper-V VmSwitch may fail to allocate VMQ queues for virtual machines.

+ This KB solves the problem described here

Download