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.
Table 76: Mapping Data Governance events to native SharePoint events
| Create |
Undelete
Item copied
Item added |
| Delete |
Item deleted |
| Rename |
Item restored from Recycle Bin |
| Read |
Checkout
View |
| Security Change |
Audit mask change
Inheritance breakage
Inheritance restore
Permission level granted
Permission level revoked |
| Write |
Item checked in
Item moved
Item renamed
Item updated
Version deletion
Version restored
Item updated
Attachment added |
This appendixprovides 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.
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.
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:
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".
-
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.
Note: Run the Set-QServiceConnection command before you can use any of the Data Governance Edition commands.
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
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:
Set-ExecutionPolicy RemoteSigned
Then, type the following at the Windows PowerShell command prompt to confirm that the execution policy has been changed:
Get-ExecutionPolicy RemoteSigned
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
To determine the service account or managed domain ID
To determine the deployment name
