Windows Server Technical Preview and Hyper-V Server Technical Preview Expiration Extension

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)

TOTD: DC is not advertising as a time server

#Hello, guys! 
#Here is a new tip of the day (TOTD). 
#Today we discuss how to fix the most common warning which you may receive on DCs

#You run dcdiag on your DC and receives warning "..is not advertising as a time server"

dcdiag /q
Warning: nameofdc is not advertising as a time server.
......................... nameofdc failed test Advertising

#The main time source in domain is DC with PDC role . Run the following command to query FSMO owners:

netdom query fsmo

#On your PDC you have to set up w32tm with external (generally) or internal time source. for example, pool.ntp.org

w32tm /config /manualpeerlist:pool.ntp.org /syncfromflags:manual /reliable:yes /update

#On your additional DCs run
w32tm /config /syncfromflags:domhier /update

#Restart w32time service on each DC
net stop w32time
net start w32time

#Update w32tm config
w32tm /config /update

#Resync time
w32tm /resync

#Re-run dcdiag
dcdiag /q /s:yourDCname

Time Synchronization in an AD DS Hierarchy

pdc

Links:

https://technet.microsoft.com/en-us/library/cc773013(WS.10).aspx