Enterprise Vault™ Classification using the Microsoft File Classification Infrastructure
- About this guide
- Getting started
- How Enterprise Vault caches the items that it submits for classification
- Setting up the classification properties
- Configuring your classification rules
- Defining and applying classification policies
- Running classification in test mode
- Publishing classification properties and rules across your site
- Using classification with smart partitions
- Appendix A. Enterprise Vault properties for use in classification rules
- Appendix B. PowerShell cmdlets for use with classification
- Appendix C. Monitoring and troubleshooting
How to publish the classification properties and rules
When you are satisfied that your classification properties and rules work as expected, you can publish them to the other storage servers in your Enterprise Vault environment. To do this, run the PowerShell cmdlet Import-EVClassificationFCIRules or Publish-EVClassificationFCIRules.
These two cmdlets perform a similar function. The difference is that Publish-EVClassificationFCIRules first exports the classification properties and rules to an XML file before it publishes them to the target servers; Import-EVClassificationFCIRules uses an existing XML file to perform the import part of the operation only.
For example, the following exports the classification properties and rules to the file
RulesFile.xml, which it then publishes to all the Enterprise Vault servers in the specified site:
Publish-EVClassificationFCIRules -StagingServer SERVERXYZ -ExportRulesPath c:\Data\RulesFile.xml -SiteId 13E...EV.example.com
Other methods for publishing the classification properties and rules are available, such as running the PowerShell cmdlets that come with the Microsoft Data Classification Toolkit. However, these methods do not automatically turn off the Enterprise Vault Storage services on the target servers while they install the new classification properties and rules. As this can lead to classification errors, we recommend that you use the Enterprise Vault classification cmdlets instead. These cmdlets do stop the Storage service before they begin the installation, and then restart it afterwards.