Identity Manager Data Governance Edition 9.1

SharePoint farms are similar to remote managed hosts in that they require an associated service account, even though they are installed locally on a SharePoint server. You have the option of selectively including and excluding objects to be scanned by one or more agent services on the SharePoint server.

NOTE: Before adding a SharePoint managed host, ensure that the following configuration steps have been completed:

Install a One Identity Manager service (job server) on a dedicated SharePoint Application Server in the SharePoint farms to be monitored. Ensure that the One Identity Manager service account is running as the SharePoint farm account (same account that is used to run the SharePoint timer service).
On the Data Governance server, run the One Identity Manager Synchronization Editor to set up a synchronization project to load your Active Directory objects into the One Identity Manager database. For more information, see the One Identity Manager Administration Guide for Connecting to Active Directory.
On the SharePoint farm server, run the One Identity Manager Synchronization Editor to set up a synchronization project to load your SharePoint objects into the One Identity Manager database. For more information, see the One Identity Manager Administration Guide for Connecting to SharePoint.
Also, check/configure the master data (task in Manager) for the service account.

Once the SharePoint synchronization project has completed, the Managed hosts view is updated to include any SharePoint farms that are available for scanning.

To add a SharePoint farm as a managed host

In the Navigation view, select Data Governance | Managed hosts.
In the Managed hosts view (right pane), select a host with the status of Not Managed and a host type of SharePoint Farm.
Select Manage host from the Tasks view or right-click menu.

The Managed Host Settings dialog appears.
At the top of the Managed Host Settings dialog, specify the following information:
1. Managed Host: This is a read-only field displaying the name of the host computer selected in the Managed hosts view.
2. Host Type: This is a read-only field displaying the type of host computer selected in the Managed hosts view.
3. Agent Install Path: (Optional) Use this field to specify an alternate installation location. This must be a local path (for example, C:\MyPath) and cannot exceed 512 characters.
  
  NOTE: By default, this field displays Use default install directory and the agent is installed in the Data Governance agent services installation directory (%ProgramFiles%\One Identity\One Identity Manager Data Governance Edition\Agent Services).
4. Keywords: (Optional) Enter a keyword which can be displayed and used to group managed hosts in the Managed hosts view.
Use the Agents page to select the service account to be used to access the SharePoint farm and the agent services to be used to scan the SharePoint farm.

To add an agent service:
1. Open the Agents page.
2. Agent Service Account: Select the service account that has the required rights for the selected SharePoint farm.
  
  The service account must be the SharePoint farm account (same account that is used to run the SharePoint timer service and the One Identity Manager service (job server)). The SharePoint farm account also needs to be added to the local Administrators group on the SharePoint server.
3. Click the Add button to add the agent service to the agents list.
  
  Repeat to add additional agent services to be used to scan the selected SharePoint farm.
  
  For more information, see Agents page.
Click the OK button at the bottom of the Managed Host Settings dialog to save your selections and deploy the managed host.
Back on the Managed hosts view, select the newly deployed SharePoint managed host, and select the Edit host settings task or right-click command.

The Managed Host Settings dialog appears allowing you to configure the additional settings required for a SharePoint managed host.
Use the Managed Paths page to specify the point within your SharePoint farm hierarchy to begin scanning.

To add managed paths:
1. Open the Managed Paths page.
2. Click the Add button.
3. In the Managed Paths Picker dialog, click the check box to the left of the component within your SharePoint farm hierarchy to be scanned.
  
  NOTE: When using multiple agent services to monitor a SharePoint managed host, select the managed path to be monitored and then select an agent service from the Agent Selection drop-down menu. Repeat this process for all of the paths to be monitored. An agent service can monitor multiple paths; however, multiple agent services cannot monitor the same managed paths. The Scanning Agent field in the Managed Paths Selection grid displays the name of the agent service selected to scan the different paths.
4. Click OK to save your selections and close the dialog.
The selected paths and assigned agent service are displayed on the Managed Paths page.

For more information, see Managed paths page.
By default, SharePoint agents scan daily at 2:00 A.M. Use the Security Scanning page to set the time and frequency with which the agent scans the target computer.

To modify the scanning schedule and settings:
1. Open the Security Scanning page.
2. Use the controls in the Scanning Schedule pane to define the time and frequency of the agent scans.
3. Use the options at the bottom of the page to modify the default security scanning behavior:
  - Immediately scan on agent restart or when managed paths change: Select this check box to perform a full scan whenever the agent restarts or there are changes made to the managed paths.
  - Ignore all files and only store folder security data: Clear this check box if you want to include file security data in the security index.
