Hi Expert,

Background and issue:

1. Hypervisor: Hyper-V Server 2016 (note that it’s not Windows Server 2016)
2. Deployment Model:Standalone
3. Host Network: NIC teaming is used, and 2 physical NICs
4. Hyper-V Network Virtualization: 1.0 (just consider it’s supported by Hyper-V Server 2016 since both HNV1 & HNV2 are supported by Windows Server 2016)
5. Want to implement network isolation by using HNV 1.0
6. run the following PowerShell command: 

New-NetVirtualizationLookupRecord -VirtualSubnetID "5001" -CustomerAddress "10.156.1.1" -ProviderAddress "172.31.153.101" -MACAddress "00155D971F27" -Rule "TranslationMethodEncap"

    7. after that, I can view the lookup record by running get-NetVirtualizationLookupRecord, but almost 3-5 minutes later, run get-NetVirtualizationLookupRecord again, no any output, seems that the configuration is totally lost.

Thanks in advance!

amoschb

Read full post . . . .

Re-posting from this thread:
https://answers.microsoft.com/en-us/windows/forum/windows_other-performance/connecting-to-virtual-machine-management-service/f1c6c189-7937-4bac-b800-0400292ada7c

ORIGINAL POST from itr88:

Overview of environment

Hyper-V host 1 - Server 2016 - not domain bound - static IP - 4 nics (1 mgmt 2 guests and 1 spare)

- software additional to OS (webroot / labtech / veeam backup & replication)

- Runs two guests

-guest1 = DC / FS / DNS / DHCP / Backup server

-guest2 = WEBSERVER

Situation

This morning at 4am, the host reboot because of monthly patches (was not suppose to but a different story altogether), issue since then.

Can connect to host, but cannot connect to hyper-v manager, stuck on this: "connecting to hyper v management service"

We have done the following in troubleshooting

-Setup DHCP and DNS (as this is running on the DC that is not running atm)

-Run MOFCOMP %SYSTEMROOT%System32WindowsVirtualization.V2.mof

-Uninstall webroot and labtech and patches.

-Ran DCOM fixes and various other attempts to fix this

We have then booted from OS disc, reinstalled OS, after reinstall could access Hyper-V manager, imported VM’s, one failed, one succeeded, rebooted server and back to square one, unable to connect to hyper-v manager service.

Hyper-V still runs as we have the webserver running, and we can do some management via powershell, but that’s it.

Anyone encounter this or a similar issue, we’ve searched the internet and we can’t find anything closely related to this issue.

RESPONSE:

Did you end-up figuring out what happened, or find a fix?



We experienced the exact same issue on June 17th (the day after your post).



We have two VM host servers. After scheduled Windows patches in the middle-of-the-night, both rebooted.  One came up normal.  But when the other
host rebooted, it came up, but none of the VMs were online.



Same thing - It was stuck on "connecting to hyper v management service".



We tried the following, but had no luck

- Reviewed Error logs - (nothing useful, other than the service was not able to change the states of the VMs)

- Tried running MOFCOMP %SYSTEMROOT%System32WindowsVirtualization.V2.mof

- Uninstalled the recent Windows patches, rebooted



We’re running a Lenovo System X server.  We initially thought perhaps it was a firmware issue / incompatibility issue with the latest patch, but uninstalling
the patch didn’t help.



We ended up re-installing Window Server 2016, after updating all system firmware.  Ran all Windows Updates, then reinstalled Hyper-V role.



With no VMs added, we started Hyper-V manager and it came up.



We did not restore any of the prior VMs. Instead we created a new one. Started it. Rebooted the host, it all came up.



We added two more VMs, rebooted the host, all came up.



Since then, we added the rest of our VMs but have not rebooted the server.  We are definitely concerned about not having yet determined the root cause
of this issue, troubleshooting (besides reinstalling everything from scratch) or a fix.  Nothing we did brought the service back, so this is still of great concern.



Any new information you may have on this issue would be highly appreciated.

Read full post . . . .

I have 3 node in Failover Cluster，when i use live Migration function ，it accuse an error：ID21502，detail was that “the virtual machine management service failed to establish a connection for virtual machine migration with host S1;No connection could
be made because the target machine actively refused it (0x8007274D)”

ps: I can move VM between S2 and S3 by live migration

OS Win2016 std

Read full post . . . .

Hi, 

I am trying to run a command with "invoke-command" cmdlet in Hyper-V host to run a script in VM and i am getting the error "An error has occured which windows powershell cannot handle.
A rewmote session might have ended"

+categoryinfo :     openerror: (win2012:String) [], PSRemotingDatastructureException

+FullyQualifiedfieldErrorId : PSsessionstateBroken

Please provide the solution to resolve it.

Read full post . . . .

Hello,

I hope this is the right place to post this question. I have roughly 60 servers running Hyper-v Server Core 2012 r2. From time to time I have to use Hyper-V Manager to connect to one of the machines. Such as when the server loses power and shuts down. Sometimes
the RODC VM will come to the boot recovery options screen, after such a shutdown, and I have no choice but to use Hyper-V Manager to connect to it.

Recently our workstations were patched against the CredSSP vulernability, and as work around until we can get the servers patched, we’ve deployed a GPO disabling network level authentication. So, I can RDP into the Hyper-V core host using mstsc.exe, but I cannot
"connect" to the VM using Hyper-V Manager.

Has anyone seen this? The only way I can "connect" to the VMs on the the Hyper-V host using Hyper-V Manager is to uninstall the CredSSP patch on my Windows 10, 1803 PC.

I also don’t see a way to patch the Hyper-V Core server. I tried to install the patch slated for Server 2012 R2 core and it fails to install stating that the server doesn’t need this patch.

Anyway, I could use some help, if anyone has any to offer. If not, I will open a ticket with MS.

Read full post . . . .

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