8 Configuration
The Advanced Management Console enables administrators to customize the application by configuring the required parameters.
This topic contains the following sections:
Agents Download
You can set the Advanced Management Console agent proxy host name and port in the Agents Download sub tab of the Configuration tab. The Agents Download sub tab consists of downloadable agent bundle files (zip files).
Note:
For Catalina, you need to install the notarized software and agent version that is released in 2.19.- In the Advanced Management Console UI, click the Configuration tab.
- Click Agents Download.
- Click Edit to display the Configure AMC Agent Proxy Settings dialog.
- Enter the following details for the agent to connect to the Advanced Management Console server:
- Agent Proxy Host Name: Specify a proxy server host name.
- Agent Proxy Port: Specify a proxy
server port number.
Note:
Clearing both the Agent Proxy host name and port deletes an existing proxy setting. If there is no proxy, then the proxy host name and port details are not needed.
Users
Access to the Advanced Management Console is managed with user accounts. When a user is added, the permissions that are given to the user determine the functions that the user can access. Users are managed in the Configuration tab of the Advanced Management Console .
The User Management topic includes the following sections:
About User Accounts
Users of the Advanced Management Console are the enterprise administrators who are responsible for managing desktops in an enterprise. A user must have an account to log in to the Advanced Management Console . Access to the different functions is controlled by the permissions given to the account.
The first time the Advanced Management Console is started, the user is prompted to create a user account. That account is then used to create additional users from the Configuration tab of the Advanced Management Console . See Creating User Accounts.
Users can change the password and edit the properties for their own account. If they do not have Administrator permission, then they cannot change their permissions. See User Permissions.
Only users with Administrator permission can create and delete users. These users can also edit the accounts of other users, including changing the permissions for the account.
Views for Users
The table view for Users in the Configuration tab of Advanced Management Console shows the user accounts that are defined. The properties view shows the properties for the selected account.
In the table view, click the arrow that appears in the Users column heading to sort the data by the values in that column. Use the navigation bar below the table to view additional pages when the number of user accounts exceeds the page size. Use the navigation bar below the properties to view the properties for other user accounts.
User Table Details
The table view for Users in the Configuration tab of Advanced Management Console provides information about the user accounts and the permissions associated with each account.
The following table describes the information that is shown in the table view for user accounts:
Column Name | Description |
---|---|
Users |
Name of the user account |
Admin Permission |
If a check mark is shown, then the account has administrator permission |
Installers Permission |
If a check mark is shown, then the account has installers permission |
Rule Sets Permission |
If a check mark is shown, then the account has rule sets permission |
Java Usage Permission |
If a check mark is shown, then the account has Java usage permission |
User Properties
The properties view for Users in the Configuration tab of the Advanced Management Console provides information about user account.
The following table describes the information that is shown in the properties view for a user account.
Property | Description |
---|---|
|
Name of the account. The string entered is used to log in to the account. |
First Name |
First name of the owner of the account |
Last Name |
Last name of the owner of the account |
Phone |
Phone number for the owner of the account |
Role |
Permissions given to the account |
Creating User Accounts
User accounts enable administrators to access the Advanced Management Console . Create the accounts for your organization and use the permissions to limit access to only the functions needed by each user.
Editing User Accounts
Edit a user account when a user's information changes or you need to change the permissions for the account. Users with Admin
permission can edit any user account. Users without Admin
permission can edit only their own account.
Changing the Account Password
You can change the account password for your Advanced Management Console as needed, regardless of the permissions given to the account.
Resetting the Admin Account Password
You can reset the admin account password of Advanced Management Console .
Note:
The password reset functionality does not support LDAP accounts.Password Rules
Requirements for Passwords
The default length for passwords is initially set by the administrator when initializing the AMC console. The length of all passwords must be between 8 and 128 characters. After the AMC console is initialized, the password length can be edited under Users in the Configuration tab. When the length is edited by changing the value in the Password Policy section of Users settings, all user accounts must use the new password length.
In addition to meeting the minimum character length requirement, all passwords must contain at least one character from each of the following groups:
-
Numbers
-
Special characters: See the following table for a list and description of the special characters that can be used in passwords
-
Lowercase letters
-
Uppercase letters
Table 8-1 Special Characters Allowed in Passwords
Name of the Character | Characters |
---|---|
question mark |
? |
at sign |
@ |
exclamation point |
! |
number sign |
# |
dollar sign |
$ |
percent sign |
% |
plus sign |
+ |
hyphen |
- |
slash |
/ |
period |
. |
backslash |
\ |
single quotation mark |
' |
comma |
, |
colon |
: |
caret |
^ |
underscore |
_ |
grave accent This character is also known as the backquote character. |
` |
tilde |
~ |
left parenthesis |
( |
right parenthesis |
) |
left brace |
{ |
right brace |
} |
left bracket |
[ |
right bracket |
] |
Deleting User Accounts
When a user account is no longer needed for the Advanced Management Console , you can delete it. Administrator permissions are required to delete a user account.
User Permissions
Access to the functions of Advanced Management Console is controlled by user accounts and the permissions given to the accounts.
The following table describes the permissions that are available:
Permission | Description |
---|---|
Admin |
Permission for managing users and desktop groups, view permission for other tabs |
Installers |
Permission for installer configuration |
Rule Sets |
Permission for desktop management, rule set management, and status |
Java Usage |
Permission for Java usage reports |
Desktop Groups
The Advanced Management Console enables enterprise administrators to define desktop groups and associate desktops with one or more groups based on desktop properties. Desktop groups are added in the Configuration tab of the Advanced Management Console . Existing desktop groups are available as filters in the Desktops tab.
This topic includes the following sections:
About Desktop Groups
Desktop groups in the Advanced Management Console provide a way to filter desktops based on the values for a group. The group name is treated as an additional property for desktops and a mapping file defines the values for that property.
As an example, consider a group named Country
, which has the values China
, France
, Russia
, and United States
. When the group is created, existing desktops are mapped to the appropriate group value. To view desktops that are associated with the group value France
, the filter criterion Country
is added in the Desktops tab and set to France
.
Desktops are associated with a group based on one of the following desktop properties:
-
IP address
-
Email
-
Host name
When the group is created, the desktop property to use is selected. A mapping file is provided, which contains a list of values for the selected desktop property and the group value to associate with the desktop.
If the desktop properties for a desktop are changed, then the new values are compared with the group mapping files. Group associations are automatically adjusted based on the new values for the desktop properties. For desktops that are added after a group is created, the desktop properties are compared with the mapping file for the group. If a match is found, then the new desktop is associated with the group.
About Mapping Files
A desktop group in the Advanced Management Console is generated from a mapping file, which is used to map desktops to the group. The mapping file can be any comma-separated values (CSV) file that contains information about the desktops in the enterprise.
Each entry in the mapping file must contain a column for the desktop property on which the mapping is based and a column for the group value that is associated with the desktop. For example, if the mapping is based on host names and the group is based on countries, then each entry must contain a host name and country name. If a mapping file contains additional columns, then that information is ignored.
The character that is used to separate columns is specified when the group is created. The default is a semicolon (;). The column indexes for the desktop property and the group value are also specified when the group is created. The index is zero-based, so the first index for the first column is 0.
The following example shows a sample mapping file named country-mapping.txt,
which can be used to create a group named Country
that contains the group values China
, France
, Russia
, and United States
. The mapping between group values and desktops is based on the host name. The file contains the host names of desktops in column 0 and the country for each desktop in column 2. The file also contains business unit information in column 1, which is ignored.
hostname1;Marketing;France hostname2;Marketing;France hostname3;Marketing;United States hostname4;Engineering;Russia hostname5;Finance;France hostname6;Finance;United States hostname7;Sales;China hostname8;Sales;Russia
- When a group is created, the mapping file is processed. Desktops
that are matched to an entry in the file are associated with the group value
that is specified for the desktop. Considering the sample mapping file in the
above example, the desktop with host name
hostname4
is associated with the groupCountry
and the group valueRussia
. - In a group, mapping a desktop to multiple group values is not allowed. So, ensure that each desktop is mapped to a unique group value.
- Desktops that do not match any entry in the file are not associated with the group.
- Entries in the file that do not match any desktop are ignored.
- The number of desktops that are matched and the number that are ignored are reported in the Configuration tab of Advanced Management Console .
- To change a mapping file, you must delete the group and create it again using the edited mapping file.
Views for Desktop Groups
The table view for Desktop Groups in the Configuration tab of the Advanced Management Console shows the groups that are defined. The properties view shows the property values for the selected group.
In both views, click the arrow that appears in the column heading to sort the data by the values in that column. Use the navigation bar below the table to view additional pages when the number of desktop groups exceeds the page size. Use the navigation bar below the properties to view the properties for other desktop groups.
Desktop Group Table Details
The table view for Desktop Groups in the Configuration tab of Advanced Management Console provides information about the number of entries in the mapping file and the number of entries that do not match a desktop.
The following table describes the information that is shown in the table view for desktop groups:
Column Name | Description |
---|---|
Group Name |
Name of the group |
Desktop Property |
Desktop property that is used to match desktops to the group |
Desktop Property Value Count |
Number of entries in the mapping file that contain the desktop property to be matched. One entry in the mapping file could match more than one desktop. For example, an email address could be associated with multiple desktops. |
Unassigned Desktop Property Value Count |
Number of entries in the mapping file that do not match any desktops. Click the unassigned desktop count value to download the CSV file. The file contains the list of desktops that don't have an agent associated with them. |
Desktop Group Property Details
The properties view for Desktop Groups in the Configuration tab of Advanced Management Console provides information about the values associated with the group and the number of desktops that match each value.
The following table describes the information that is shown in the properties view for a desktop group:
Column Name | Description |
---|---|
desktop-group-name |
Name of the desktop group. The entries in this column are the group values found in the mapping file for this group. |
number-of-desktop-property-values |
Number of entries in the mapping file that contain a value for the desktop property on which the mapping is based. The column name shows the total number of entries in the mapping file. For each row, the column shows the number of entries in the mapping file that match the group value shown in the first column. |
number-of-values-not-assigned |
Number of entries in the mapping file that do not match any desktop. The column name shows the total number of entries that are not matched. For each row, the column shows the number of entries in the mapping file that match the group value shown in the first column, but don't match any desktop. Click the count value to download the CSV file. The file contains the list of desktops that don't have an agent associated with them. |
Creating a Desktop Group
Desktop groups in Advanced Management Console add properties for searching and organizing the desktops in an enterprise.
To create a desktop group:
Updating an Existing Desktop Group
A desktop group in the Advanced Management Console organizes or groups a number of desktops together based on their properties, such as IP Address. For example, a desktop group called Country has values, such as Canada, US, and there are 100 entries that have desktop group value called Canada. You can update an existing group, by removing desktops from it, adding new desktops to it, or reassigning some desktops to a different group.
Viewing Desktops in a Desktop Group
The properties view for desktop groups in the Advanced Management Console provides links to the list of desktops that are associated with each group value. Also, desktops in the Desktops tab can be filtered by group name to see which desktops are associated with the group.
To view the desktops that are in a desktop group:
You can also use the filters in the Desktops tab to view the desktops in a group. Select the group name from the filter criteria.
Deleting a Desktop Group
When a desktop group is no longer needed, you can delete it. To change a desktop group, you must delete it and then re-create it with the edited mapping file.
To delete a desktop group:
Desktop Group Properties
Properties for desktop groups describe the mapping file that is used to create the group. The properties also identify the desktop property on which the mapping for the group is based.
The following table describes the properties for desktop groups:
Property | Description |
---|---|
Group name |
Name of the group. The group name is used as the filter name for the filter criteria and display option in the Desktops tab. |
CSV Input File |
Location of the mapping file. Click Browse to go to the file. |
Group Value Column Index |
Index of the column in the mapping file that contains the value for the group. For example, if the group identifies the country for each desktop, then this index is the column in which the country name appears. The columns are zero based, which makes the first column in the file column 0. |
Desktop Property Index |
Index of the column in the mapping file that contains the value for the desktop property that is used to determine if a desktop is part of the group. For example, if the mapping is based on the host name of desktops, then this index is the column in which the host name appears. The columns are zero based, which makes the first column in the file column 0. |
Desktop Property |
Desktop property that is used to determine if a desktop is part of the group. Select a property from the list provided. |
Separator in CSV File |
Character or string that is used to separate the values in the mapping file. The default is a semicolon (;). |
JAR Signing
In the Configuration tab of the Advanced Management Console , you can generate a self-signed certificate on the server to sign rule set jars.
Settings
The Advanced Management Console enables administrators to specify the parameters in the Java Usage Tracker properties file. Administrators can also configure the server parameters that the agent uses.
Java Usage Tracking
The Advanced Management Console agent automatically enables the Usage Tracker on agent-managed Windows and macOS desktops. However, you need to manually configure the Java Usage Tracker on the Linux operating system.
Server Settings
- In the Advanced Management Console UI, click the Configuration tab.
- Click Settings.
- Enter the Hostname of the server.
- Enter the Port Number of the server.
- Customize the browser Session Timeout for the AMC UI. A notification is displayed informing the user about the timeout and an option to extend the session. The value should be set in the range of 5 minutes to 480 minutes(8 hours).The default value is 60 minutes.
- Click Save.
Java Usage Tracker Configuration on Managed Desktops
Managed desktops are those desktops, where the Advanced Management Console agents are running and installed. The Advanced Management Console agents configure Java Usage Tracker on managed desktops. This helps you in handling the Java Usage Tracker configuration issues, if in case you have Java Usage Tracker configured with one server and want to switch to Advanced Management Console for Java tracking.
To achieve this configuration, the Advanced Management Console agent places the usagetracker.properties
file (Java Usage Tracker configuration file) in the appropriate JRE sub directory. For JREs prior to JDK 9, the file is placed in the lib/management
folder, and for JDK 9, it's the conf/management
folder. In the Advanced Management Console UI, you can download the usagetracker.properties
file in the Settings sub tab of the Configurations tab.
When you modify any of the Java Usage Tracker properties, for example Java Usage Tracker separator, Java Usage Tracker listener port, or Quote Character, and then the Advanced Management Console automatically updates such configuration on all the managed desktops.
Modifying Advanced Management Console Server Host Name
You can modify the hostname that you had specified during the initialization of Advanced Management Console , in case you had entered the host name incorrectly.
Agent Settings
This topic includes the following sections
Agent Action Intervals and Units
In the Advanced Management Console web user interface, you can set the time between regular agent actions to different values. The Advanced Management Console checks for updates to these values. When you modify the agent intervals in the Advanced Management Console UI and save the changes, a command is created with the information of the new intervals. Agents then fetch this command the next time they check for new commands and update themselves with new interval values and the new values replace the old interval values.
To configure the agent intervals:
-
In the Advanced Management Console UI, click the Configuration tab.
-
Click Agent Settings.
-
Click Edit to display the Agent Actions Interval and Units dialog.
-
Edit any of the following values. You can either edit all of them or just the ones that you want to:
- JUT Processing Interval
- Interval for the agents to report Java Usage Tracker records to the server
- Check Command Interval
- Interval to check if the server has any commands for the agent
- Standard JRE Scan Interval
- Interval to scan Java Runtime Environment (JRE) in the standard location (For example, on Windows it is
C:\Program Files\Java
) and report to server - Application JRE Scan Interval
- Interval to scan JRE under the application location (For example, on Windows it is C:\Program Files) and report to server
- LocalStorage JRE Scan Interval
- Interval to scan JREs in the entire local storage system (not targeting any particular directory) and report to server
- Agent Auto Update
- Enable or disable the agent auto update
- Agent Log File Max Size (Kb)
- Maximum agent log file size in Kb
- Number of Agent Log Files
- Maximum agent log file number during agent log rotation
- Randomize Interval
- Enable or disable randomize interval
-
Click Save.
Agent Update Initiation
The agent update initiation setting provides you with a way to influence the frequency at which agent updates are initiated or retried. This frequency can affect the load on servers and the network.
Enabling or Disabling Agent Auto Update
The Advanced Management Console provides an option in the Configuration tab to enable or disable the agent auto update.
- In the Advanced Management Console , click the Configuration tab.
- Click the Agent Settings sub tab.
- Click Edit.
- Select or deselect the Agent Auto Update check box under Agent Action Intervals and Units to enable or disable agent auto update.
- Click Save.
Tracking Managed JREs in Agents
In the Configurations tab of the Advanced Management Console UI, you can select the type of managed Java Runtime Environments (JREs), such as Standard, Private, Installed, Enterprise, or Web-enabled JREs that you want to track on the agent side. You can also include or exclude specific folders from JRE scanning and tracking.
Retaining Temporary Backup Files
AMC provides an additional option to retain the backup of temporary files.
In case of agent failure, you can use these temporary files for
debugging. However, this option is not enabled by default. To enable this
option, add a new property preserveUpdateTemporaryFiles:
TRUE
to the AMCAgent.properties
file,
which is in the Configuration folder. In case of
agent failure, find the backup files in the Versions
folder.
If the preserveUpdateTemporaryFiles
is not present
or if the option is set to FALSE
, then backup files will
not be retained. In addition, when the auto-update is successful, the
temporary files will be automatically deleted even if the property
preserveUpdateTemporaryFiles
option is set to
TRUE
.
Database Maintenance
Cleaning of older commands are auto-scheduled and runs every midnight. However, you can use the Advanced Management Console Database cleaning tool to manually delete previous commands of the specified status and date. You can also edit the threshold date and status of the commands.
- In the Advanced Management Console UI, click the Configuration tab.
- Click Database Maintenance.
- Click Clean DB to delete all commands.
- Click Edit to change the date and select the required status of the commands.
- Click Save.