For more information, see Security Scanning page.
By default resource activity is not collected. Use the Resource Activity page to enable and configure resource activity collection and aggregation.

Note: To gather and report on resource activity in SharePoint, ensure that SharePoint native auditing is configured for any resources of interest. For more information, see Configure SharePoint to track resource activity.

IMPORTANT: Collecting resource activity on your managed hosts impacts network usage and increases the load on the database server and Data Governance server, especially when collecting activity on large busy servers. Configuring the proper exclusions and aggregation window is important to limit some of this load. Carefully plan out which resources you want to collect activity on and enable resource activity collection only on those resources.

To configure resource activity collection and aggregation:
1. Open the Resource Activity page.
2. Select the Collect and aggregate events option.
3. Select the type of events to be collected:
  - Security change
  - Create
  - Delete
  - Rename
  - Write
  - Read (disabled by default)
4. Use the Aggregation control to set the time frame to be used to consolidate similar events. Valid aggregation intervals are:
  - 5 minutes
  - 1 hour
  - 8 hours (default)
  - 1 day
5. By default, certain well-known accounts are excluded from the resource activity collection. To modify the exclusion list, click the Resource Activity Exclusions button to specify the accounts to be excluded.
  
  Note: The agent service account is not included in this exclusion list by default. You will need to add that manually for SharePoint managed hosts.
For more information, see Resource activity page.
Click the OK button at the bottom of the Managed Host Settings dialog to save your selections.

Scanning of the specified managed paths begins on the configured schedule. Once the managed host is successfully added (Status is Managed), you are able to see and manage security information for the SharePoint resources on the target managed host using the Resource browser. Double-click the managed host in the Managed hosts view to display the Resource browser.

Adding a NetApp CIFS device as a managed host

You can add supported NetApp storage devices as managed hosts, with remote agents. This procedure covers NetApp 7-Mode devices and NetApp Cluster-Mode devices running OnTap with the CIFS file system protocol enabled. See NetApp managed host deployment before adding a NetApp managed host.

NOTE: You can configure one target host computer at a time or multiple host computers (of the same type) at once.

To add a NetApp CIFS device as a managed host

In the Navigation view, select Data Governance | Managed hosts.
In the Managed hosts view (right pane), select a host with the status of Not Managed and a host type of NetApp OnTap 7 Mode CIFS Device or NetApp OnTap Cluster Mode CIFS Device.
Select Manage host from the Tasks view or right-click menu.

NOTE: If you selected multiple host computers with the status of Not Managed and of the same host type, use the Manage multiple hosts task or right-click menu command. The settings specified on the Managed Host Settings dialog will apply to all selected host computers.

The Managed Host Settings dialog appears.

NOTE: If you select a host computer on a domain that was not previously identified as a managed domain, the Domain Credentials dialog appears. Click the Set button to supply the credentials of an Active Directory user with administrative rights on the selected domain. Assigning the credentials for the domain registers the user as a Data Governance Edition service account, links the service account to the domain and adds it to the managed domains list.

Once the domain credentials are set, the Managed Host Settings dialog appears.
At the top of the Managed Host Settings dialog, specify the following information:
1. Managed Host: This is a read-only field displaying the name of the host computer selected in the Managed hosts view.
2. Host Type: This is a read-only field displaying the type of host computer selected in the Managed hosts view.
3. Agent Install Path: (Optional) Use this field to specify an alternate installation location. This must be a local path (for example, C:\MyPath) and cannot exceed 512 characters.
  
  NOTE: By default, this field displays Use default install directory and the agent is installed in the Data Governance agent services installation directory (%ProgramFiles%\One Identity\One Identity Manager Data Governance Edition\Agent Services).
4. Keyword: (Optional) Enter a keyword which can be displayed and used to group managed hosts in the Managed hosts view.
For NetApp OnTap Cluster Mode CIFS managed hosts, use the Credentials page to enter the credentials of a user with access to the target NAS host computer:
1. User Name: Enter the name of a user account with access to the target NAS host computer.
  
  Note: The user must have the "ontapi" User Login Method application.
2. Password: Enter the password associated with the user account entered above.
3. Port: Enter the destination port to be used for communication between the agent and target NAS host computer. The default value is 443.
4. Host EndPoint: (Optional) Enter the API endpoint (FQDN, host name or IP address) for the NetApp Cluster Mode connection.
  
  NOTE: The default is to use the FQDN of the targeted host. You would only use this setting if the API connection needs to be specified as something other than the FQDN of the targeted host.
