Agent

1. Introduction to Agent Version Analytics

The Agent Version Analytics section provides a detailed overview of agent performance and update status across multiple hosts. This section helps IT administrators ensure that agents are up-to-date and functioning properly on all devices.

2. Key Information Available in the Agent Version Analytics Section

Host and User Data:

• Username: Identifies the user linked to the host.
• Hostname: Lists the unique device identifier where the agent is installed.
• Version: Displays the installed agent version (e.g., version 1.0).

Update Status:

• Updated: Indicates whether the agent version is up to date (True/False).
• Updated On: Timestamp of the last agent update.

Device Information:

• IP Address: Shows the host’s network address.
• Serial Number: Unique identifier for each device.
• Make and Model: Specifies the manufacturer and model of the device (e.g., Dell, HP, Lenovo).
• MAC Address: Unique identifier for the network interface of the device.
• Installed On: Timestamp of when the agent was installed on the host.

Activity Tracking:

• Last Activity: Shows the last recorded activity of the agent on the host.
• Last Activity Action: Provides insights into the agent’s most recent operation.

File Upload for Hostname Verification:

• Verify Feature: Allows administrators to upload an Excel file (.XLS or .XLSX) to validate hostnames against the Proactive Agent Version table.
• Delete Feature: Enables administrators to remove outdated or inactive hostnames by uploading an Excel file.
• The file must be formatted correctly with unique hostnames and no blank rows.

3. Updating the Self-Heal Agent to the Latest Version

Steps to Perform an Update:

1. Access the Admin Console: Navigate to the Self-Heal section and open the Admin Console.
2. Locate the Update Section: Find the “Update Self-Heal Agent” section.
3. Initiate the Update: Click the “+Version” button to open the update form.
4. Fill in Update Details: Enter the latest version number and upload the updater file (techselfsupport.zip) in the Solution field.
5. Apply Update: Submit the form to initiate the update.
6. Verify Completion: Check the Agent Analytics page to confirm that all hosts have been successfully updated.

4. Ensuring Remaining Hosts Get Updated

• Hosts that are offline during the update process will automatically update when they come online and connect to the platform.
• The updater file (techselfsupport.zip) is pre-configured to detect outdated versions and trigger the update process upon network connection.
• This ensures a seamless update mechanism, reducing manual intervention and maintaining uniformity across all devices.

5. Understanding the Configurations Section

The Configurations Section provides insights into system settings, user details, host machine configurations, and applied configurations. This section helps administrators track configuration changes, monitor deployments, and manage system settings efficiently.

Key Information Available in the Configurations Section:

• Username: The user associated with the configuration.
• Hostname: The device where the configuration is applied.
• Status: Indicates whether the configuration is CREATED or DEPLOYED.
• Type: Defines the category of the configuration entry.
• Created By: Shows the user who manually executed the Auto Solution or the system process that generated the configuration.
• Configuration String: Displays the details (in JSON format) that were entered in the form when running an Auto Solution.

6. How to View Configuration Details?

Steps to Access the Configurations Section:

Navigate to the Configurations Page

• Open the Dashboard.
• Go to Self-Heal.
• Click on Analytics.
• Select Advanced.

Search for Specific Configurations

• Use the search bar to filter configurations by Username, Hostname, or Status.
• The system will display the relevant results.

7. Difference Between CREATED and DEPLOYED Status

• CREATED: Indicates that the configuration has been generated but has not yet been applied to the target machine or user.
• DEPLOYED: Confirms that the configuration has been successfully applied and is active on the respective machine or user.