Enterprise Vault 12.3 ReadMeFirstVeritas Enterprise Vault™ 12.3ReadMeFirstLast updated: 5-Apr-2018The latest version of this document is available from the Veritas Supportwebsite at.For the latest news about this release, including any hotfixes, subscribeto.This document describes the new features in Veritas Enterprise Vault 12.3.If you are performing a new installation of Enterprise Vault, follow the installation instructions in the Enterprise Vault Installing and Configuring guide. If you are upgrading, follow the instructions in Upgrade Instructions.
![]()
These guides are in the Veritas Enterprise VaultDocumentationEnglishAdministration Guides folder on the Enterprise Vault media. Contents. New features in Enterprise Vault 12.3. Changes in Enterprise Vault 12.3.New features in Enterprise Vault 12.3Enterprise Vault 12.3 includes the following new features.
If Outlook 2016 was installed on the Enterprise Vault server, the SearchFolderManager tool failed to process any mailbox. This has been fixed. Journaling failed to process messages from users with an apostrophe in their email alias CFT-568.
For information about the new features in earlier releases, see the release notes for,. Changes in Enterprise Vault 12.3 Changes to prerequisite software for Enterprise Vault 12.3There are no changes to prerequisite software since Enterprise Vault 12.The Enterprise Vault installer requires Microsoft.NET Framework 4.5.2, andall Enterprise Vault servers require both Microsoft.NET Framework 4.5.2 and.NET Framework 3.5 SP1.For full details of all supported versions of software and devices, see the EnterpriseVault.Appendix A provides details of the versions of software that have been dropped since Enterprise Vault 11.0. Support for Outlook 2016 on the Enterprise Vault serverArchiving from Exchange public folders is now supported with Outlook 2016 on the Enterprise Vault server.Testing has shown that performance of public folder archiving is affected if Outlook 2016 is installed on the Enterprise Vault server. If you are already using Outlook 2013, we recommend that you continue to use it on the Enterprise Vault server.If you choose to install Outlook 2016, you may need to configure legacy (Exchange 2010 or earlier) public folders so that users whose mailboxes are on Exchange Server 2013/2016 can access them.
See the following Microsoft article for instructions:Note the following:. Enterprise Vault supports Outlook 2016 (32-bit version).
Enterprise Vault supports the Windows Installer (.msi) package, which is available with the volume license. The following versions of Outlook 2016 are not supported:. Outlook 2016 (64-bit version). Outlook 2016 (Click-to-Run version).
Connections to Exchange 2010 with Outlook 2016 are not supported. If you want to use Exchange 2010, you must use Outlook 2013. Outlook 2016 supports Exchange 2013 and 2016 connections, but only using MAPI over HTTP. Outlook Anywhere and RPC are not supported connection methods.New and enhanced PowerShell cmdletsIn earlier versions of Enterprise Vault, you needed to import certain modulesto use PowerShell cmdlets that the Enterprise Vault Management Shell did not automaticallyload. For example, you needed to import the module Symantec.EnterpriseVault.PowerShell.Monitoring.dllto make available cmdlets like Get-EVServiceState and Get-EVTaskState.
Known issues and limitations Classification using Microsoft File Classification Infrastructure on Windows Server 2016 3909224Classification using the Microsoft File Classification Infrastructure is not supported on Windows Server 2016. NetBackup Agent for Enterprise Vault cannot back up data from multiple open partitions in the same vault store 3928569With the introduction of in EnterpriseVault 12.3, vault stores can now contain multiple, open vault store partitions.Previously, each vault store could contain just one open partition.The NetBackup Agent for Enterprise Vault does not currently support this enhancedfunctionality. Instead of backing up the data from every open partition in a vaultstore, the agent backs up the data from the most recently opened partition only.The other partitions are not backed up and marked as secured.This issue will be fixed in a future version of the NetBackup Agent. If you normallyuse the agent to perform backups of your Enterprise Vault data, see the Backupand Recovery guide for alternative methods to back up the data. Policy Manager scripts fail if you specify the name of the system mailbox 3941033To use the Enterprise Vault Policy Manager, you must specify the SMTP address of the Enterprise Vault system mailbox, irrespective of the version of Outlook that is installed on the Enterprise Vault server.
The script fails to run if you specify the name of the system mailbox. Files not deleted on placeholder deletion on NetApp 9.2 devices 3941424On NetApp 9.2 devices, archived files are not deleted when the placeholders are deleted. DocumentationThe Enterprise Vault media includes the Enterprise Vault documentation in all supported languages.The Enterprise Vault documentation is available in PDF and HTML format in the Veritas. Administration documentationThe Enterprise Vault administration documentation is available in English, Japanese, and Simplified Chinese from the following locations:. Veritas Enterprise VaultDocumentation folder on theEnterprise Vault media. Administration Console (click Help Help on Enterprise Vault)DocumentCommentsEnterprise Vault Documentation LibraryIncludes all the following documents in Windows Help (.chm) format so thatyou can search across them all. Legal noticeCopyright © 2018 Veritas Technologies LLC.
All rights reserved.Veritas, the Veritas Logo, Enterprise Vault, Compliance Accelerator, and DiscoveryAccelerator are trademarks or registered trademarks of Veritas Technologies LLCor its affiliates in the U.S. And other countries. Other names may be trademarksof their respective owners.This product may contain third-party software for which Veritas is required toprovide attribution to the third party ('Third-party Programs'). Some of the Third-partyPrograms are available under open source or free software licenses. The LicenseAgreement accompanying the Software does not alter any rights or obligations youmay have under those open source or free software licenses. Refer to the Third-partyLegal Notices document accompanying this Veritas product or available at:The product described in this document is distributed under licenses restrictingits use, copying, distribution, and decompilation/reverse engineering.
No part ofthis document may be reproduced in any form by any means without prior written authorizationof Veritas Technologies LLC and its licensors, if any.THE DOCUMENTATION IS PROVIDED 'AS IS' AND ALL EXPRESS OR IMPLIED CONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TOTHE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. VERITAS TECHNOLOGIESLLC SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITHTHE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.The Licensed Software and Documentation are deemed to be commercial computersoftware as defined in FAR 12.212 and subject to restricted rights as defined inFAR Section 52.227-19 'Commercial Computer Software - Restricted Rights' and DFARS227.7202, et seq. 'Commercial Computer Software and Commercial Computer SoftwareDocumentation,' as applicable, and any successor regulations, whether deliveredby Veritas as on-premises or hosted services.
Any use, modification, reproductionrelease, performance, display or disclosure of the Licensed Software and Documentationby the U.S. Government shall be solely in accordance with the terms of this Agreement.Veritas Technologies LLC500 E Middlefield RoadMountain View, CA 94043.
I'm an MSP and I've encountered a disturbing trend over the last couple of weeks among 4 different workstations at 4 different client sites.Each client is running the on-premises version of Microsoft Office 2016 Home and Business with the latest patches (automatically patched by MS). When using Microsoft Outlook 2016 with the SEP add-In enabled, Outlook will abruptly crash with a generic dialog 'Outlook has encountered a problem and is restarting'.
After some testing, it appears that this happens when entering a folder that contains a large number ( 600) of messages, although I'm not certain that is the trigger. Two of these clients have encountered this issue while entering their Deleted Items folders, while the other two encountered this issue with their Inboxes. In all cases, we can start Outlook in Safe Mode and disable the SEP add-in, then we can access the folders that caused the crash.All 4 workstations are running fully-patched versions of Windows 10 - 3 of the workstations are running the Anniversary Update (1609), 1 is running the Creators Update (1703).Of the 4 workstations, 2 are running SEP 12.1.6 MP7, 1 is running SEP 12.1.6 MP8, 1 is running SEP 12.1.6 MP9. Apparently, this is an ongoing problem that the latest update has not solved.As much as I hate to leave ANY protection disabled, it seems that disabling the SEP add-in is the ONLY way to allow these users to continue to work without issue.I'd appreciate any feedback or suggestions. We have a site location have the similar issues, but we are using notes. Well, I would say almost the same problem.just this apps crashed all the time. So for me, it is more like the notes/outlook profile setup.other locations so far doesn't have the crashed issues, and only one site and they have very specific notes setup.the workaround is either install SEP without notes/outlook protection, or rename the nlnvp.dll files.that location have a lot of users, so we go for create new package without the notes/outlook plugin, and improve our spam mail system.
![]()
Disabling the Symantec Outlook Add on is not an option. The people want to know why or how to fix the problem and they want Solutions not just disabling. You may make a request to Symantec why they provide the add on at all for anyone if it doesn’t do anything.
Think about it. Perhaps a JPEG has a virus in it before it’s opened as an email when it’s previewed in the email.
Perhaps there is a remote code execution that occurs in outlook that is not a scannable file. Perhaps there is a remote code execution that occurs in outlet that is not a scannable file. There are exploits in fonts even. I would rather have all the possible protections I can possibly get. I do not reinstall operating systems I provide solutions. There are two solutions here. One is to disable that Outlook add on. The other turn is to correct the application is causing the problem.
If you ever notice that the correction is never the update to the outlook ad on it’s always an update to the application in the case of semantic add on’s. In the past it was a very simple remove the last service pack under view installed updates and and remove programs. Having two different solutions helps you decide which one you want rather than having the only choice to disable. My point was I had two identical computers one it found fault the other it did not find fault. My further research has shown that the problem was the original office 2016 bill that I used on one was different then the office 2016 build on the other even though they were both patched to the current version and identical in every way except the initial build. That tells me that the old version created registry entries that lingered even after an update and the new installed future office 2016 did not create those registry entries which caused this issue.
The add on is looking for parameter that doesn’t exist anymore because office has changed the way that it’s built from 2015 to the year 2017 of the package called office home and business 2016.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |