Example 9: List of zones and special profiles

The following examples show the additional sections of the report that show detailed information about zones and special user profiles.

The Zone report lists detailed information about each zone. Below is a sample.

Copy

Zone Report

Zone Report
CN,Type,Parent Zone,Tenant ID,Tenant URL,Is ZPA provisiong,Is agentless client supported,Number of user profiles,Number of group profiles,Number of local user profiles,Number of local group profiles,Number of local Windows user profiles,Number of local Windows group profiles,Number of cross domain users,Number of cross forest users,Number of NIS maps,Number of roles,Number of PAM rights,Number of Command rights,Number of Windows Desktop rights,Number of Windows Application rights,Number of Windows Network Access rights,Number of role assignments,Number of computer roles,Number of roles with "MFA required",Number of roles with "audit if possible",Number of roles with "audit required",Number of roles with "audit not required"

keJg5xag6R,$CimsZoneVersion7,FbiyaZP2IT,AAQ0527,http://xxxxxxxxxxx,
Yes,No,#,#,#,#,#,#,#,#,#,#,#,#,#,#,#,#,#,#,#,#,#
...

In the next section of the licensing report lists the Special AD User Profiles Defined Report. This report lists out any special user profiles (SCP) that have been defined; profiles are detected based on pattern matching such as "oracle", "hadoop", "hdfs", "hive", and so forth.

You can configure the pattern match my modifying the registry value (value name: "SpecialUserProfilePattern"; type: multi string). Each row stands for a defined name pattern (from all zones).

If there is no name pattern configured, this section is not displayed in the report.

Copy

Special AD User Profiles defined Report

Special AD User Profiles defined Report

"oracle": #
"hadoop": #
"hdfs": #
"hiv$": #
...    

The next section of the licensing report is the Special Local User Profiles Defined Report, which is very similar to the previous section. This report lists out any special local user profiles (SCP) that have been defined; profiles are detected based on pattern matching, such as "oracle", "hadoop", "hdfs", "hive", and so forth.

You can configure the pattern match my modifying the registry value (value name: "SpecialUserProfilePattern"; type: multi string). Each row stands for a defined name pattern (from all zones).

If there is no name pattern configured, this section is not displayed in the report.

Copy

Special Local User Profiles defined Report

Special Local User Profiles defined Report

"oracle": #
"hadoop": #
"hdfs": #
"hiv$": #
...