Symantec Management Agent Communication overview
search cancel

Symantec Management Agent Communication overview

book

Article ID: 256573

calendar_today

Updated On:

Products

IT Management Suite Client Management Suite

Issue/Introduction

What happens when the Symantec Management Agent tries to communicate back to the Symantec Management Platform (SMP) for the first time?

Environment

ITMS 8.x

Resolution

Initial Communication Workflow of the Symantec Management Agent (SMA)

Introduction

The Symantec Management Agent (SMA) plays a vital role in the communication between managed client machines and the Symantec Management Platform (SMP). When a client is first set up, a specific sequence of operations is performed to ensure the machine is properly registered, inventoried, and managed. This article outlines the high-level steps the SMA takes during its initial communication with the SMP server.

Initial Communication Workflow

1. Agent Installation

The process begins with the installation of the Symantec Management Agent on a client machine, which can be either a workstation or a server.

2. Registration and GUID Assignment

Once installed, the SMA performs a registration process with the SMP server. During this step, the agent obtains a unique Global Unique Identifier (GUID) that identifies the client machine within the management system.

3. Basic Inventory Submission

Following registration, the agent sends a basic inventory of the machine to the SMP server. This initial dataset includes key information about the system's hardware and software configuration.

4. Initial Wait Period

After transmitting the basic inventory, the SMA enters a holding period where it waits up to 15 minutes before checking in with the server again. This delay allows the server time to process the data and update its records.

5. Server Processing

On the server side, the SMP processes the basic inventory and populates all required data classes for the registered resource. This includes categorizing the machine and preparing it for policy assignment.

6. Delta Resource Membership Update

A scheduled task called NS.Delta Resource Membership Update runs periodically—every 5 minutes by default. This task updates resource targets across the system. During this update cycle, the newly registered machine is evaluated and added to any applicable targets based on its attributes.

7. Policy Assignment During Agent Check-in

Once the SMA checks in again (typically for a configuration update), it receives a set of policies tailored to the resource targets it has been assigned to. These policies define what actions the agent should take on the client machine.

8. Policy-Driven Actions

Based on the received policies, the agent may perform a variety of actions, including:

  • Installing or uninstalling software

  • Installing additional plugins

  • Gathering more detailed inventory data

  • Shutting down the computer

Conclusion

The initial communication between the Symantec Management Agent and the SMP server is a structured, multi-step process designed to ensure accurate registration, inventory collection, and policy deployment. By following this workflow, the SMP can effectively manage client machines from the very first interaction.

Additional Information