This looks like a problem we found when you have both the HyperV and RDSH roles installed on your HyperV box. Is this the case? Apparently there is a licensing conflict when both of these roles installed when not using NLA authentication. If the host is intended to be used for VDI, can you remove the RDSH role?
No problem, glad that helped. This isn't a typical use case, but I'm sure more people will hit this issue. I'll let you know when/if this issue is resolved.
I have the same error chaps - I have Hypernode1 and Hypernode2 in a cluster, and both are configured with the following bits:
They are licensed correctly, and when I RDP directly to the vDesktop from another machine on the LAN, it works fine, however, when I try to access via the Web Portal, I receive the licensing protocol error. I've tested with and without GA enabled, and can successfully log on to another non-RemoteFX vDesktop from the same portal without issue.
DELL-Marc Z
30 Posts
773
1
Posted April 27th, 2011 15:00
Daniel,
This looks like a problem we found when you have both the HyperV and RDSH roles installed on your HyperV box. Is this the case? Apparently there is a licensing conflict when both of these roles installed when not using NLA authentication. If the host is intended to be used for VDI, can you remove the RDSH role?
Marc