ClientOS problems and confusion over process

  • 3
  • Question
  • Updated 5 months ago
Photo of Kevin Whelan

Kevin Whelan

  • 53 Posts
  • 2 Reply Likes

Posted 2 years ago

  • 3
Photo of Mike Kouri

Mike Kouri, Official Rep

  • 1026 Posts
  • 269 Reply Likes
Is there a question here?
Photo of Kevin Whelan

Kevin Whelan

  • 53 Posts
  • 2 Reply Likes
Sorry post upload failed and lost all data so having to retype

I am hoping to apply some classification and rules based on ClientOS so trying to first reduce the unknown % of clients currently listed in my HMOL 6.6r3

first question
under active clients tab: randomly one of the unknown is underlined allowing me to assign a classification,why only one out of many? and then once entered that name appears in the dashboard but the object doesn't appear in the advanced configuration common OS objects,
reading online help indicates that it should
I am unable to find one entry I was testing with to alter or remove  "Lenovo PC"
have searched HMOL and the term does not appear anywhere under search facility

Dashboard capture
Top 10 Wi-Fi Client OS Types by Usage
Report Period: May 24, 2016, 10:00AM - May 25, 2016, 10:00AM
Client OSUsageunknown117.12 GB
IOS77.29 GB
Mac_OSX_Desktop67.74 GB
WindowsDesktop_OS43.22 GB
MacOS29.92 GB
Android28.29 GB
iPod/iPhone/iPad13.22 GB
Windows7.61 GB
Lenovo PC5.15 KB

OS Object list
(none of these contain lenovo)

2nd question
I have found posts on this forum indicating additional Strings for IOS9 and MacOS El Capitan
I finally discovered the OS object list was default and was unable to be edited so I cloned the OS objects and then added in the two new OS objects sub categories.
these are now showing on the dashboard but as duplicates ie default MACOS and my cloned Mac OS Desktop both appear in pie graph
are these both a total of objects or are some clients being duplicated in each category
what is the correct procedure for this please

3rd question
Of 40 identical models of cloned  HP windows 10 64bit laptops most show as windows 8, a couple are unknown which I suspect is because they have Nov v1511 update applied.
looking into the default windows OS object it just list the dhcp strings as "default" and the http user agents are years out of date? No Windows NT 6.2 /6.3 /10.0 for example

How do I set these clientOS objects up correctly please,
 I am struggling with the whole concept and the documentation.
 It seems odd that we are having to each manually apply these additions when these OS have been live for years,
Does someone have an up to date and working list that I can copy
I have a large unknown percentage which I think can be reduced significantly
Photo of Will Rhodes

Will Rhodes

  • 45 Posts
  • 9 Reply Likes
Following this.... I''m wondering many of the same things.
Photo of Matt Davies

Matt Davies

  • 6 Posts
  • 0 Reply Likes
Following this myself.  I too want to know want to know how to update the client OS list to show the newer operating systems instead of showing "unknown" in the dashboard.
Photo of Bill W.

Bill W.

  • 222 Posts
  • 35 Reply Likes
I am by no expert on this, but I'll give you some suggestions, info, and conjecture.  First, if you upgrade HM to the current version (as of this post 6.8r4), then many of the OS objects will get updated.  This is a screenshot of my Windows OS object in my HM:

As you can see, Windows 10 is now in there in DHCP options.

If you can't or don't want to upgrade at this time, you can add the entries in yourself.  It appears you cannot modify the default OS Objects even though there are buttons that make you think you could.  The New and Remove buttons should be grayed out.  Because even though you can use them, you cannot save your changes.

So what you could do is create a new OS Object, let's call it "Windows 10", and then add in the DHCP option and User Agent entries for Windows 10.  The DHCP Option 55 for Windows 10 is 1,3,6,15,31,33,43,44,46,47,121,249,252.  The HTTP User Agent ID Field for Windows 10 is "Windows NT 10.0".  You could do this for any missing OS.  Extra info, the HTTP User Agent ID Field for Windows 10 Phone is "Windows Phone 10.0", so you can make that too.

As for the duplicates, this is just a guess, but it is because you cloned the OS Object and then didn't remove the existing entries.  Instead of cloning, you should have just created a new one with just the entries that were missing.  HM uses all OS Objects.  So I theorize that if you have the same entries in multiple OS Objects, they will appear as duplicates in the dashboard.  Try removing the duplicate entries from your cloned OS Object, or delete your cloned OS Object and create a new one with just the missing entries.
Photo of Kevin Rennie

Kevin Rennie

  • 1 Post
  • 0 Reply Likes
Great post thanks, have been trying to add OS details for bring my 6.6r3a upto date but when I add the OS Type and apply the option to save is greyed out. When I go back to the OS Objects the details I added and applied are no longer there.

What am I missing??

Photo of Kevin Whelan

Kevin Whelan

  • 53 Posts
  • 2 Reply Likes

this is 6.8r5 default and doesn't have any changes.
I have manually made  my own windows object like you but why do we all have to research and find the tags and apply them individually
the whole system appears very random
Photo of Bill W.

Bill W.

  • 222 Posts
  • 35 Reply Likes
Oops...I'm a month behind. 6.8r5 is the current release, not 6.8r4 like I stated.  I don't have a "flying bee" in HM, and the HiveNation announcement on the home page is still announcing 6.8r4 as the new release, so I didn't realize they had a new release.

My screenshot that has Windows 10 in it is from HM 6.8r4 and is NOT modified.  You can tell because in the Parameter Request List the entry for Windows 10 is Default.  I'm not sure why yours has a Windows 8 entry instead of Windows 8/10 entry and is missing the Windows 10 entry.  My HM is on-prem. Is yours online? Although I don't see why they would have the on-prem one different than the online one, I guess it could be.

Unfortunately, we have to research this and make changes like this because Aerohive (and any vendor for that matter because this is not isolated to just Aerohive) has no control over what DHCP fingerprint companies use.  So Aerohive is always catching up.  And the OS objects may or may not get updated when a new version of HM is released.  And even if they are updated, they will probably already be out of date.  There are new OS's on network devices coming out all the time.  And Aerohive will most likely only include those of the most common OS's as it would be difficult to include every one.  I've found that a good place to look up these fingerprints is at