Thinking of going Virtual with our server

[ITGURU]

Hyper-V is so simple. The cost of Datacentre is minimal especially if on EES agreement. Just renewed out agreement and on Datacentre we paid £30 per 2 cores.

[localzuk]

Hyper-V is so simple. The cost of Datacentre is minimal especially if on EES agreement. Just renewed out agreement and on Datacentre we paid £30 per 2 cores.

There's a minimum of 16 cores per server though, so that £30 becomes £240 for a server, minimum.

[talksr]

have you tried index:1 instead of 3

when i apply images i use 1 and it has worked for every DISM image i have ever made and applied

 

No, got exactly the same error:

 

 

X:\windows\logs\DISM>dism /Apply-Image /ImageFile:E:sourcesinstall.wim /index:1 /ApplyDir:C:

 

Deployment Image Servicing and Management tool

Version: 10.0.14393.0

 

 

Error: 87

The parameter is incorrect.

The DISM log filke can be found at X:\windows\Logs\DISM\dism.log

[Roberto]

There's a minimum of 16 cores per server though, so that £30 becomes £240 for a server, minimum.

 

Very true, but if you're running enough Windows Servers to need it then you're paying that anyway regardless of what virtual host you use. I know you know that @localzuk but its the kind of thing that cannot be overstated in a 'getting started with virtual server' thread.

[talksr]

Ok guys, I am really not having a lot of luck trying to install Server 16 DC core onto this server. The server is an HP ProLiant DL320e Gen8 v2.

I have been trying to install Server 2016 Data Centre core onto an 8gb USB drive connected into the back of the server so I can utilise the space on the 4x1 tb raid for hyper v images as suggested, but the server 2016 installer refuses to accept the USB drive as a possible install location. I have tried other USB drives, but it has made no difference. It just doesn't seem to like them. On the install options screen, it shows the drive as having a total size of 746.4gb - this is incorrect. It should be 7-8gb.

 

I have taken the top of the server off and can see that there is a vacant MINI SAS slot but no USB slots or SD slots available for me to plug anything in to install the OS to.

 

If I install Server 2016 DC GUI version, as soon as I install Hyper V, the server will not boot up. I have had an ongoing call open with HP for this issue since November and they have STILL not got to the bottom of it, despite a BIOS reset, various iLO updates and a new main board. The whole thing is getting a little beyond a joke now as I still have an appliance not fit to be used.

 

Any ideas.

[3s-gtech]

Is VT-d enabled in the BIOS? Possibly super patronising but it's sometimes not on by default.

[talksr]

Is VT-d enabled in the BIOS? Possibly super patronising but it's sometimes not on by default.

 

Yeah, all on. Checked it three times since the new board went in, just to be sure.

[Willott]

No, got exactly the same error:

 

Do you have back slashes in your imagefile parameter? the full command should be:

 

dism /apply-image /imagefile:e:\sources\install.wim /index:1 /Applydir:C:

 

You may need to adjust your source path to ensure you're picking up the correct WIM (ie if you do "dir e:\sources\*.wim" do you get a list of files back)?

[Davit2005]

This isn't at you guys personally, I'm just correcting some info.

 

Microsoft recommend you DO NOT use Windows Server with a GUI for Hyper-V, they would much rather you use Windows Server 2016 Core, which only has a recommended value of 512MB RAM. Also Microsoft fully support installing and running Server Core from a USB stick (this article is for 2008 R2 but same applies to 2012R2 and 2016).

 

None taken.

 

I do find that managment of core is a bit tiresome to setup. I'd suggest going down the core route however as it will stop some idiot using the host as a web browser :-) .

[talksr]

Do you have back slashes in your imagefile parameter? the full command should be:

 

dism /apply-image /imagefile:e:\sources\install.wim /index:1 /Applydir:C:

 

You may need to adjust your source path to ensure you're picking up the correct WIM (ie if you do "dir e:\sources\*.wim" do you get a list of files back)?

 

Thanks...I think we are getting somewhere...let's just hope it doesn't start freezing again once it is has installed!