Hi all, As we are upgrading our HP DL380 g7 to a newer server, I will now have a fairly decent server not being used anymore. I was thinking of putting Window Server 2016, but it isn't listed as supported. I know other people that have used 2012R2 drivers without any issues.

ILO 3 NIC connector. Minecraft Slow Motion Mod Download. NIC 3 connector. NIC 4 connector. HP ProLiant DL380 Generation 7 (G7). Demarrage Par Auto Transformateur Pdf To Jpg. DA - 13595 Worldwide — Version 21 — January 18, 2011. OS and Virtualization. Software and latest listing of software drivers available for your server, please visit our Support Matrix. Sirius Radio Crack Codes more. Solved: Hi, My HP Prolient DL360 G7 Server has 4 HDD but when booted it shows only Disk 0 When I goto Computer Management, Device Manager I get - 3841916. Hi: You need the HP ProLiant ILO 3 Management Controller driver. I'm having the same issue on an HP DL380 G7. Oct 22, 2012. Not all ProLiant hardware previous to G7 and Gen8 may be supported by HP drivers and software on Windows Server 2012. After doing a self-discovery on the local server and a discovery of any other network servers you have added to the list, HP-SUM will display any failed dependencies needed to fix. This table lists all of the software and firmware on this Service Pack for ProLiant. For more information on this deliverable go to www.hpe.com.

Is there any reason I can't do this besides the obvious of not being supported by HP (5 year old server, so I don't really care)? I plan to turn it into our DR server, so it would only be used for backups and running servers if the main Hyper-V failed.

I am assuming this wouldn't break any MS licensing right since I am buying a 2016 license for it? Thanks, -Kyle. Scott Alan Miller wrote:Hyper-V should never be installed as a role, only directly. Windows Server should not need to be supported on a server at all, as only the hypervisor should be.

I assume that HPE also does not support Hyper-V 2016, which is a problem. But if you had to, use Hyper-V 2012 R2 and Windows Server 2016 is all set for you then. The reason for the full install is for StorageCraft which has to runs on bare metal. I am adding the Hyper-V role, so I can live migrate servers to in the case of needing maintenance. Also if the main Hyper-V server failed, I would spool them up on the HP. TekPro wrote: Scott Alan Miller wrote:Hyper-V should never be installed as a role, only directly.