Page tree
Skip to end of metadata
Go to start of metadata

The information on this page refers to License Statistics v6.3 and newer, which consolidated group management into a single Groups page under the Administration section. If you are using a version previous to v6.3see documentation for previous versions.

Generally, license server groups are reported on in the same way as individual license servers. However, wherever status is reported, license server groups have the status "Unknown," because the license servers in a group can have various statuses.

Administrative users can create and manage license server groups using the License Server Groups tab in the Groups page, found under the Administration section in the left navigation pane. See Creating and managing groups for information on creating and managing license server groups.


All data for license server groups will be shown on reports regardless of visibility settings, so even if a feature or a license server is invisible for a particular user, that user will see usage information for it on reports. This ensures that all users viewing reports for a license server group see the same information instead of each seeing different information. 


Let's assume we have three license servers: server PL in Poland, server US in the United States, and server DK in Denmark. Each server contains the feature Windows XP Floating (WXPF) and belongs to a license server group called XF. The XF license server group has the aggregated data gathered for each WXPF feature on PL, US, and DK.

The total available licenses for WXPF per license server are:

  • USA = 10
  • PL = 10
  • DK = 10

Therefore, the total available licenses for WXPF for the license group XF = 30.

Now, let's assume there are three License Statistics users, each with different visibility settings for the license servers and features:

  • Sebastian can see all license servers and features
  • Peter's visibility settings hide license server US
  • Anna's visibility settings hide feature WXPF on the license servers DK and PL.

If visibility settings were applied to the reports for the license server group, the three users would each see different statistics for the available license count for WXPF.

  • Sebastian would see all 30 total available licenses
  • Peter would see only 20 total available licenses
  • Anna would see only 10 total available licenses

With this example, you can see the importance of ignoring visibility settings for license server groups and its features. Ignoring visibility settings ensures that every user sees the same data in the report, so each of our three users will see 30 total available licenses, regardless of their visibility settings. 

How realtime data is reported 

Realtime data is reported for features on a license server group only if each aggregated feature has realtime data. This could lead to problems in grids that display realtime data (such as the Current Utilization report), because realtime data would not be reported if a feature on one of the license servers in the group is no longer being used but has historical data. To avoid such problems, any feature on a license server group that had realtime data that was previously aggregated is no longer included in the aggregation if its usage is older than 24 hours.


Using our above example of three servers that each serve the WXPF feature, let's assume that after a couple of years, we move the DK server to a Mac OS Mavericks Nodelocked (MMN) and we do not renew the licenses for WXPF. However, we do not want to delete the historical usage data for WXPF.

Now, only two of the three license servers in the XF license server group have realtime data. Instead of excluding the realtime data for WXPF for the XF license server group because one of the features has no realtime usage, the WXPF feature on the DK server is ignored (no realtime usage within 24 hours). As a result, the realtime data for license server group XF is an aggregation of WXPF realtime usage only for the PL and US servers, which still have realtime usage within 24 hours. In this way, the realtime usage for features on the license servers in the license server group is still reported.