allowed list of WSUS appliable patches
Hi, i want to start using an internal Wsus server for our clearwell servers, but i am wondering, can any Microsoft offered patch be applied? including the MS Office patches? are there certain patches that we need to exclude? If so, is there list of KB numbers that i should NOT apply to a Clearwell server? Are all MS updates tested for compatibility by Symantec? or does Symantec have a list of verified patches that are allowed to be applied?Solved1.2KViews3likes3CommentsClearwell email proxy address
Hi, We have CLearwell 7.1.4 installed in our environment and per user is havingaround 100 proxy addresses of mailbox.Now requiremnt is user wants to display his atleast 60 email proxy addresses.I can achive this requirement If I set "esa.employmentmanager.max.emails=60" under Property Browser.. Please let me know how much is recommended figure for this property and what is the maximun figure which we can set here ?474Views1like1CommentUsing Exchange throttling policies for Clearwell service account
Excuse my lack of complete understanding of Clearwell as I am an Exchange person who's being tasked with implementing Clearwell in our environment. So I now know Clearwell uses MAPI to query and collect data from the stores. I also understand the rights that the service account requires. I had a couple of questions, 1. Does the service account have to be only an AD account or does it need to be mailbox-enabled? In the sense does it require a mailbox in the Exchange environment? 2. Our concern with Clearell is primarily around the performance impact it might cause in our production Exchange 2010 environment. We are obviously going to be testing it a lot but I wanted to know if the Symantec staff has seen anyone use client throttling policies against the Clearwell service account? The throttling policies impose limits on how much resources that particular mailbox can consume in Exchange. We were considering setting some throttling policies specifically for the Clearwell service account mailbox. Thank you,Solved883Views1like3CommentsHOT OFF THE PRESS - Clearwell 7.1.3 Released
The SymantecClearwell Product Development team is proud to announce the general availability of Symantec Clearwell eDiscovery Platform V7.1.3 This new release has been in the making for one year and rounds off many features from previous releases making it the most complete release with many marquee features, the highlights of which include (but are not limited to): Identification & Collections Search and Preview of EV collections : ability to run search-only tasks against Enterprise Vault sources, preview sample files, and run date range and custodian-based analytics on the results Custodian Manager : fully-integrated Custodian Management feature using a streamlined custodian-centric workflow. Administrators not only have the ability to match the custodian manager features in Symantec’s Discovery Accelerator, but can also use new customization capabilities for the attributes that can be tracked Processing Several new reports and many others enhanced : De-duplication reports, Reconciliation report, Discovery & Processing Options reports etc. Improved Container handling : improves container extraction management by allowing users to exclude by container format for discovery Search Email Header Processing & Search : lets users search through the Internet Headers section of emails. This includes standard header fields (To, Cc, Bcc, Subject, From) and custom header fields the customer may choose to index (e.g.: X-Originating-IP, Received-By) Various reports including Excel Search Report and Search Hit Report Review Transparent Predictive Coding Graphs : presentation of prediction accuracy data by displaying the information in a graphical format. Prediction Status Enhancements : the Prediction Status screen has been enhanced with a graph of prediction accuracy over the iterations. Family Propagating Tag Set Behavior : enhancement work to support a new family propagating tag behavior for tag sets. Export & Production Features Image Remediation : better manage and control document imaging, especially for handling in other third-party tools. Slipsheet Enhancement : feature provides users with the ability to customize slipsheets for each production. An overview of the features is included in the attached document.Solved1.1KViews1like2CommentsError Installing Clearwell Confirmation Server
I got everything installed on 7.1.2 fresh install. Installed Fix2. I went to install the Confirmation server ( same box, I know it should be separate but client won't allocate) for Legal Hold Module and I noticed that it detected a previous version even though there was none. Then installation failed with these errors in log file: checking data store (0.1.1.4:esadb_lds_case_group_4) checking data store (0.1.1.5:esadb_lds_case_appliance_5) checking data store (0.1.9083.1563164678:esadb_lds_evidence_repo_a6wwh757gm) an unexpected error occurred while reading cluster info: null java.lang.ExceptionInInitializerError at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.hibernate.engine.UnsavedValueFactory.instantiate(UnsavedValueFactory.java:22) at org.hibernate.engine.UnsavedValueFactory.getUnsavedIdentifierValue(UnsavedValueFactory.java:44) at org.hibernate.tuple.PropertyFactory.buildIdentifierProperty(PropertyFactory.java:44) at org.hibernate.tuple.entity.EntityMetamodel.<init>(EntityMetamodel.java:123) at org.hibernate.persister.entity.AbstractEntityPersister.<init>(AbstractEntityPersister.java:434) at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:109) at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:226) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294) at com.teneo.esa.common.database.PersistenceManagerImpl.<init>(PersistenceManagerImpl.java:93) at com.teneo.esa.common.database.PersistenceManagerFactory.createPersistenceManager(PersistenceManagerFactory.java:684) at com.teneo.esa.common.database.PersistenceManagerFactory.getPersistenceManager(PersistenceManagerFactory.java:332) at com.teneo.esa.common.database.PersistenceManagerFactory.getPersistenceManager(PersistenceManagerFactory.java:244) at com.teneo.esa.cluster.DataStoreLocatorImpl.getPersistenceManager(DataStoreLocatorImpl.java:497) at com.teneo.esa.cluster.ClusterServiceBase$TransactionT1.transact(ClusterServiceBase.java:268) at com.teneo.esa.cluster.DataStoreLocatorImpl.getMetaData(DataStoreLocatorImpl.java:509) at com.teneo.esa.cluster.DataStoreLocatorImpl.getMetaData(DataStoreLocatorImpl.java:46) at com.teneo.esa.cluster.ClusterAdminTool.checkSystem(ClusterAdminTool.java:309) at com.teneo.esa.cluster.ClusterAdminTool.main(ClusterAdminTool.java:618) at com.teneo.esa.cluster.ClusterAdminTool.main(ClusterAdminTool.java:636) at com.teneo.esa.cluster.ClusterAdminTool.main(ClusterAdminTool.java:652) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.teneo.esa.Main.runPatched(Main.java:252) at com.teneo.esa.Main.mainStatus(Main.java:85) at com.teneo.esa.Main.main(Main.java:45) Caused by: java.lang.IllegalArgumentException: unregistered type manager for class com.teneo.esa.matter.Court at com.teneo.esa.cluster.TypeManager.<init>(TypeManager.java:91) at com.teneo.esa.cluster.TypeManager.<init>(TypeManager.java:60) at com.teneo.esa.matter.Court.<clinit>(Court.java:12) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.hibernate.engine.UnsavedValueFactory.instantiate(UnsavedValueFactory.java:22) at org.hibernate.engine.UnsavedValueFactory.getUnsavedIdentifierValue(UnsavedValueFactory.java:44) at org.hibernate.tuple.PropertyFactory.buildIdentifierProperty(PropertyFactory.java:44) at org.hibernate.tuple.entity.EntityMetamodel.<init>(EntityMetamodel.java:123) at org.hibernate.persister.entity.AbstractEntityPersister.<init>(AbstractEntityPersister.java:434) at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:79) at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:226) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294) at com.teneo.esa.common.database.PersistenceManagerImpl.<init>(PersistenceManagerImpl.java:93) at com.teneo.esa.common.database.PersistenceManagerFactory.createPersistenceManager(PersistenceManagerFactory.java:684) at com.teneo.esa.common.database.PersistenceManagerFactory.getPersistenceManager(PersistenceManagerFactory.java:332) at com.teneo.esa.common.database.PersistenceManagerFactory.getPersistenceManager(PersistenceManagerFactory.java:244) at com.teneo.esa.cluster.DataStoreLocatorImpl.getPersistenceManager(DataStoreLocatorImpl.java:497) at com.teneo.esa.cluster.ClusterServiceBase$TransactionT1.transact(ClusterServiceBase.java:268) at com.teneo.esa.cluster.DataStoreLocatorImpl.getMetaData(DataStoreLocatorImpl.java:509) at com.teneo.esa.cluster.DataStoreLocatorImpl.getMetaData(DataStoreLocatorImpl.java:46) at com.teneo.esa.cluster.ClusterAdminTool.checkSystem(ClusterAdminTool.java:309) at com.teneo.esa.cluster.ClusterAdminTool.main(ClusterAdminTool.java:618) at com.teneo.esa.cluster.ClusterAdminTool.main(ClusterAdminTool.java:636) at com.teneo.esa.cluster.ClusterAdminTool.main(ClusterAdminTool.java:652) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.teneo.esa.Main.runPatched(Main.java:253) ... 2 more any thoughts? ideas?Solved819Views1like1Comment