none
hyper-v 2016 on server HP DL580G7

    Question

  • Hello

    I tried to install a version of "hyper-v 2016" but I have a problem.

    Microsoft Hyper-V Server 2016 Technical Preview 5 -> TP5

    Version TP5 was in itself drivers for network cards HP DL580 G7 NC375i,

    but the final version does not support these cards.

    How can you move drivers from TP5 to the final version?

    The driver of the HP Windows 2012 R2 do not install themselves.

    I have a note about not supported operating system.

    Is it possible to do something in compatibility mode with previous versions?

    Friday, March 3, 2017 12:41 PM

Answers

  • After uploading the windows update and maneuver with the installation of drivers like windows 10 my NC375i network cards are in the system :) hyper-v 2016

    • Marked as answer by Bizonpol Monday, March 6, 2017 1:49 PM
    Sunday, March 5, 2017 8:21 PM

All replies

  • Hi Bizonpol,

    Server 2016 is not supported for HP DL580G7.
    http://h20564.www2.hpe.com/hpsc/swd/public/readIndex?sp4ts.oid=4142793&swLangOid=8&swEnvOid=4166

    Also there are no HPE drivers for network card NC375i.
    http://h20564.www2.hpe.com/hpsc/swd/public/readIndex?sp4ts.oid=4038767&swLangOid=8

    I tink not there is a supported way to move the TP5 buildin drivers to the final Version.
    Compatibility mode with drivvers? please never!

    Regards

    Sebastian

    • Proposed as answer by jc_p Thursday, March 8, 2018 10:49 AM
    • Unproposed as answer by jc_p Thursday, March 8, 2018 10:49 AM
    Friday, March 3, 2017 12:55 PM
  • I found a solution by installing the drivers of win 10.

    blog.citrix24.com/install-windows-server-2016-core-intel-nuc

    See if will work from 2012 or 2016 TP5.

    I do not know where hyper-v server 2016 puts its drivers

    Friday, March 3, 2017 1:21 PM
  • It does not make any sense to perform testing on TP5.  It is not supported and is a different distribution entirely when compared to the final release.  During the TP releases, Microsoft would include things that were expected to no be in the final build.

    The vendor of the hardware device is the one responsible for drivers for that device.  Microsoft does not write drivers for third-party devices.  Microsoft does have a method in place for third parties to have their device drivers included as part of the distribution, but there are specific timelines the vendor must meet in order for the driver to make it into the distribution.  During TP, these deadlines are more flexible, so you may find a driver in the TP that is not in the final release.

    If you have a system that is not listed in www.windowsservercatalog.com as supporting Windows server 2016, you can try drivers for Windows 10 (if they exist) to get something to work, but that does not change the support matrix.  Working and supporting are two completely separate things.

    Hyper-V Server places its drivers in the exact same location as Windows Server.


    . : | : . : | : . tim

    Friday, March 3, 2017 2:17 PM
  • Be aware that you might have to disable VMQ on your NICs, I had some troubles with a G7 server and Hyper-V 2016.

    Andreas Sobczyk CloudMechanic.net

    Friday, March 3, 2017 4:35 PM
  • After uploading the windows update and maneuver with the installation of drivers like windows 10 my NC375i network cards are in the system :) hyper-v 2016

    • Marked as answer by Bizonpol Monday, March 6, 2017 1:49 PM
    Sunday, March 5, 2017 8:21 PM
  • Solution With NC375i and windows server 2016 !!

    Justinstall this firmware update https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c0334850

    download link  : https://downloads.hpe.com/pub/softlib2/software1/cd/p1040529012/v64851/firmware-9.30-0.zip



    • Edited by jc_p Thursday, March 8, 2018 10:55 AM
    Thursday, March 8, 2018 10:54 AM
  • Hi Bizonpol,

    Are you able to explain the technical steps you took to get this working please?

    thanks

    Jack

    Wednesday, March 14, 2018 4:03 PM
  • It turns out that I do not know how it worked.
    I tried to do it again on another server, but nothing helped.
    It was only the method of exporting the hp drivers from the existing server "powershell export drivers" and the new import system using pnputil that turned out to be fully effective.

    If you want to write, I can send you exported working drivers somehow.

    Friday, April 20, 2018 9:48 PM