HyperVServer Build

Obsolesce

I'm assuming Disk 0 is your RAID10.

You have a partition setup for 80GB which is your C volume.

Now you need to (on DISK 0), create another VOLUME using the rest of the space and give it the letter D.

Joel

Obsolesce

diskpart
select disk 0
create partition primary
select partition 5
format fs=ntfs label="DATA" quick
assign
list disk
list part
list vol

NashBrydges

@obsolesce I don't have to run any firewall powershell commands. The steps I listed above are literally all I need to do. I did this on a server about 10 days ago. Installed perfectly on a Dell R420.

NashBrydges

@joel If you followed the steps I layed out, you HAVE to log in as WSMAN\username where username is the user you setup on the Hyper-V server. I don't know why but without "WSMAN", regardless of the workgroup name, the remote management doesn't work.

Obsolesce

@nashbrydges said in HyperVServer Build:

@obsolesce I don't have to run any firewall powershell commands. The steps I listed above are literally all I need to do. I did this on a server about 10 days ago. Installed perfectly on a Dell R420.

I never mentioned the firewall.

I mentioned in my first response here to make sure the host and management PC are fully up to date.

NashBrydges

@obsolesce Haha, sorry, this was supposed to be a response to Joel's post about firewall powershell. Tagged the wrong person.

Joel

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!

Obsolesce

@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!

Why don't you just mount the ISO in a virtual cdrom for the VM?

black3dynamite

@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.

NashBrydges

@joel

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: /delete

The 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.

PhlipElder

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.

JaredBusch

@phlipelder said in HyperVServer Build:

The simplest thing to do is set up the second partition on the host,

No, never.

JaredBusch

@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.

JaredBusch

@nashbrydges said in HyperVServer Build:

@joel

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: /delete

The 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_Files folder to copy them to on the host.

PhlipElder

@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?

JaredBusch

@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.

PhlipElder

@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.

JaredBusch

@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.

PhlipElder

@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?