5. Click the Test API Credentials button to verify valid credentials have been entered.
Use the Agents page to select the remote agent and service account to be used to scan the target host.

To add a remote agent:
1. Open the Agents page.
2. Select the agent: Select the agent host computer to be used to scan the target computer.
3. Select the service account: Select a service account with sufficient permissions to access the target computer and the agent host.
  
  An agent requires a service account that has the rights to read security information on the remote host. Only previously configured service accounts that are registered with Data Governance Edition are available for selection. For more information, see Readying a service account and domains for deployment.
4. Click the Add button to add the agent to the agents list.
  
  TIP: For remote managed hosts, add only one remote agent during the host's initial deployment. You can add additional remote agents later using the Edit host settings task after the managed host is deployed.
  
  For more information, see Agents page.
Use the Managed Paths page to specify the roots of the NTFS directory tree to be scanned by the agent.

To add managed paths:
1. Open the Managed Paths page.
2. Click the Add button.
3. In the Managed Paths Picker dialog, click the check box to the left of a directory to add it to the managed paths list.
  
  NOTE: When using multiple agents to monitor a remote managed host, select the managed path to be monitored and then select an agent from the Agent Selection drop-down menu. Repeat this process for all paths to be monitored. An agent can monitor multiple paths; however, multiple agents cannot monitor the same managed paths. The Scanning Agent field in the Managed Paths Selection grid displays the agent selected to scan the different paths.
4. Click OK to save your selections and close the dialog.
The selected paths appear on the Managed Paths page.

For more information, see Managed paths page.
By default, remote agents scan daily at 2:00 A.M. Use the Security Scanning page to change the time and frequency with which the agent scans the target computer.

To modify the scanning schedule and settings:
1. Open the Security Scanning page.
2. Use the controls in the Scanning Schedule pane to define the time and frequency of the agent scans.
3. Use the options at the bottom of the page to modify the default security scanning behavior:
  - Immediately scan on agent restart or when managed paths change: Select this check box to perform a full scan whenever the agent restarts or there are changes made to the managed paths.
  - Ignore all files and only store folder security data: Clear this check box if you want to include file security data in the security index.
  - Collect activity for real-time security updates: Select this check box to watch for changes to the structure and security of the file system on the target managed host and apply them to the scanned data.
For more information, see Security Scanning page.
By default, resource activity is not collected. Use the Resource Activity page to enable and configure resource activity collection on the target host.

IMPORTANT: Collecting resource activity on your managed hosts impacts network usage and increases the load on the database server and Data Governance server, especially when collecting activity on large busy servers. Configuring the proper exclusions and aggregation window is important to limit some of this load. Carefully plan out which resources you want to collect activity on and enable resource activity collection only on those resources.

To configure resource activity collection and aggregation:
1. Open the Resource Activity page.
2. Select the Collect and aggregate events option.
3. Select the type of events to be collected:
  - Security change
  - Create
  - Delete
  - Rename
  - Write
  - Read (disabled by default)
4. Use the Aggregation control to set the time frame to be used to consolidate similar events. Valid aggregation intervals are:
  - 5 minutes
  - 1 hour
  - 8 hours (default)
  - 1 day
5. By default, certain well-known system accounts, file extensions and folders are excluded from the resource activity collection. To modify the exclusion list, click the Resource Activity Exclusions button to specify the accounts and objects to be excluded.
  
  Note: By default, the Data Governance agent excludes the domain service account from activity collection and aggregation.
For more information, see Resource activity page.
Click the OK button at the bottom of the Managed Host Settings dialog to save your selections and deploy the managed host.

Scanning of the specified managed paths begins on the configured schedule. Once the managed host is successfully added (Status is Managed), you are able to see and manage security information for the folders and shares on the target managed host using the Resource browser. Double-click a managed host in the Managed hosts view to display the Resource browser.

Adding an EMC CIFS device as a managed host

You can add EMC storage devices as managed hosts, with remote agents. This procedure covers NAS devices running EMC Celerra/VNX or EMC Isilon operating systems with the CIFS file system protocol enabled. See EMC managed host deployment before adding an EMC managed host.

NOTE: You can configure one target host computer at a time or multiple host computers (of the same type) at once.

To add an EMC CIFS device as a managed host

In the Navigation view, select Data Governance | Managed hosts.
In the Managed hosts view (right pane), select a host with the status of Not Managed and a host type of EMC Celerra/VNX Device or EMC Isilon Device.
Select Manage host from the Tasks view or right-click menu.

