HyperVServer Build
-
@joel said in HyperVServer Build:
This server build is frustrating...I managed to get the HyperV server installed and able to connect to it via Hyper-V Manager. However when trying to boot the Guest VM via my CDRom (WindowsServer2016)m it tells me the BIOS was locked and the OS was tied to vendor. Note: I was using the original CD that I got shipped with the server!!!
I then tried burning an ISO (generic) to USB but was unable to mount and boot from it as the HyperV Manager couldnt see the USB plugged into the Host! I read about making it 'offline' first but when attempting that, it turns out i couldnt make removable media offline!!
This thing is a nightmare!
Thinking of packing in Hyper-V!Sorry to be late. Me too got such errors. When tried to install the oem version of win server purchased with the machine. In my case I solved by installing from a demo iso and then coverting it in a production system via cmd line.
It was an hpe oem disk which refused to run due to hyperv exposed BIOS. Classic hpe shitwork.Let me dig into the cmds I'll post later.
-
Ok this link has the command
-
Dont know about your case. In my case the oem version expected few BIOS info masked by hyperv. Either I altered the hyperv registry or I followed the siplier demo to production conversion.
-
Minds well start getting use to not having a Desktop environment anyway. Because it will be expected to manage Windows Server 2019 from command prompt, PowerShell, RSAT or Windows Admin Center.
This screenshot is from using Windows_InsiderPreview_Server_17709
-
@black3dynamite said in HyperVServer Build:
Minds well start getting use to not having a Desktop environment anyway. Because it will be expected to manage Windows Server 2019 from command prompt, PowerShell, RSAT or Windows Admin Center.
This screenshot is from using Windows_InsiderPreview_Server_17709
Yes, very well right. Days are counted for the Windows GUI
-
@black3dynamite said in HyperVServer Build:
Minds well start getting use to not having a Desktop environment anyway. Because it will be expected to manage Windows Server 2019 from command prompt, PowerShell, RSAT or Windows Admin Center.
I remember saying this around 2012.
-
-
@stuartjordan said in HyperVServer Build:
LTSC and GUI definitely go hand in hand. Both meant for the same general audience.
-
@scottalanmiller said in HyperVServer Build:
@black3dynamite said in HyperVServer Build:
Minds well start getting use to not having a Desktop environment anyway. Because it will be expected to manage Windows Server 2019 from command prompt, PowerShell, RSAT or Windows Admin Center.
I remember saying this around 2012.
I remember you saying this a lot, I just don't remember the first occurrence anymore.
-
I got tired of seeing links here and there saying to do this and that, firewall rules open/closed here and there, add account there, etc., etc... all to no avail and only making things worse and opening security holes.
So I decided to post the working procedure that I use (nicely cleaned up, you're welcome), with the info coming straight from the MS Docs site (linked in references)... From there, I converted everything to be done via PowerShell to make everyone's life better.
You'll notice there really isn't that much you have to do to the host, and the stuff you need to do to the management PC is minimal, but a lot of what you see around the net isn't in there. Why? Because it doesn't need to be.
-
@obsolesce Apologies, I had been away for a couple weeks so just got back. I didnt thank you (and everyone else) for the comments and feedback here. @Obsolesce - your blog is so great and useful and I am very grateful for outlining those steps it works a treat (just set this up on a test environment to test it).
What would be great, is if you (or anyone else) can assist in the steps like in the blog of how then to provision a VM.
SO going over this thread, once the connection to Hyper-V Manager is established, we need to build a VM. I'd like to add a couple VM's but want to store the VDHX's on a 'D' drive (which isnt currently showing). When I built the server, I put 4 disks in OBR10 and then created a 100GB partition for the HyperVServer. I have 1.5TB free which i'd like to assign the 'D' drive. How can I connect to do this?I have tried to open Computer Management and connect to the Hypervisor but due to other firewall rules it tells me it cannot be managed.
Any help again on this? I know there's been some info above but it seems so scattered and one 'guide' steps would be useful if possible?
-
@joel said in HyperVServer Build:
@obsolesce Apologies, I had been away for a couple weeks so just got back. I didnt thank you (and everyone else) for the comments and feedback here. @Obsolesce - your blog is so great and useful and I am very grateful for outlining those steps it works a treat (just set this up on a test environment to test it).
What would be great, is if you (or anyone else) can assist in the steps like in the blog of how then to provision a VM.
SO going over this thread, once the connection to Hyper-V Manager is established, we need to build a VM. I'd like to add a couple VM's but want to store the VDHX's on a 'D' drive (which isnt currently showing). When I built the server, I put 4 disks in OBR10 and then created a 100GB partition for the HyperVServer. I have 1.5TB free which i'd like to assign the 'D' drive. How can I connect to do this?I have tried to open Computer Management and connect to the Hypervisor but due to other firewall rules it tells me it cannot be managed.
Any help again on this? I know there's been some info above but it seems so scattered and one 'guide' steps would be useful if possible?
Although - this, I believe works well.....
diskpart
select disk 0
create partition primary
select partition 5
format fs=ntfs label="DATA" quick
assign
list disk
list part
list vol -
@joel said in HyperVServer Build:
@obsolesce Apologies, I had been away for a couple weeks so just got back. I didnt thank you (and everyone else) for the comments and feedback here. @Obsolesce - your blog is so great and useful and I am very grateful for outlining those steps it works a treat (just set this up on a test environment to test it).
What would be great, is if you (or anyone else) can assist in the steps like in the blog of how then to provision a VM.
SO going over this thread, once the connection to Hyper-V Manager is established, we need to build a VM. I'd like to add a couple VM's but want to store the VDHX's on a 'D' drive (which isnt currently showing). When I built the server, I put 4 disks in OBR10 and then created a 100GB partition for the HyperVServer. I have 1.5TB free which i'd like to assign the 'D' drive. How can I connect to do this?I have tried to open Computer Management and connect to the Hypervisor but due to other firewall rules it tells me it cannot be managed.
Any help again on this? I know there's been some info above but it seems so scattered and one 'guide' steps would be useful if possible?
Happy to help!
Regarding your drive configuration...
There are some local policies you need to adjust and some firewall rules you need to open in order to use Disk Management remotely.I'd recommend installing WAC and taking care of the requirements.
https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/deploy/prepare-environment -
Thanks again. I'll take a look.
One prob I ran into last time was when I wanted to install Server 2016 on my guest VM. I had the CD Rom connected to my host, but I couldnt find where to load it to boot the VM from it.
I'd like to use a Gen2 server and i'm unsure how to get either a) to boot from the physical DVD connected to my host, or b) load an ISO to the host (ie in the D drive) to then boot from there. Any ideas on that?
