Chat now with support
Chat with Support

Identity Manager Data Governance Edition 8.0 - User Guide

Introduction Data Governance navigation node and views Administering Data Governance Edition Managing unstructured data access
Managing resource access Managing account access Working with security permissions Working with SharePoint security permissions Account access modeling Bringing data under governance
Classifying governed resources Managing governed resources using the web portal Data Governance Edition reports Troubleshooting Appendix: EMC, NetApp Filer, and SharePoint configuration details Appendix: PowerShell commands Appendix: Governed data attestation policies Appendix: Governed data company policies Appendix: Governed data risk index functions About us

Checking the agent status

For security indexing and resource activity tracking to function as expected, the agent must have a status of Managed. You can see the status of an agent in the Agents view. Also, if the status of a managed host is anything other than Managed, check the host's agents' status to determine where the issue lies.

Note: During deployment, the state changes quickly, and a regular refresh allows you to see the changes.

Table 59: Agent states

Agent states

Description
Agent host belongs to another deployment An agent already resides on this server that belongs to another Data Governance Edition deployment. See the Status Detail column for additional information, including the name of the deployment that is already using this agent.
Agent Out Of Disk Space

The hard disk of the agent's working directory dropped below 2GB.

NOTE: This condition causes the agent to shutdown with an error. This is a safeguard to prevent disruption of other services hosted on the computer, allowing you time to add a volume or reallocate space. See Agent Shutdown Because of Error.
Agent Shutdown Because of Error

The agent may shut down with error for the following reasons:

  • Agent scanning does not progress after two hours.

  • There is not enough free disk space on the agent (minimum 2GB). See Agent Out Of Disk Space.

    		NOTE: To determine if low space on the host volume was the cause, check the Agent Events view or agent logs.
  • An error occurred while the agent attempted to open an NTFS security database to perform a sync.
Agent Update Required An unsupported agent version has attempted to register with the server.
Agent Unregistered The agent has unregistered.
Configuration Failed An error has occurred while creating the agent service on the agent host computer.
Configuration in Progress The agent service is being configured.
Deleting The agent is being deleted.
Deleting and Uninstalling The agent software is being uninstalled.
Host Configuration Failed

While preparing for an agent installation, one of the conditions were encountered:

  • The host's data root is invalid.
  • The host has a NetApp FPolicy configuration error.
Host Domain Not Managed The host domain is not yet managed in Data Governance Edition.
Install Failed An error occurred while installing the agent.
Install in Progress The agent installation is in progress.
No Communication from Agent The agent has failed to renew its lease. This state is often an indication of an error on the agent computer. Ensure that the agent can communicate with the server.
OK The agent is working properly. The agent is deployed and has contacted the Data Governance service.
Registration Failed An error occurred while the agent was attempting to register with the server.
Removal of configuration failed An error occurred while removing the agent from the agent host computer.
Removal of configuration in progress The agent service is being removed.
Resolved The managed host's information has been resolved, but it has not yet been confirmed for management. This is a temporary state.
Uninstall Failed An error occurred while uninstalling the agent service from the agent host computer.
Uninstall in Progress The agent is being uninstalled.
Uninstalled The uninstall has finished. This is a temporary state.
Unknown The current state of the agent is unknown.
Unresolvable The agent computer cannot be resolved.
Unresolved The agent computer has not yet been resolved.
Waiting for agent connection

The management server is waiting for the agent to register with the server.

 NOTE: If an agent remains in this state for a long time, it could indicate a communication issue between the agent and the server.

Viewing agent errors

You can quickly assess your agents for any potential critical issues by reviewing logged error messages using the Agents view in the Manager.

Note: The Agent Errors column in the Managed hosts view indicates when an agent associated with a managed host has encountered any errors. However, you can only view an agent's error messages using the Agents view.

To view agent errors

  1. In the Navigation view, select Data Governance | Agents.

    The Agents view appears.

  2. The Critical Error column indicates if there are any error messages logged for an agent.

  3. Select the agent from the Agents view, and select View agent errors in the Task view or right-click menu.

    Note: The View agent errors task is only available for agents that have error messages logged.

  4. The event viewer appears.

    Click the Clear Events button ( ) in the upper left corner to clear the agent errors. Click Yes on the confirmation dialog.

    Click the close button in the upper right corner to close the event viewer.

Note: You can also clear error messages for a specific agent using the Clear agent errors task from the Agents view.

Restarting agents

You must restart an agent when a new storage volume is added to the managed host being scanned by the agent.

To restart an agent

  1. In the Navigation view, select Data Governance | Agents.
  2. Select the required agents in the Agents view, and select Restart agent in the Tasks view or right-click menu.
  3. Click Yes to confirm.

Note: When a Data Governance agent is restarted, it re-creates all information within its local index. The server index is updated when the full scan completes. An agent will immediately start scanning when the service is restarted if the Immediately scan on agent restart or when managed paths change option is selected. This option is available at the bottom of the Security Scanning page on the Managed Host Settings dialog.

To determine whether data in the client is the most current from the agent, ensure that the data state of the managed host being examined is marked as "Data available."

Removing managed hosts

Removing managed hosts (and associated agents)

Note: All agents associated with a managed host are uninstalled when you remove a managed host. You can, however, remove a remote agent without removing the managed host using the Edit host settings task. For more information, see Removing agents.

Before removing a managed host ensure that the impact of its removal is considered. Any governed data records or activity information associated with resources on that host is removed from the database as well. Use caution when removing the governance on an item, as there may be business reasons for this setting. For more information on removing governance, see Managing resources under governance.

It can take a considerable amount of time to remove a managed host with governed resources (for example, one to two hours per million governed resources). The Manager lists the managed host in the "Deleting" state until this process finishes.

To remove a managed host (and its agents)

  1. In the Navigation view, select Data Governance | Managed hosts.

  2. Select a managed host from the Managed hosts view, and select Remove in the Tasks view or right-click menu.

    Note: You can select multiple managed hosts for removal.

    The Remove task is not available for host computers with a status of Not Managed.

  3. Click Remove to confirm the removal.

    If you remove a managed host with governed data, the data is no longer governed. All associated security information and resource activity is also deleted.

Related Documents