Chat now with support
Chat with Support

Identity Manager Data Governance Edition 8.1.1 - Deployment Guide

Introduction Data Governance Edition system requirements Install One Identity Manager Data Governance Edition Deploy Data Governance Edition components Post installation configuration Authentication using service accounts and managed domains Working with managed hosts and agents Upgrade Data Governance Edition Remove Data Governance Edition Troubleshooting Appendix: NetApp managed host deployment Appendix: EMC managed host deployment Appendix: SharePoint managed host deployment

Adding a Windows cluster / Windows computer as a remote managed host

You can add Windows servers and Windows clusters as managed hosts, with remote agents. However, you cannot collect resource activity for these types of remote managed hosts.

Note: Only Windows failover cluster configurations are supported.

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

To add a Windows cluster or Windows computer managed host with a remote agent

  1. In the Navigation view, select Data Governance | Managed hosts.
  2. In the Managed hosts view (right pane), select a host with the status of Not Managed and a host type of Windows Computer.
  3. 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.

  4. 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 on the Managed hosts view.
    2. Host Type: Select Windows Cluster / Remote Windows Computer.
    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.
  5. 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.

  6. 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.

  7. 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. Use the check boxes 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.

  8. 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 a generic managed host

You can remotely scan managed hosts (other than those on the supported list) by adding a “generic” managed host. This type of managed host supports scheduled scans only and does not support real-time security updates or resource activity collection.

Note: These hosts must be accessible through Windows shares. To determine if a host can be scanned for security information, you can use the Filesystem Statistics Utility (QAM.Server.FileSystemStatistics.exe) that is included with a Data Governance Edition installation. It scans a file system, enumerates its contents, and provides statistics on the files and folders contained on the specified data roots.

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

To add a generic managed host

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

    NOTE: If you do not see the host you want to manage listed, edit the Data Governance service configuration file (DataGovernanceEdition.Service.exe.config) as follows:

    • Locate the customHostParameters section.

      <customHostParameters>

          <additionalOperatingSystems>

              <!--<operatingSystem value="MyOperatingSystem"/>-->

          </additionalOperatingSystems>

      </customHostParameters>

    • Remove the commented operatingSystem line and replace it with a line that specifies the operating system value for the host you want to manage. That is, the string found in the ADSMachine.OperatingSystem field. For example, if the host you want to manage has the operating system field "MyOS", edit this setting as follows:

      <customHostParameters>

          <additionalOperatingSystems>

              <operatingSystem value="MyOS"/>

          </additionalOperatingSystems>

      </customHostParameters>

      This will include all machines that contain the string "MyOS" in its operating system field.

    • If you want to specify an exact match, include the isExact parameter as follows:

      <customHostParameters>

          <additionalOperatingSystems>

              <operatingSystem value="MyOS" isExact="true"/>

          </additionalOperatingSystems>

      </customHostParameters>

    All of the hosts found using this filter will now appear in the Managed Host view as Unknown host type.

  2. In the Managed hosts view (right pane), select a host with the status of Not Managed and a host type of Unknown.
  3. 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.

  4. 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: Select Generic Host Type.
    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 Server installation directory (%ProgramFiles%\One Identity\One Identity Manager Data Governance Edition\Agent Services).

      If there is an existing agent, you cannot install another agent with a different installation directory. All agents must be installed in the same directory.

    4. Keywords: (Optional) Enter a keyword which can be displayed and used to group managed hosts in the Managed hosts view.
  5. 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.

  6. 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, including those that are excluded, appear on the Managed Paths page.

    For more information, see Managed paths page.

  7. 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 check boxes 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.

  8. 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 a Distributed File System (DFS) root managed host

Adding a DFS root enables you to view and manage the access on resources that are physically distributed throughout your network.

TIP: As of Data Governance Edition version 7.0.1, you can perform additional managed host tasks against DFS links, such as:

  • Target existing reports, including the Resource Access and Resource Activity reports
  • Calculate perceived owners
  • Place a DFS link under governance; adding the DFS link to the Governed data view and making the usual menu options available
  • Publish a DFS link to the IT Shop; making it available to others through a resource access request

Once added, the Data Governance server periodically synchronizes the DFS structure into the One Identity Manager database making the DFS path available within the Resource browser. You are able to quickly see where all the data has been replicated throughout your network.

This information is also available within the resource access, resource activity, and account activity reports if the underlying resource is being scanned on another activity enabled host.

NOTE: In order for a DFS link, target share path or folder to be placed under governance or published to the IT Shop, both the DFS server hosting the DFS namespace and the share server where the DFS link is pointing to must be added as managed hosts. If the required servers (those that contain DFS security details) are not already managed, a message box appears listing the servers that need to be added as managed hosts. Click the Add managed hosts with default options button to deploy a local agent to the servers listed in the message box and complete the selected operation. Click Cancel to cancel the selected operation and manually add the servers as managed hosts.

Note: By default, the Data Governance server synchronizes DFS every 24 hours, you can force an immediate synchronization using Windows PowerShell or you can alter the synchronization interval through a configuration file setting.

To force an immediate DFS synchronization, run the following PowerShell cmdlet:

Trigger-QDfsSync [-ManagedHostID] <String> [<CommonParameters>]

You must specify the ID (GUID format) of the DFS managed host to be synchronized. To synchronize all of your DFS managed hosts, set the -ManagedHostId to All.

To change the default synchronization interval, add or modify the following setting in DataGovernanceEdition.Service.exe.config file (which is located in the Data Governance server installation directory):

<add key="DFSDataSyncInterval" value="1440"/>

The value specified is interpreted as minutes. If this value is not present, the default is 24 hours.

To add a DFS root managed host

  1. In the Navigation view, select Data Governance | Managed hosts.
  2. From the Managed hosts view (right pane), select Manage DFS host from the Tasks view or right-click menu.
  3. In the DFS Managed Host Settings dialog, select the following information:

    • DFS Domain: Select the DFS domain.
    • DFS Root: Click the Select Root button to display a list of available DFS roots within the selected domain. Select a root from the list and click OK.

    Click OK to save your selections and close the dialog.

  4. Back in the Manager, click the Save toolbar button to add the DFS root managed host.

Adding a SharePoint managed host

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.

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

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

    The Managed Host Settings dialog appears.

  4. 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.
  5. 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.

  6. Click the OK button at the bottom of the Managed Host Settings dialog to save your selections and deploy the managed host.
  7. 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.

  8. 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.

  9. 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.

  10. 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.

  11. 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.

Related Documents