Freigeben über

Hyper-V and the Windows Server Technical Preview

  • Artikel

Today we released the Windows Server Technical Preview.  You can read more about this, and how to get the bits yourself, over on the Server & Cloud Blog.

Some other resources that are available right now are:

Cheers,
Ben

Comments

  • Anonymous
    October 01, 2014
    Looking forward to playing with this! Do you know when the RSAT package will be available, so we can test managing Server 10 from Windows 10?

  • Anonymous
    October 01, 2014
    RSAT tools for Windows 10 Preview are here: www.microsoft.com/.../details.aspx

  • Anonymous
    October 01, 2014
    Thanks Greg! Been looking for that all day!

  • Anonymous
    October 02, 2014
    New toys! Looking forward to playing with them! :-)

  • Anonymous
    October 02, 2014
    What is the predominant HyperV deployment in the public cloud? Is is Hyper-V Server 2012 on bare metal or Windows Server 2012 with Hyper-V?

  • Anonymous
    October 03, 2014
    I installed Windows Tech Preview on my laptop and I noticed it is cooler running Hyper-V virtual machines. I also notice there is now procesor throtling available on the power profiles.

  • Anonymous
    October 08, 2014
    I have trying to install Server 2003 in a VM.  There doesn't seem to be option to install integration services so I can get the drivers for the Ethernet NICs. The notes say integration services are now part of windows update which I can't access because I can't install the drivers for the Ethernet NICs.  In addition, I require that the VM's not be attached to the internet - only ever connected to a private network.  How can I install integration services?

  • Anonymous
    October 14, 2014
    @Darren: get the vmguest.iso from a Windows Server 2012 R2 server (c:windowssystem32vmguest.iso) which has Hyper-V installed and attach it to your 2003 VM

  • Anonymous
    December 30, 2014
    The comment has been removed

  • Anonymous
    August 03, 2015
    McArthor, did you ever find a fix for Hyper-V Mgt with Windows 10?  It only seems to be happening when trying to manage clustered nodes.  I can connect to non-clustered nodes just fine.  So far Microsoft forums don't seem to be of any help when I post this issue.