Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

252656

December 29th, 2015 02:00

vWorkspace 8.0 | HyperV 2012 R2 | Virtual Network Name

At a customer we just upgraded all the HyperV servers to HyperV 2012R2.


Now we got an issue that the 'Virtual Network Name' is saying '


Is this a known issue?

17 Posts

December 29th, 2015 02:00

Reimporting doesn't work in my case.

As a workaround we already defined the network name in the provisioning settings manually, but it is still a strange issue.

feature or bug what's the difference ;)

32 Posts

December 29th, 2015 02:00

we had exactly the same problem.

When you remove the template and re-Import the template from the broker then the Network Name is correct.

as workaraound we define the network name in the provisioning settings. no we can sure the network is correct

if this is a feature or a bug, i don't know...

January 4th, 2016 00:00

Noticed same things on my environment too, VDI Machines tagged to different Ethernet label.

Regards,

No Events found!

Top