Enterprise Vault™ Compatibility Charts
- About this guide
- Enterprise Vault core dependencies
- Introduction
- Operating system
- Standalone Enterprise Vault Administration Console
- Enterprise Vault API Runtime
- Microsoft SQL Server
- Clustering
- Elasticsearch index location
- .NET Framework
- Enterprise Vault Server support for Add-Ins
- Microsoft Outlook on the Enterprise Vault server
- Veritas backup agents for Enterprise Vault
- Microsoft Management Console (MMC)
- Web browsers
- System Center Operations Manager (SCOM)
- Server virtualization
- Citrix
- Cloud deployment
- Domain and forest functional levels
- FIPS 140-2 compliance
- IPv6 support
- Enterprise Vault compatibility with Microsoft Security Patches
- Hybrid Modern Authentication (HMA)
- Storage devices, appliances, and software
- Exchange archiving
- Exchange archiving client compatibility
- About Exchange archiving client compatibility
- Windows operating systems for Outlook Add-In
- Windows email clients
- Web browsers
- Browser support for Enterprise Vault Office Mail App for Exchange 2016 and Exchange 2019
- Mac client operating systems
- Mac email clients
- Mac client browsers
- Desktop search utilities
- File System Archiving (FSA)
- Domino mailbox archiving and journal archiving
- SharePoint archiving
- SMTP archiving
- Microsoft Teams Archiving
- Skype for Business Archiving
- Enterprise Vault Search
- Compliance Accelerator and Discovery Accelerator
- Supported versions of Enterprise Vault in Accelerator environments
- Audit Server
- Compatibility of Accelerator client and server components
- Compliance Accelerator
- Compliance Accelerator compatibility with Enterprise Vault
- Compliance Accelerator compatibility with other server components
- Compliance Accelerator compatibility with other client components
- Veritas Surveillance (formerly Veritas Advanced Supervision) compatibility with other server components
- Server virtualization
- Discovery Accelerator
- eDiscovery Platform
- Antivirus software
- Third-party integrations
- Localization
- Appendix A. Changes to prerequisite software for Enterprise Vault 12
- Appendix B. Changes to prerequisite software for Enterprise Vault 14
- Appendix C. Revision history
Supported Windows components
Enterprise Vault File System Archiving placeholder and file internet shortcuts have been tested with the following Windows components. If a Windows component does not appear on this list, it is advisable to perform a proof of concept validation of a production system prior to installation.
Note:
Where applicable, the support shown is based on the Enterprise Vault FSA Agent/Placeholder service and application hosted on the same file server.
Table: Supported Windows components
Item | Version | Enterprise Vault | |
12 | 14 | ||
FAT16, FAT32 | All versions | N | N |
NTFS | 2012, 2012 R2 | Y | Y |
2016, 2019 | Y [1] | Y | |
EFS (Encrypting File System) | 2012, 2012 R2 | Y | Y |
2016 | Y [1] | Y | |
2019 | P | P | |
2012, 2012 R2 | Partial | Partial | |
2016, 2019 | P | P | |
Directory Junction Points [4] | 2012, 2012 R2 | Partial | Partial |
2016, 2019 | P | P | |
Hard Links | All versions | N | N |
Symbolic Links | All versions | N | N |
Alternate Data Streams [5] | 2012, 2012 R2 | Y | Y |
2016, 2019 | P | P | |
Quotas | 2012, 2012 R2 | P | P |
2016, 2019 | P | P | |
Volume Shadow Copy | 2012, 2012 R2 | P | P |
2016 | Y [1] | Y | |
2019 | P | P | |
File Compression [6] | 2012, 2012 R2 | Partial | Partial |
2016, 2019 | P | P | |
Single Instance Storage | All versions | N | N |
Microsoft DFS Namespace [7] | 2012, 2012 R2 | Y | Y |
2016 | Y [1] | Y | |
2019 | Y [9] | Y | |
Microsoft DFS-R (RDC) [8] | 2012, 2012 R2 | Y | Y |
2016 | Y | ||
2019 | Y [9] | Y | |
Branch Cache | 2012, 2012 R2 | Y | Y |
2016 | Y [1] | Y | |
2019 | P | P | |
BitLocker | Storage Server 2012, R2 | Y | Y |
2016 | Y [1] | Y | |
2019 | P | P | |
ReFS | 2012, 2016, 2019 | N | N |
CSVFS | 2012, 2016, 2019 | N | N |
Microsoft Data Deduplication | Storage Server 2012, R2 | Y | Y |
2016 | Y [1] | Y | |
2019 | P | P | |
Storage Replica [10] | 2016 | Y [9] | Y |
2019 | P | P | |
- Requires Enterprise Vault server and FSA Agent 12.1 or later.
- A single mount point created as an Enterprise Vault volume and all its subfolders are supported. The subfolders can also be archiving targets. Neither nested mount points nor volume targets added above the mount point are supported.
- Enterprise Vault does not write files to the root of the mount point if you have logged in using the Vault Service account. You must create a folder within the mount point to hold the files.
- A single junction point created as an Enterprise Vault volume and all its subfolders are supported. The subfolders can also be archiving targets. Nested junction points are not supported.
- Enterprise Vault will retain Alternate Data Streams on Placeholders.
- An archived file that was originally compressed with Windows compression will be recalled uncompressed when accessed through FSA. The recalled file cannot be re-compressed with Windows compression due to a Microsoft limitation.
- Supports only the addition of physical file server paths hosting DFS shares as archiving targets. Does not support the addition of DFS Namespace as an archiving target. Supports access to placeholders from client computer using DFS virtual namespace. Enterprise Vault search displays the full physical file server path and not the DFS "virtual" path. For more information, see https://www.veritas.com/docs/100017525.
- Only internet shortcuts are supported. Placeholders are not supported.
- Requires Enterprise Vault 12.5
- For best practices, refer https://www.veritas.com/support/en_US/article.100048427.