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!Copy the iso to the server instead.
-
Sometimes Hyper-V will puke all over itself when trying to install from network ISO so in most cases, I end up copying the ISO from the remote network folder to a local folder on the Hyper-V server after I've created the network drive.
- Create network drive on Hyper-V server from cmd with
net use z: \\10.10.10.200\some_folder /persistent:yes /user:username "supersecretpassword" - Create local folder for ISOs on the Hyper-V server from cmd run
mkdir c:\ISO - Copy the ISO from the network drive to the new ISO folder from cmd with
copy z:\my_iso.iso c:\ISO
If you don't want to keep the mapped network drive, remove it from cmd with
net use z: /deleteThe key is to have the ISO locally stored on the Hyper-V server. Once you do, you can use Hyper-V Manager to navigate to the local folder on the Hyper-V server to connect the ISO to use to create the VM.
- Create network drive on Hyper-V server from cmd with
-
Please have a look at these:
http://www.mpecsinc.com/powershell-guide-standalone-hyper-v-server/http://www.mpecsinc.com/powershell-guide-new-vm-powershell/
The first is a complete set of PowerShell and CommandLine to run on the newly installed Hyper-V Server OS.
The second is the PowerShell to use to set up a VM.
The simplest thing to do is set up the second partition on the host, create a folder called ISOs, copy the necessary ISO files into that folder, and tweak the above PowerShell to point to that location.
Note that since the guest VMs are Windows based, the Windows Server Standard license covers installing the host OS in Desktop Experience Mode using the Server Standard installer files and activating with the supplied key that came with the license.
-
@phlipelder said in HyperVServer Build:
The simplest thing to do is set up the second partition on the host,
No, never.
-
@phlipelder said in HyperVServer Build:
Note that since the guest VMs are Windows based, the Windows Server Standard license covers installing the host OS in Desktop Experience Mode using the Server Standard installer files and activating with the supplied key that came with the license.
It does not work like that.
-
@nashbrydges said in HyperVServer Build:
Sometimes Hyper-V will puke all over itself when trying to install from network ISO so in most cases, I end up copying the ISO from the remote network folder to a local folder on the Hyper-V server after I've created the network drive.
- Create network drive on Hyper-V server from cmd with
net use z: \\10.10.10.200\some_folder /persistent:yes /user:username "supersecretpassword" - Create local folder for ISOs on the Hyper-V server from cmd run
mkdir c:\ISO - Copy the ISO from the network drive to the new ISO folder from cmd with
copy z:\my_iso.iso c:\ISO
If you don't want to keep the mapped network drive, remove it from cmd with
net use z: /deleteThe key is to have the ISO locally stored on the Hyper-V server. Once you do, you can use Hyper-V Manager to navigate to the local folder on the Hyper-V server to connect the ISO to use to create the VM.
I always make a
C:\ISO_Filesfolder to copy them to on the host. - Create network drive on Hyper-V server from cmd with
-
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
Note that since the guest VMs are Windows based, the Windows Server Standard license covers installing the host OS in Desktop Experience Mode using the Server Standard installer files and activating with the supplied key that came with the license.
It does not work like that.
Please clarify?
-
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
Note that since the guest VMs are Windows based, the Windows Server Standard license covers installing the host OS in Desktop Experience Mode using the Server Standard installer files and activating with the supplied key that came with the license.
It does not work like that.
Please clarify?
There is no desktop experience in Hyper-V. This is basic Hyper-V 101 knowledge here.
-
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
Note that since the guest VMs are Windows based, the Windows Server Standard license covers installing the host OS in Desktop Experience Mode using the Server Standard installer files and activating with the supplied key that came with the license.
It does not work like that.
Please clarify?
There is no desktop experience in Hyper-V. This is basic Hyper-V 101 knowledge here.
To clarify:
Note, that since the guest VMs are Windows based, the license and installer files purchased to run those VMs can be used to install the host OS in Desktop Experience Mode and activate using the supplied key.
-
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
Note that since the guest VMs are Windows based, the Windows Server Standard license covers installing the host OS in Desktop Experience Mode using the Server Standard installer files and activating with the supplied key that came with the license.
It does not work like that.
Please clarify?
There is no desktop experience in Hyper-V. This is basic Hyper-V 101 knowledge here.
To clarify:
Note, that since the guest VMs are Windows based, the licensed and installer files purchased to run those VMs can be used to install the host OS in Desktop Experience Mode and activate using the supplied key.
/sigh
FFS No. this is not how anything works.
The OP is installing Hyper-V Server, as he should. Not Windows Server.
-
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
Note that since the guest VMs are Windows based, the Windows Server Standard license covers installing the host OS in Desktop Experience Mode using the Server Standard installer files and activating with the supplied key that came with the license.
It does not work like that.
Please clarify?
There is no desktop experience in Hyper-V. This is basic Hyper-V 101 knowledge here.
To clarify:
Note, that since the guest VMs are Windows based, the licensed and installer files purchased to run those VMs can be used to install the host OS in Desktop Experience Mode and activate using the supplied key.
/sigh
FFS No. this is not how anything works.
The OP is installing Hyper-V Server, as he should. Not Windows Server.
Take a deep breath.
I am suggesting that the OP instead use the OS installer files that came with the purchased license(s) to avoid the expressed frustration with the non-GUI Hyper-V Server.
That better?
-
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
Note that since the guest VMs are Windows based, the Windows Server Standard license covers installing the host OS in Desktop Experience Mode using the Server Standard installer files and activating with the supplied key that came with the license.
It does not work like that.
Please clarify?
There is no desktop experience in Hyper-V. This is basic Hyper-V 101 knowledge here.
To clarify:
Note, that since the guest VMs are Windows based, the licensed and installer files purchased to run those VMs can be used to install the host OS in Desktop Experience Mode and activate using the supplied key.
/sigh
FFS No. this is not how anything works.
The OP is installing Hyper-V Server, as he should. Not Windows Server.
Take a deep breath.
I am suggesting that the OP instead use the OS installer files that came with the purchased license(s) to avoid the expressed frustration with the non-GUI Hyper-V Server.
That better?
No, actually, because you were not suggesting that.
You never recommended that the OP wipe his install completely and then install a Windows Server instead of Hyper-V Server.
You incorrectly spewed misleading information.
Additionally, there are nearing on absolute zero situations where anyone should ever install Windows Server on the hardware.
-
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
Note that since the guest VMs are Windows based, the Windows Server Standard license covers installing the host OS in Desktop Experience Mode using the Server Standard installer files and activating with the supplied key that came with the license.
It does not work like that.
Please clarify?
There is no desktop experience in Hyper-V. This is basic Hyper-V 101 knowledge here.
To clarify:
Note, that since the guest VMs are Windows based, the licensed and installer files purchased to run those VMs can be used to install the host OS in Desktop Experience Mode and activate using the supplied key.
/sigh
FFS No. this is not how anything works.
The OP is installing Hyper-V Server, as he should. Not Windows Server.
Take a deep breath.
I am suggesting that the OP instead use the OS installer files that came with the purchased license(s) to avoid the expressed frustration with the non-GUI Hyper-V Server.
That better?
No, actually, because you were not suggesting that.
You never recommended that the OP wipe his install completely and then install a Windows Server instead of Hyper-V Server.
You incorrectly spewed misleading information.
Additionally, there are nearing on absolute zero situations where anyone should ever install Windows Server on the hardware.
That's a whole lot of "you" statements. I believe that I've made myself clear in the follow-ups.
Yes, I made a few assumptions there as tends to happen thus the need for clarification.
With a USB flash drive it takes all of 15 minutes to re-install the OS.
And, we install Windows Server on bare hardware a lot here as that's what we do for a living.
Please, feel free to express whatever opinion but keep things professional otherwise what's the point?
-
@phlipelder said in HyperVServer Build:
I believe that I've made myself clear in the follow-ups.
You did, but only because I responded to your misleading post.
-
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
I believe that I've made myself clear in the follow-ups.
You did, but only because I responded to your misleading post.
Dude, give a guy a break. Jimney Cricket.
-
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
Note that since the guest VMs are Windows based, the Windows Server Standard license covers installing the host OS in Desktop Experience Mode using the Server Standard installer files and activating with the supplied key that came with the license.
It does not work like that.
Please clarify?
There is no desktop experience in Hyper-V. This is basic Hyper-V 101 knowledge here.
To clarify:
Note, that since the guest VMs are Windows based, the licensed and installer files purchased to run those VMs can be used to install the host OS in Desktop Experience Mode and activate using the supplied key.
/sigh
FFS No. this is not how anything works.
The OP is installing Hyper-V Server, as he should. Not Windows Server.
Take a deep breath.
I am suggesting that the OP instead use the OS installer files that came with the purchased license(s) to avoid the expressed frustration with the non-GUI Hyper-V Server.
That better?
Having a GUI for no reason at all will not solve any of the OP's issues that are going on...
-
@obsolesce said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
Note that since the guest VMs are Windows based, the Windows Server Standard license covers installing the host OS in Desktop Experience Mode using the Server Standard installer files and activating with the supplied key that came with the license.
It does not work like that.
Please clarify?
There is no desktop experience in Hyper-V. This is basic Hyper-V 101 knowledge here.
To clarify:
Note, that since the guest VMs are Windows based, the licensed and installer files purchased to run those VMs can be used to install the host OS in Desktop Experience Mode and activate using the supplied key.
/sigh
FFS No. this is not how anything works.
The OP is installing Hyper-V Server, as he should. Not Windows Server.
Take a deep breath.
I am suggesting that the OP instead use the OS installer files that came with the purchased license(s) to avoid the expressed frustration with the non-GUI Hyper-V Server.
That better?
Having a GUI for no reason at all will not solve any of the OP's issues that are going on...
Having a GUI avoids the need to delve into PowerShell and CLI to set up a server for the first time. Or, at least trial and error the commands and see the results directly in the managers.
And, if the OP needs this box to go into production shortly, avoids the possibility of unknowingly having something misconfigured.
I'm pulling out. Have a great weekend everyone.
-
@phlipelder said in HyperVServer Build:
@obsolesce said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
@jaredbusch said in HyperVServer Build:
@phlipelder said in HyperVServer Build:
Note that since the guest VMs are Windows based, the Windows Server Standard license covers installing the host OS in Desktop Experience Mode using the Server Standard installer files and activating with the supplied key that came with the license.
It does not work like that.
Please clarify?
There is no desktop experience in Hyper-V. This is basic Hyper-V 101 knowledge here.
To clarify:
Note, that since the guest VMs are Windows based, the licensed and installer files purchased to run those VMs can be used to install the host OS in Desktop Experience Mode and activate using the supplied key.
/sigh
FFS No. this is not how anything works.
The OP is installing Hyper-V Server, as he should. Not Windows Server.
Take a deep breath.
I am suggesting that the OP instead use the OS installer files that came with the purchased license(s) to avoid the expressed frustration with the non-GUI Hyper-V Server.
That better?
Having a GUI for no reason at all will not solve any of the OP's issues that are going on...
Having a GUI avoids the need to delve into PowerShell and CLI to set up a server for the first time. Or, at least trial and error the commands and see the results directly in the managers.
And, if the OP needs this box to go into production shortly, avoids the possibility of unknowingly having something misconfigured.
I'm pulling out. Have a great weekend everyone.
Misconfigurations happen more via GUI than via CLI.
He's doing this in a Workgroup, so there are many things he'll have to do via CLI and PowerShell even if he had a GUI to work with.
He does not have any requirements in his Hyper-V Host needs that Hyper-V Server cannot fulfil, at least none were mentioned.
-
@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
