Get Live Help
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.
|Data Governance events||Native SharePoint events|
Item restored from Recycle Bin
Audit mask change
Permission level granted
Permission level revoked
Item checked in
For full parameter details and examples, see the command help
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
Open a Windows PowerShell window and type the following at the Windows PowerShell command prompt:
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".
To verify that the module was added, type the following at the Windows PowerShell command prompt:
The registered PowerShell modules are listed.
Note: Run the Set-QServiceConnection command before you can use any of the Data Governance Edition commands.
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:
The location of the Windows PowerShell profile file is as follows: WINDOWS\system32\windowspowershell\v1.0
Note: If you get the error message "...profile.ps1 cannot be loaded because the execution of scripts is disabled" the next time you start a new Windows PowerShell session, type the following at the Windows PowerShell command prompt:
Then, type the following at the Windows PowerShell command prompt to confirm that the execution policy has been changed:
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.