NOTE: If you selected multiple host computers with the status of Not Managed and of the same host type, use the Manage multiple hosts task or right-click menu command. The settings specified on the Managed Host Settings dialog will apply to all selected host computers.

The Managed Host Settings dialog appears.

NOTE: If you select a host computer on a domain that was not previously identified as a managed domain, the Domain Credentials dialog appears. Click the Set button to supply the credentials of an Active Directory user with administrative rights on the selected domain. Assigning the credentials for the domain registers the user as a Data Governance Edition service account, links the service account to the domain and adds it to the managed domains list.

Once the domain credentials are set, the Managed Host Settings dialog appears.
At the top of the Managed Host Settings dialog, specify the following information:
1. Managed Host: This is a read-only field displaying the name of the host computer selected in the Managed hosts view.
2. Host Type: This is a read-only field displaying the type of host computer selected in the Managed hosts view.
3. Agent Install Path: (Optional) Use this field to specify an alternate installation location. This must be a local path (for example, C:\MyPath) and cannot exceed 512 characters.
  
  NOTE: By default, this field displays Use default install directory and the agent is installed in the Data Governance agent services installation directory (%ProgramFiles%\One Identity\One Identity Manager Data Governance Edition\Agent Services).
4. Keyword: (Optional) Enter a keyword which can be displayed and used to group managed hosts in the Managed hosts view.
Use the Agents page to select the remote agent and service account to be used to scan the target host.

To add a remote agent:
1. Open the Agents page.
2. Select the agent: Select the agent host computer to be used to scan the target computer.
3. Select the service account: Select a service account with sufficient permissions to access the target computer and the agent host.
  
  An agent requires a service account that has the rights to read security information on the remote host. Only previously configured service accounts that are registered with Data Governance Edition are available for selection. For more information, see Readying a service account and domains for deployment.
4. Click the Add button to add the agent to the agents list.
  
  TIP: For remote managed hosts, add only one remote agent during the host's initial deployment. You can add additional remote agents later using the Edit host settings task after the managed host is deployed.
  
  Note: If you are collecting resource activity (Collect and aggregate events on the Resource Activity page) or real-time security updates (Collect activity for real-time security updates on the Security Scanning page), you can only specify one agent to scan the EMC storage device.
  
  For more information, see Agents page.
Use the Managed Paths page to specify the roots of the NTFS directory trees to be scanned by the agent.

To add managed paths:
1. Open the Managed Paths page.
2. Click the Add button.
3. In the Managed Paths Picker dialog, click the check box to the left of a directory to add it to the managed paths list.
  
  NOTE: When using multiple agents to monitor a remote managed host, select the managed path to be monitored and then select an agent from the Agent Selection drop-down menu. Repeat this process for all paths to be monitored. An agent can monitor multiple paths; however, multiple agents cannot monitor the same managed paths. The Scanning Agent field in the Managed Paths Selection grid displays the agent selected to scan the different paths.
4. Click OK to save your selections and close the dialog.
The selected paths appear on the Managed Paths page.

For more information, see Managed paths page.
By default, remote agents scan daily at 2:00 A.M. Use the Security Scanning page to change the time and frequency with which the agent scans the target computer.

To modify the scanning schedule and settings:
1. Open the Security Scanning page.
2. Use the controls in the Scanning Schedule pane to define the time and frequency of the agent scans.
3. Use the options at the bottom of the page to modify the default security scanning behavior:
  - Immediately scan on agent restart or when managed paths change: Select this check box to perform a full scan whenever the agent restarts or there are changes made to the managed paths.
  - Ignore all files and only store folder security data: Clear this check box if you want to include file security data in the security index.
  - Collect activity for real-time security updates: Select this check box to watch for changes to the structure and security of the file system on the target managed host and apply them to the scanned data.
    
    Note: If you enable Collect activity for real-time security updates, ensure your EMC device is configured for auditing.For more information, see EMC managed host deployment.
For more information, see Security Scanning page.
By default, resource activity is not collected. Use the Resource Activity page to enable and configure resource activity collection on the target host.

IMPORTANT: Collecting resource activity on your managed hosts impacts network usage and increases the load on the database server and Data Governance server, especially when collecting activity on large busy servers. Configuring the proper exclusions and aggregation window is important to limit some of this load. Carefully plan out which resources you want to collect activity on and enable resource activity collection only on those resources.

