Many of the PowerShell commands you can use to manipulate your taxonomies require that you know the ID of a category. You must know the parent taxonomy of the category.
To determine a taxonomy ID using PowerShell
To determine a category ID using PowerShell
To determine an extractor ID using PowerShell
The following commands in the Quest.DataGovernance snapin can be used to deploy and configure the Classification Server. It is recommended that the Manager be used for easier deployment. For full details, see the command help, using the Get-Help command.
Use this command | If you want to |
Get-QClassificationServerDeploymentOptions | Obtain the Classification default configuration settings. This must be performed before you can deploy the server. |
Get-QDeploymentInfo | View deployment information for your Data Governance Server including the deployment ID, classification server name, and the classification port. |
Deploy-QClassificationServer | Deploy the Classification Server with the required configuration settings to a specified host computer, and install it. This results in the required services running on the remote computer that process classification data and respond to queries regarding classification. |
Deploy-QClassificationWorker | Deploys a Classification worker to a specified computer. This service is responsible for processing classification data and responding to queries regarding classification. This command requires that the Classification server has been previously deployed (using the Deploy-QClassificationServer command). |
Deploy-QDefaultTaxonomies | Deploys the default taxonomies. For details on these taxonomies, see Appendix C: Classifying Data with Data Governance Templates. |
Set-QDeploymentInfo | Change the deployment parameters for the Data Governance server including the deployment ID, classification server name, and the classification port. Note: Changing this value can prevent the Data Governance service from communicating with existing agents. It is not recommended to change the deployment ID of an existing server. |
Using PowerShell you can cause an immediate re-classification of all NTFS and SharePoint data for all of the managed hosts within your environment or on only selected data.
If you have made changes to any existing rules within a taxonomy that will result in changes to how data has been previously classified. You can run this command to ensure the classification reflects the change.The ability to perform an immediate re-classification is important for manual classification of containers. In cases where classification should be inherited by child resources, the children will need to be re-processed to have this inherited classification applied.
Syntax: Request-QClassification <ServerAddress> [ManagedHostId] [Folder]
To force a re-classification of your data using PowerShell
Examples:
To re-classify all recognized data on the managed hosts in your environment, enter only the server address: Request-QClassification “server.address.com:8723”.
To re-classify all recognized data on a specific managed host, specify the host ID but not a specific folder: Request-QClassification “server.address.com:8723” “92c17163-a883-4037-a4f6-3735cfeae732”.
To re-classify the contents of a specific folder, on a specific managed host, enter all the parameters: Request-QClassification “server.address.com:8723” “92c17163-a883-4037-a4f6-3735cfeae732” “C:\ImportantDocuments”.
The following commands in the Quest.Classification and the QuestQCS snapins can be used to help troubleshoot issues with your classification server or worker deployments. For full details, see the command help, using the Get-Help command. You must load the Quest.Classification snapin and import the QuestQCS snapin to use these commands.
Use this command | If you want to |
Get-QClassificationLogs | View the logs for any of the classification services. |
Get-QWorkerServers | Get a list of the classification workers in your deployment. |
Get-QServiceInfo | View information about the classification extension installed on the Data Governance server. |
Connect-QCSClient | Connect to the Classification server. Note: The GatewayAddress parameter must be specified in the format: https://<Classification server name>:8725/gateway. You must also use the fully qualified domain name for the server. Note: You must run the Connect-QCSClient command before you can run the Get-QCSSupportBundle. |
Get-QCSSupportBundle |
Gather diagnostic information on the classification server and workers. The information includes Classification system information (such as Classification services status, Classification system configuration, event bus configuration/queue size, log files, and registered services) and Windows system information (such as environment variables, installed services, logical disk, memory cache, memory devices, network adapters, operating system, page file usage, processor information, running processes, and Windows event logs.)By default, the generated file (QCS_SupportBundle_MM-dd-yyyy_HH.mm.ss.FFFFF.zip) can be found in C:\ProgramData\Quest Software\QCS. Note: To use this command to collect system information, you must be an administrator on the classification server and workers and have rights to access the classification system (designated as the classification identity service account). Note: Remote file collection for the worker servers requires the hidden (c$) admin shares to be available. |
© 2025 One Identity LLC. ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center