Map SharePoint events to Data Governance events

When you track resource activity using Data Governance Edition, the results appear in views, reports, and dashboards. To simplify things, SharePoint events are grouped for easier reporting. The following table outlines the events you see in your reports, and the corresponding SharePoint events.

Appendix: PowerShell commands

Appendix: PowerShell commands

This appendix provides a list of the Windows PowerShell commands available to deploy and configure Data Governance Edition components and administer Data Governance Edition to manage the unstructured data in your organization.

• Adding the PowerShell snap-ins
• Finding component IDs
• Data Governance Edition deployment
• Service account management
• Managed domain deployment
• Agent deployment
• Managed host deployment
• Account access management
• Resource access management
• Governed data management
• Classification management

For full parameter details and examples, see the command help or the One Identity Manager Data Governance Edition Technical Insight Guide. For a list and full parameter details and examples of the PowerShell commands available for creating and maintaining managed resources (such as, file shares created through the IT Shop self-service request functionality), see the One Identity Manager Data Governance Edition IT Shop Resource Access Requests User Guide.

Adding the PowerShell snap-ins

Data Governance Edition comes with a Windows PowerShell snap-in for you to use to manage your environment.

If you installed Windows PowerShell on your computer after you installed the Data Governance server, you must register the cmdlets before you can start using them in Windows PowerShell.

To import the Data Governance Edition PowerShell module

1. Open a Windows PowerShell window and type the following at the Windows PowerShell command prompt:

   Import-Module "<path>"

   Where <path> is the file path for the QAM.Client.PowerShell.dll assembly. By default, the <path> for the Data Governance server machine is "C:\Program Files\One Identity\One Identity Manager\QAM.Client.PowerShell.dll".

2. To verify that the module was added, type the following at the Windows PowerShell command prompt:

   Get-Module -All

   The registered PowerShell modules are listed.

Adding the module automatically to new sessions

If you do not want to manually add the Data Governance Edition PowerShell module each time you start a new Windows PowerShell session, you can modify the Windows PowerShell profile file so that it is added automatically for you.

To add the Data Governance Edition PowerShell module automatically when you start a new Windows PowerShell session

• Add the following line to the Windows PowerShell profile file (profile.ps1) file:

  Import-Module "<path>"

  The location of the Windows PowerShell profile file is as follows: WINDOWS\system32\windowspowershell\v1.0

Finding component IDs

Many of the Windows PowerShell commands you can use to manipulate your deployment require that you know the component’s ID.

To determine the managed host, container parent, container, resource node, or agent ID

• Run the Get-QManagedHosts command.

To determine the service account or managed domain ID

• Run the Get-QManagedDomains command.

To determine the deployment name

• Run the Get-QDeploymentInfo command.