To configure resource activity collection and aggregation:
1. Open the Resource Activity page.
2. Select the Collect and aggregate events option.
3. Select the type of events to be collected:
  - Security change
  - Create
  - Delete
  - Rename
  - Write
  - Read (disabled by default)
4. Use the Aggregation control to set the time frame to be used to consolidate similar events. Valid aggregation intervals are:
  - 5 minutes
  - 1 hour
  - 8 hours (default)
  - 1 day
5. By default, certain well-known system accounts, file extensions and folders are excluded from the resource activity collection. To modify the exclusion list, click the Resource Activity Exclusions button to specify the accounts and objects to be excluded.
  
  Note: By default, the Data Governance agent excludes the domain service account from activity collection and aggregation.
Click the View/Update cepp.conf button to check the status or modify the cepp.conf file. Selecting this button displays a Logon Credentials dialog allowing you to enter the IP address or hostname and credentials of the EMC Celerra/VNX control station and select the data mover that holds the managed paths to be scanned.
- Once the cepp.conf is retrieved and displayed, you can edit the Proposed cepp.conf file (lower pane). Select the Update File button to save your edits, which will be sent to the EMC device.
  
  Note: The cepp service will be stopped and restarted for the selected data mover to apply the new cepp.conf file.
- Use the Check Status button to check the status of the current cepp.conf file.
For more information, see Resource activity page.
Click the OK button at the bottom of the Managed Host Settings dialog to save your selections and deploy the managed host.

Scanning of the specified managed paths begins on the configured schedule. Once the managed host is successfully added (Status is Managed), you are able to see and manage security information for the folders and shares on the target managed host using the Resource browser. Double-click a managed host in the Managed hosts view to display the Resource browser.

Adding an NFS managed host

Data Governance Edition supports the scanning of NAS devices with NFS file system protocol enabled, including NetApp 7-Mode, NetApp Cluster and EMC Isilon devices.

NOTE: Before adding an NFS managed host, ensure the following configuration steps have been completed:

During the One Identity Manager installation process and Data Governance configuration process, add the optional Unix module.
During the One Identity Manager Data Governance Edition installation process, ensure the One Identity Manager service (job server) is configured properly and that the UNIX connector server function is selected.
Run the One Identity Manager Synchronization Editor to set up a synchronization project to load your UNIX objects into the One Identity Manager database.

For EMC Isilon NFS managed hosts:

On the Data Governance server and all agent servers, you must have a Trusted Root Certificate Authority certificate to validate the Isilon server's HTTP certificate. See the EMC Isilon Web Administration Guide for details.
The service account for an agent managing EMC Isilon storage devices, must have "run as root" permissions on the Isilon SMB share to be managed (that is, selected as a managed path).

For NetApp 7-Mode NFS managed hosts (does NOT apply to Cluster Mode devices):

The service account for an agent managing NetApp 7-Mode filers must be a member of the local Administrators group on the NetApp filer in order to create FPolicy. This account must also have permissions to access folders being scanned.
Monitoring real-time security updates and collecting resource activity requires FPolicy; and in order to use FPolicy, the CIFS file system protocol must be enabled for NetApp 7-Mode devices.

Adding a NFS managed host

In the Navigation view, select Data Governance | Managed hosts.
From the Managed hosts view, select Manage NFS host from the Tasks view or right-click menu.

The Managed Host Settings dialog appears.
At the top of the dialog, specify the following information:
1. Managed Host: Enter the IP address or the fully qualified domain name of the NFS host computer to be managed.
2. Host Type: Select NetApp Cluster NFS Device, NetApp 7-Mode NFS Device, or EMC Isilon NFS Device.
3. Agent Install Path: (Optional) Use this field to specify an alternate installation location. This must be a local path (for example, C:\MyPath) and cannot exceed 512 characters.
  
  Note: By default, this field displays Use default install directory and the agent is installed in the Data Governance agent services installation directory (%ProgramFiles%\One Identity\One Identity Manager Data Governance Edition\Agent Services).
4. Keywords: (Optional) Enter a keyword which can be displayed and used to group managed hosts in the Managed hosts view.
Open the NIS Host page to specify the NIS server whose users and groups have been synchronized with One Identity Manager.
Open the Credentials page and enter the credentials of a user with access to the target NAS host computer:
1. User Name: Enter the name of a user account with access to the target NAS host computer.
2. Password: Enter the password associated with the user account entered above.
3. Port: Enter the destination port to be used for communication between the agent and target NAS host computer.
  - NetApp filers: The default value is 443.
  - EMC devices: The default value is 8080.
