Data Governance Edition includes a mechanism that enables the server to determine what agents are functioning without needing each agent to maintain a persistent connection to the Data Governance server.
Every few minutes the agent contacts the server to renew its lease. If the server has not received a lease renewal from an agent in the expected time frame, the agent goes into the "No communication from agent" state. This state indicates that the server is unable to receive information from the agent.
If an agent is in this state, you can attempt to restart the agent. For more information, see Restarting agents.. It is important to understand why the agent allowed its lease to expire. Leases may expire because the agent service stopped unexpectedly or the agent host computer lost its network connection so the agent could not contact the server to renew its lease.
Note: You can also review lease expiration information in the Data Governance server log (DataGovernanceEdition.Service.exe.dlog) in the Data Governance service installation directory (%ProgramFiles%\One Identity\One Identity Manager Data Governance Edition\Server\).
For a complete list of possible agent states, see Verifying managed host system status or Checking the agent status.
Prior to deploying Data Governance agents:
This table lists the methods that can be used to deploy Data Governance agents.
Note: As of Data Governance Edition version 7.0.2, manually deploying agents is NOT allowed. You must use the Manager client to deploy and configure Data Governance agents because you need access to the Data Governance application roles within One Identity Manager.
Table 15: Agent deployment methods
| Manager - single agent deployment |
The recommended method for adding a managed host.
- Select the host computer from the Managed host view (must have already been synchronized into One Identity Manager).
- Select the Manage host task.
- In the Managed Host Setting dialog, select the managed host configuration settings.
Use the Managed DFS host task to add a Distributed File System (DFS) root managed host.
Use the Manage NFS host task to add an NFS managed host for scanning supported NAS devices with NFS file system protocol enabled.
Use the Manage Cloud host task to add a SharePoint Online or OneDrive for Business managed host. |
For more information on determining the type of agent to be deployed, see Working with managed hosts and agents.
For more information on deploying the different types of managed hosts, see Adding and configuring managed hosts.
For more information about the configuration settings available, see Managed host configuration settings. |
| Manager - multiple agent deployment |
Use to add and configure multiple managed hosts at once.
- Select multiple host computers of the same host type from the Managed host view.
- Select the Manage multiple hosts task.
- Set the appropriate managed host configuration settings that will be applied to all selected hosts.
|
Not available for adding SharePoint managed hosts.
Does not apply to DFS, NFS, or Cloud host types (you do not select host computers when adding these types of managed hosts).
The server deploys the agents in a staggered manner.
All hosts must be in managed domains.
For more information on adding or configuring managed hosts, see Adding and configuring managed hosts. |
| Windows PowerShell |
Use the following PowerShell cmdlets in the OneIdentity.DataGovernance snap-in to deploy and configure managed hosts:
- Add-QManagedHostByAccountName: To add a managed host to your deployment and configure its settings.
- Set-QManagedHostProperties: To change the properties of a managed host.
- Set-QAgentConfiguration: To set the managed paths to be scanned.
|
These PowerShell cmdlets do not support adding Cloud managed hosts or setting managed paths for Cloud managed hosts.
For more detailed information on using Windows PowerShell to manage your agent deployment, see the One Identity Manager Data Governance Edition Technical Insight Guide. |
Different types of managed hosts behave differently. The following sections provide the steps to configure each type of managed host.
You can add the following host computers as a managed host to your Data Governance Edition deployment:
- Local Windows computer. For more information, see Adding a local managed host (Windows computer).
- Windows Cluster/Remote Windows computer. For more information, see Adding a Windows cluster / Windows computer as a remote managed host.
- Generic resource (that is, a Server Message Block (SMB) share running on any Active Directory joined computer). For more information, see Adding a generic managed host.
- Distributed File System (DFS) root. For more information, see Adding a Distributed File System (DFS) root managed host.
- SharePoint farm. For more information, see Adding a SharePoint farm managed host.
- EMC storage device with CIFS file system protocol enabled. For more information, see Adding an EMC CIFS device as a managed host.
- NetApp 7-Mode filer with CIFS file system protocol enabled. For more information, see Adding a NetApp CIFS device as a managed host.
- NetApp Cluster-Mode filer with CIFS file system protocol enabled. For more information, see Adding a NetApp CIFS device as a managed host.
- EMC Isilon storage device with NFS system protocol enabled. For more information, see Adding an NFS managed host.
- NetApp 7-Mode filer with NFS file system protocol enabled. For more information, see Adding an NFS managed host.
- NetApp Cluster-Mode filer with NFS file system protocol enabled. For more information, see Adding an NFS managed host.
- SharePoint Online resources. For more information, see Adding a cloud managed host.
- OneDrive for Business resources. For more information, see Adding a cloud managed host.
Related Topics
Managed host configuration settings
