Has the DHCP fingerprint changed for Win10 Release 1803?

[tobias_protz]

HMNG 11.26 on premise here. We are using the OS identification to separate clients into different VLANs. After rolling out Update 1803 onto a number of Win10 clients, I can see "Radius Reject" messages in the HiveManager, apparently the OS ist being rejected and then sent to a different VLAN normally reserved for undocumented clients.

I found that apparently MS added another entry to the OS fingerprint, 119. But if I add this as another OS object, the clients with older versions are not recognized anymore (the 1803 will be sent into the correct VLAN then though).

Is this fixed in the latest HMNG release and the OS objects that are delivered together with it?

[dsouri]

Hi Tobias,

This would be a longer process, you're absolutely right.

One alternative route, which could arguably take less time, is to spin up a brand new VM with a fresh/latest Hivemanager install, and rebuild the network policies and Objects. Then, a support agent can re-initialize your previous Keys.

Of course, for more complex deployments, this may not be the best option, as it would literally be a fresh start.

If you take the incremental route, (I don't know which version of 11.26.x you have now), once at the newest version, a support agent can re-initialize the previous keys.

I would advise taking note of the current System-ID and Active keys, to use when requesting re-initialization of the keys.

So once you've started the process, if you need assistance or run into any questions along the way, your Select-Level support provides 24/7 phone support.

Hope this helps!

David Souri

HiveCommunity Moderator

[tobias_protz]

Hi David,

Thanks a lot! Now I just have to figure out why the new OS object will affect devices which should be covered by the old one ^^

Upgrading to the latest HiveManager will need some more time, deploying a new VM and then exporting and re-importing the config does take more time than just updating the present install, so I will have to plan it during non-office-hours.

By the way, can you tell me if the licenses will all be correctly transferred during the HM upgrade process 11->12 ?

[dsouri · Accepted solution]

Hi Tobias,

It seems there was a change to the OS fingerprint, so adding the new OS Object seems to be the fix in other instances.

I would always recommend re-assessing this after getting to the latest Hivemanager On-prem Software and latest AP HiveOS Versions.

To Upgrade Hivemanager On-Prem: https://docs.aerohive.com/330000/docs/help/english/ng/Content/reference/virtual-appliance-release-notes.htm

To Know which HiveOS To upgrade Devices to:

https://thehivecommunity.aerohive.com/s/feed/0D50c00005jmpq9CAA

And for direct assistance, I see your account has Select-Level Support, so don't hesitate to create a case for the upgrade process.

Hope this helps, 

David Souri

HiveCommunity Moderator