eG Help

Tags are strings that identify items such as machines, applications, desktops, Delivery Groups, Application Groups, and policies. After creating a tag and adding it to an item, administrators can tailor certain operations to apply to only items that have a specified tag. Additionally, administrators can configure tag restrictions while creating or editing desktops in Delivery Groups, and creating and editing Application Groups. The tag restriction feature provides greater flexibility and allows administrators to use the existing machines for more than one publishing task, saving the costs associated with deployment and managing additional machines. Furthermore, the tags applied on the items help administrators to define and fine-tune the policies and usage restrictions for the items. Sometimes, administrators may wish to review the utilization of the tags and tag restrictions in the environment. For this purpose, administrators can use the Tag Usage test!

This test auto-discovers the tags and tag restrictions, and reveals the count of Application Groups, Desktop Groups, machines and applications that are tagged. In addition, this test also reports the number of objects, unknown objects, reboot schedules and Entitlement policy rules with tag restrictions. This way, administrators can easily identify the count of the items that are tagged or tag restricted in the environment.

Outputs of the test : One set of results for each tag on the target Delivery Controller.

Measurement	Description	Measurement Unit	Interpretation
Desktop_groups	Indicates the number of desktop groups that are tagged with this tag.	Number
Machines	Indicates the number of machines that are tagged with this tag.	Number
App_groups	Indicates the number of application groups that are tagged with this tag.	Number
Apps	Indicates the number of applications to which this tag is applied.	Number
Total_objects	Indicates the total number of objects that are tagged with this tag.	Number
Unknown_objects	Indicates the number of unknown objects that are tagged with this tag.	Number	If a tag is applied to an object, but that object would not be visible to the calling delegated administrator via the corresponding Get-Broker* cmdlet, then the object is not counted as an object of that type, but is instead reported as an ‘unknown’ object.
Restrict_App_Groups	Indicates the number of applications that have this tag restriction.	Number	An application group can be restricted to a single set of tagged machines. Once a tag restriction has been defined for an application group, applications within the group will only be hosted by machines with the tag. This helps administrators in managing the application launches.
Restrict_ent_policy_rule	Indicates the number of Entitlement policy rules that are restricted with this tag.	Number	A tag may be used to restrict which machines may be made accessible to a user by an entitlement policy rule. A machine may be made accessible by an entitlement policy rule only if either the rule has no tag restriction or the rule has a tag restriction and the machine is tagged with the same tag.
Total_restrict_objects	Indicates the total number of objects that have this tag restriction.	Number
Restrict_reboot_schedule	Indicates the number of reboot schedules that have this tag restriction.	Number	A restart schedule specifies when machines in a Delivery Group are periodically restarted. You can create one or more schedules for a Delivery Group. The machines are identified by a tag that you apply to the machine. This is called a tag restriction, because the tag restricts an action to only items (in this case, machines) that have the tag. For example, let’s say all of your machines are in one Delivery Group. You want every machine restarted once every week, and you want the machines used by the accounting team restarted daily. To accomplish this, set up one schedule for all machines, and another schedule for only the machines in accounting.
Unknown_restrict_objects	Indicates the number of Unknown objects that have this tag restriction.	Number