Introducing AppClarity 5.2
How it works
Working with AppClarity
Technical support for AppClarity
AppClarity 5.2 - Implementing and Using Lab Guide
Ex 1 - AppClarity 5.2 - Installing the 1E Catalog and the 1E SLA Platform
Ex 2 - AppClarity 5.2 - Scouting for devices and applications
Ex 3 - AppClarity 5.2 - Getting data from a restored CM database
Ex 4 - AppClarity 5.2 - Installing AppClarity
Ex 5 - AppClarity 5.2 - Connectivity and Integration with ActiveEfficiency
Ex 6 - AppClarity 5.2 - Exploring Applications, Products and Installations
Ex 7 - AppClarity 5.2 - Working with Management Groups
Ex 8 - AppClarity 5.2 - Entitlement Management and Compliance
Ex 9 - AppClarity 5.2 - Software Reclaim
- Ex 1 - AppClarity 5.2 - Installing the 1E Catalog and the 1E SLA Platform
- AppClarity 5.2 - Implementing and Using Lab Guide
Working with Management Groups
Management Groups are used to partition Installations and Licenses within AppClarity to allow for granular management of reporting, licensing and software reclaim. A Management Group defines a group of installations, so that for example each department or geographical entity can view and manage their own Installations. A Management Group can also be defined as a License Container, which enables Licenses to be allocated to the individual groups, rather than being applied centrally.
Each installation can only exist in a single given Management Group (except the Global View Management group which shows all installations). By default, they will be added to the Central Management Group, which is a built-in Management Group that is configured as a License Container and used to contain all Installations that do not meet the criteria for any other Management Group. There is also a Global View Management Group, which will always show every installation.
For some small or centrally managed organizations, where a single team is responsible for management and licensing of software, it may be perfectly acceptable to manage everything centrally through these built-in Management Groups. However, many organizations will require some level of partitioning to allow different groups to manage Installations and Licenses on different groups of machines.
It may be useful in some organizations to use a term such as 'Cost Center' or 'Business Unit' instead of 'Management Group'. AppClarity allows an administrator to define their own term for Management Group as it appears in the console by modifying values in the SiteSettings table in the AppClarity database. The following example SQL query could be used to change the label for Management Group to Business Unit. The AppClarity console will need to be closed and reopened for the changes to reflect.
UPDATE [SiteSettings] SET uss_ManagementGroup_ManagementGroupLabel='Business Unit'
UPDATE [SiteSettings] SET uss_ManagementGroup_AllManagementGroupsLabel='All Business Units'
Creating a Management Group
In this exercise, you will create a new Management Group, define the rules which will determine which Installations become members of the group and then observe the effects of this in the console.
Create a Management Group
- In the AppClarity console, click the Configuration icon in the vertical toolbar to open the Configuration page
- Select All Management Groups. Note the built-in Central and Global View Management Groups
- Select the Global View Management Group and note the Is license container option is not checked. Observe this setting on the Central Management Group
- In the middle pane, under the Management Group heading, click the link labelled Click here to add a new Management Group
- Enter Sales as the group Name. A description can be added if required
- Uncheck the Is license container box – this group will not be used to manage licensing
- Click Apply to create the new Management Group and observe that it is added to the list of Management Groups in the middle pane
Create a Management Group Rule
Installations are added to a Management Group by applying Management Group Rules. Each Installation passes through the defined rules in order, and is added to the group associated with the first rule that applies. If none of the rules apply (or no rules are defined) the Installation will be added to the Central group.
In this task, you will create a rule that adds Installations to the Sales Management Group if the name of the computer that the Installation has been discovered on contains SAL.
- From the Configuration page of the AppClarity console, select Management Group Rules. Note that there are no rules defined by default (which is why everything ends up in Central)
- By default, the list of rules is displayed as a read-only view. Click the Edit button at the bottom of the page, then click the link labelled Click here to add a new rule…
- Enter Sales Computers as the Rule Name
- In the text that defines the query rule below the Rule Name, click the <variable> link and note the options that are available. Select device NetBIOS Name from the drop-down
- Click the equal to link and change this to containing
- Click the <value> link and enter SAL and hit Enter
- Click the <Management Group> link and select Sales from the list
- The rule should now look like this
- Click OK to save the Rule. Note that the new rule is added to the top of the list, meaning it will be evaluated first, and if an Installation meets the criteria (i.e. the NetBIOS name contains SAL) it will be added to the Sales Management Group
- Ensure the new Sales Computers rule is selected and click the Preview button at the bottom of the pane. This indicates that 0 additional installations will be reclaimed as a result of applying this rule (we'll cover software reclaim soon enough!) Click Commit to apply changes
Viewing Products for the Sales group
You can now see the effect of creating this Management Group when viewing Products in the AppClarity console.
- In the AppClarity console, open the Products page
- Note that at the top of the page there is now a Management Group drop-down. This is used to filter the view to include only Products for which there are Installations in the selected Management Group. The view is currently filtered to show Installations from the Central Management Group
- Select Global View from the drop-down, select 1E under Publishers then locate the Shopping Agent Product and observe the Install Count
- Keep the 1E Shopping Agent Product selected and change the Management Group to CENTRAL. Note that the Install Count has reduced, indicating that some Installations are no longer included in the Central Management Group
- Keep the 1E Shopping Agent Product selected and change the Management Group to Sales. The Install Count should reflect the number of Installations that were removed from the Central Management Group into the Sales Management Group
- Navigate to the Linked Installations tab in the section at the bottom. Notice the only installs showing under the Sales Management Group are machines with SAL in the machine name
- Browse around some other Products with the Sales Management Group selected. Note that the Linked Installations tab confirms that only Installations on computers containing SAL are included in this view
Delegating Management of a Management Group
Until now, you have been using the AppClarity console logged in as an AppClarity Administrator, and have therefore had visibility of all Management Groups. One of the reasons for defining Management Groups is to delegate management of them to others. In this exercise, you will add a new user to AppClarity and grant them access to just the Sales Management Group.
Create a new user
- In the AppClarity console, open the Configuration page and select the Users tab
- Click on Click here to add a new user
- Add a new user with the following properties
- Select the Roles tab, which enables permissions to be granted to each specific Management Group. Select Product Editor for the Sales Management Group (note that selecting the Product Editor permission automatically adds the Product Viewer permission) then click Apply
View the console as a restricted user
In this task, you will open the console logged on as AppConsoleUser1 and observe the limitations that have been applied.
- Log 1ETRN\User off of 1ETRNW72 and log as 1ETRN\AppConsoleUser1
- Open Internet Explorer and browse to http://1etrnap/1EAppClarity to install the AppClarity console
- Note that when the console opens on the Preferences page, the Default Management Group is set to Sales. Click the drop-down and note that this user has no other options. Role based security has limited what this user can access, which is the Sales Management Group
- Change the Home Screen to Products and click Apply. This user's activity is restricted to Product administration so it makes sense to have the Products page as their home screen
- Note that settings on all other tabs on the Configuration page are not accessible to this user. Click on the Reporting tab and review the message stating you do not have permission
- Open the Products page and note that the list of Products is filtered by the Sales Management Group, which this user cannot change
- Change the Licensable filter to include Non-licensable products to ensure there is a fair comparison to the products displayed for the AppInstaller account that is logged onto on 1ETRNAP. Note the number of Publishers is smaller than what the entire estate shows
- Close the AppClarity console and log AppConsoleUser1 out of the machine
Understanding Management Group Rules
So far you have created a single Management Group and defined a rule that adds Installations to that group when the computer's NetBIOS name contains 'SAL'. All other Installations that do not meet the conditions of this rule fall into the Central Management Group. In this exercise, you will add some more Management Groups and create rules to add Installations to these. You will then observe the effect and importance of the order that rules are sequenced.
Define Management Groups and Rules based on Device Tags
ActiveEfficiency has the ability to define custom attributes (named Device Tags) for devices it has discovered. There are a number of useful Device Tags (such as Operating System Name, ConfigMgr Site Code and Primary User) that are captured by default from the scout against the ConfigMgr database, but the feature provides an extensible key/value definition that can be used to tag devices with just about any identifier.
- From the Configuration page in the AppClarity console, create new Management Groups named Lab Computers and Production Computers, leaving each enabled as a License Container
- Create a new Management Group Rule named Lab Computers with the following properties
- Note that when you add the new rule it is inserted into the rule sequence below whichever rule was selected when you clicked Click here to add new rule…added the new rule (in this case, below Sales Computers. With the Lab Computers rule selected click the symbol to the right to move this rule above the Sales Computers rule
- Ensure the Lab Computers rule is selected and add another rule named Production Computers configured as below
- The sequence of rules should now look like this:
- If the rules are not in that order, use the arrow to move rules around to get it in the right order
- When you have created the new rules, remember to Preview and Commit the effects to make the new rules active
View the effects of the new rules
In this task, you will view the effects of the new rules on the Products page.
- In the AppClarity console open the Products page and filter the list to the Lab Computers Management Group. Click on 'a' for product to review the Apple Inc. products installed. Note that this is showing only Installations from the training lab environment (i.e. where the computers' NetBIOS names starts with 1etrn) under the Linked Installations tab
- Click on 'a' to remove the Publisher filter applied in the previous step and change the management group filter to Production Computers to observe the Installations from the restored Production ConfigMgr database (domain equals 1E)
- Change the filter to the CENTRAL Management Group and observe that there are very few Installations in this group (most Installations have now been added to the other Management Groups). Navigate to Microsoft Corporation Publisher to see a few installs
- Change the filter to the Sales Management Group. Note that there are no longer any Installations in this group
- Return to the Management Group Rules on the Configuration page and click Edit
- Change the order of the rules so that Sales Computers appears above Production Computers, as shown below
- Preview and Commit the change to make the new rule sequence active
- Return to the Products page and select the Apple Inc. publisher. Note that the Sales Management Group now includes Installations (the sales machines are now being moved into the Sales management group before they qualify for the Production Computers management group criteria)
- Select the Production Computers Management Group from the filter drop-down. This group now includes all Installations from the 1E domain that were not captured by the Sales Computers rule first (i.e. whose computer name does not contain SAL)
You have now learned how Management Groups can be used to partition up Installations in your environment. Installations are assigned to a group based on Management Group Rules, which can use various pre-defined properties or custom Device Tags to match Installations to the correct Management Group. You have observed how the sequencing of Management Rules is extremely important and may result in Management Groups not including the expected Installations.
Management Groups are typically used to define the scope of delegated management of Installations, including Policies to reclaim installations, and Licenses. You have seen how Users can be assigned to Roles for specific Management Groups. These Roles define the tasks they are able to complete on Installations and Licenses associated with the Management Group.