We use the UI on our Connection Broker frequently to shadow RDS sessions. Occasionally, when initiating a remote session, we get the error "Can't get IPv4 or IPv6 address for VM ".
The connection broker can resolve the VM name to an IP, ping the VM, etc., but will not start a shadow session. The pattern I see is when the host server of the VM does not have an IP listed in the network summary portion of Hyper V, the Connection Broker throws this error. Any time I have a vm with an IP showing in Hyper V, the shadow works fine.
Does anyone know why a Hyper V host would randomly not recognize an IP for a VM? Please see attached image where the top one gets an error and the bottom one does not. They are the same type of machine, network switch, firewall settings, GP, etc.
