CorpCaleCeo

Windows Hyper-V Server 2016: Does it support containers?

I’m looking to enable containers on my infrastructure however looking when I run the Get-Windows Feature command I don’t see containers as an option. I’m no referring to Windows Server 2016 (core or GUI) then enabling Hyper-V, I’m running the free hypervisor
OS specifically.

however in order to resolve will I need to install windows server 2016 core activate it and then use the containers via the full OS and not the free hypervisor and yes I could use nested virtualisation however I don’t want to go down then route. Also dose
windows Hyper-V server 2019 support containers?

Option: (1) wait for windows Hyper-V server 2019, (2) upgrade to windows server 2016 or (3) ????


Thank you, God speed

Read full post . . . .

Yesterdays update broke my hyper-v linux VM – VM Setting Key Storage Drive Enabled causing error

I updated my windows Hyper-V server 2016 core yesterday and whilst 99% of my VM’s were not affect the main once was and its not working due to VM Setting Key Storage Drive Enabled causing error how do I resolve or disable this option. the vm is off
and will not turn on and when I try I get this message below

the image below is the error code I received and it all after restarted the server after yesterdays update

Hyper-V Virtual Machine error code

Virtual VM settings

VM Setting Key Storage Drive Enabled causing error


Thank you, God speed

Read full post . . . .

importing and starting VMs in Hyper-V Server 2016 core using Powershell. All Virtual Machines are located on a diffierent partition

Background:

I’ve upgraded my infrastructure hastily and I done this before the correct way but as I sold my original server I had move the VM’s quickly but with consequences.

The correct way would have been to build the server, add to domain whilst it was live on a different Hyper-V host, assign static IP, change server name, installed windows feature e.g. Hyper-V,
etc.

I done this before and all worked fine as the DC is a VM which is was always online to authenticate against without issues e.g. AD, DNS, DHCP. however as mentioned I rushed it and now I’m stuck
in a workgroup environment on the Hyper-V server 2016 core install.

current Setup:

x1 HP ProLiant ML350 G6, 3 partitions with partition 1 is OS running Hyper-V server 2016 (Core OS), Partition 2 is VMS Datastore (I store all my Virtual machines here) and Partition 3 is ISO and
general software and files.

all other Hyper-V servers are offline and unavailable which would not help as DC VM is offline

Currently the Hyper-V server 2016 core is in a workgroup environment

IP address for the server are statically assigned, and I can ping them from w10 workstation

All workstations are on the domain there are no workgroups and I cannot connect to the domain as
the VM is offline

Firewall has been disabled on server and workstations to allow connectivity for ping, etc

routers been configured for DHCP, DG to allow connectively 

Dilemma:

How do I import the DC VM into Hyper-V via PowerShell, so I can turn it on, then I can connect the server to the domain after configuring the server IP statically, so the IP & DNS point to
the DC VM and all will be good in the world again as I can use Hyper-V manager to connect and import the other VM via Hyper-V manager?

Question:

I have a Hyper-V server 2016 core install and I’m not sure how to import the virtual machine to get them started using PowerShell with VM’s located on a different partition, does anyone know how
to do this?


Thank you, God speed

Read full post . . . .

Hyper-V Server 2016 Host to Host Migration Error – Kerberos Auth but configured

Greetings and salutations

I’m encountering an error with host to host migration both host are hyper-v server 2016 core installs and using windows 10 and server 2016 to manage them (dual boot) on client.

Background Info: I had a server 2012 which I converted from full gui to core and this had the VMs hosted on the DAS then I moved the VM’s to the new 2016 core installed hyper-v server hosts.

New system: I have upgraded to 2 x server running hyper-v server 2016 and removed the server 2012 after migration the VM’s successfully from 2012 hyperV to each of the new hyper-v 2016 server meaning 2012 was able to migrate to 2016 with
no issues but when I try to migrate from 2016 to 2016 I get errors.

Error: I get an Kerberos errors so I amended the delegation of each computer (hyper-v 2016 servers) in AD to allow Kerberos only for cifs and vm migrations, used PowerShell and undertook a gpupdate /force on the DC and both hyper-v 2016
servers. now it seems like this credential update is not reach the 2016 hyper-v hosts as this error keeps appearing no matter how many times I amend the DC (removed re-added, gpupdate /force etc).

client VMs on 2016 hyper-v host Version: All VMs have been updated and operate a version 8.0 which is server 2016 since the migration from 2012 to 2016

management client: W10 laptop domain joined with RSAT installed, hyper-v manager installed and working, able to PowerShell to each server e.g. Enter-PSSession -ComputerName: etc, RDP connects no issues, project Honolulu works fine. all good.

aspect of management work fine but just cant use vm migration on 2016 hyper-v core host?

Hyper-V Hosts: Both fully updated - set to auto, download all (test environment not live), logged in with domain accounts domainusername

RDP Enabled secure only

Domain joined

NIC: static assigned 

Can anyone shed some light on this error?

Read full post . . . .

Hyper-V Server 2016 Host to Host Migration Error – Kerberos Auth but configured

Greetings and salutations

I’m encountering an error with host to host migration both host are hyper-v server 2016 core installs and using windows 10 and server 2016 to manage them (dual boot) on client.

Background Info: I had a server 2012 which I converted from full gui to core and this had the VMs hosted on the DAS then I moved the VM’s to the new 2016 core installed hyper-v server hosts.

New system: I have upgraded to 2 x server running hyper-v server 2016 and removed the server 2012 after migration the VM’s successfully from 2012 hyperV to each of the new hyper-v 2016 server meaning 2012 was able to migrate to 2016 with
no issues but when I try to migrate from 2016 to 2016 I get errors.

Error: I get an Kerberos errors so I amended the delegation of each computer (hyper-v 2016 servers) in AD to allow Kerberos only for cifs and vm migrations, used PowerShell and undertook a gpupdate /force on the DC and both hyper-v 2016
servers. now it seems like this credential update is not reach the 2016 hyper-v hosts as this error keeps appearing no matter how many times I amend the DC (removed re-added, gpupdate /force etc).

client VMs on 2016 hyper-v host Version: All VMs have been updated and operate a version 8.0 which is server 2016 since the migration from 2012 to 2016

management client: W10 laptop domain joined with RSAT installed, hyper-v manager installed and working, able to PowerShell to each server e.g. Enter-PSSession -ComputerName: etc, RDP connects no issues, project Honolulu works fine. all good.

aspect of management work fine but just cant use vm migration on 2016 hyper-v core host?

Hyper-V Hosts: Both fully updated - set to auto, download all (test environment not live), logged in with domain accounts domainusername

RDP Enabled secure only

Domain joined

NIC: static assigned 

Can anyone shed some light on this error?

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 53 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/wp-db.php on line 1995