Click the Test API Credentials button to verify valid credentials have been entered.

For more information, see Credentials page.
Use the Agents page to select the remote agent and service account to be used to scan the target host.

To add a remote agent:
1. Open the Agents page.
2. Select the agent: Select the agent host computer to be used to scan the target computer.
3. Select the service account: Select a service account with sufficient permissions on the selected agent host.
  
  Only previously configured service accounts that are registered with Data Governance Edition are available for selection. For more information, see Readying a service account and domains for deployment.
4. Click Add to add the agent to the agents list.
  
  TIP: For remote managed hosts, add only one remote agent during the host's initial deployment. You can add additional remote agents later using the Edit host settings task after the managed host is deployed.
For more information, see Agents page.
Use the Managed Paths page to specify the directories to be scanned by the agent to create and maintain the security index.

To add managed paths:
1. Open the Managed Paths page.
2. Click the Add button.
3. In the Managed Paths Picker dialog, select the check box to the left of the directories to be scanned.
  
  NOTE: When using multiple agents to monitor a remote managed host, select the managed path to be monitored and then select an agent from the Agent Selection drop-down menu. Repeat this process for all paths to be monitored. An agent can monitor multiple paths; however, multiple agents cannot monitor the same managed paths. The Scanning Agent field in the Managed Paths Selection grid displays the agent selected to scan the different paths.
4. Click OK to save your selections and close the dialog.
The selected paths appear on the Managed Paths page.

For more information, see Managed paths page.
By default, remote agents scan daily at 2:00 A.M. Use the Security Scanning tab to change the time and frequency with which the agent scans the target computer.

To modify the scanning schedule and settings:
1. Open the Security Scanning page.
2. Use the controls in the Scanning Schedule pane to define the time and frequency of the agent scans.
3. Review the options at the bottom of the page to modify the default security scanning behavior:
  - Immediately scan on agent restart or when managed paths change: Select this check box to perform a full scan whenever the agent restarts or there are changes made to the managed paths.
  - Collect activity for real-time security updates: Select this check box to watch for changes to the structure and security of the file system on the target managed host and apply them to the scanned data.
    
    Note: Collecting real-time security updates is not available for EMC Isilon NFS devices.
    
    NOTE: For NetApp 7-Mode managed hosts, real-time security updates and resource activity collection requires FPolicy. In order to use FPolicy, CIFS file system protocol must be enabled.
For more information, see Security Scanning page.
By default, resource activity is not collected. Use the Resource Activity page to enable and configure resource activity collection on the target host.

IMPORTANT: Collecting resource activity on your managed hosts impacts network usage and increases the load on the database server and Data Governance server, especially when collecting activity on large busy servers. Configuring the proper exclusions and aggregation window is important to limit some of this load. Carefully plan out which resources you want to collect activity on and enable resource activity collection only on those resources.

Note: Collecting resource activity is not available for EMC Isilon NFS devices.

To enable and configure resource activity collection and aggregation:
1. Open the Resource Activity page.
2. Select the Collect and aggregate events option.
3. Select the type of events to be collected:
  - Security change
  - Create
  - Delete
  - Rename
  - Write
  - Read (disabled by default)
4. Use the Aggregation control to set the time frame to be used to consolidate similar events. Valid aggregation intervals are:
  - 5 minutes
  - 1 hour
  - 8 hours (default)
  - 1 day
5. By default, certain file extensions and folders are excluded from the resource activity collection. To modify the exclusion list, click the Resource Activity Exclusions button to specify the objects to be excluded.
For more information, see Resource activity page.
Click the OK button at the bottom of the Managed Host Settings dialog to save your selections and deploy the managed host.

Scanning of the specified managed paths begins on the configured schedule. Once the managed host is successfully added (Status is Managed), you are able to see and manage security information for the folders and shares on the target managed host using the Resource browser. Double-click a managed host in the Managed hosts view to display the Resource browser.

Identity Manager Data Governance Edition 9.1 - Deployment Guide

Adding a SharePoint farm managed host

Adding a NetApp CIFS device as a managed host

Adding an EMC CIFS device as a managed host

Adding an NFS managed host

Selecione seu produto:

Para podermos atendê-lo melhor, informe o Propósito de seu chat:

Soluções recomendadas para seu problema

Identity Manager Data Governance Edition 9.1 - Deployment Guide

Adding a SharePoint farm managed host

Adding a NetApp CIFS device as a managed host

Adding an EMC CIFS device as a managed host

Adding an NFS managed host