Need advice on enterprise vault.
We had enterprise vault 10 with exchange 2010 due to some reason we stopped archiving mailbox.
Recently we updated exchange to 2016 Cu10. We are in the process to enable mailbox archiving again.
the question is
1. Can we install a fresh EV version 12.4 on new hardware and start archving again.
2. Is there anything we need to do on the old EV before we implement the new setup (like uninstall the ev, decomminisiong).
Regards,
Patwi
Hello Patwi,
If your old EV is still running, you should consider to disable the mailboxes for archiving in the old one, and maybe even ZAP the mailbox (Utilities guide, see EVPM). You should also consider removing shortcuts from mailboxes (if you still have them for the old EV).
When installing the new one, make sure you use a seperate SQL Instance (or SQL server) as the Directory database will need to be seperate from the old one.
Hello Gertjan,
Good Morning,
Thankyou for the reply.
as you said disabling and removing shortcut will be taken care of.
What is ZAP of mailbox i could not figure out. would let me know what is it.
I tried to search documents pertaining to decommining of enterprise server however could not find the right ones.
Regards,
Patwi
Hello Patwi,
Zapping a mailbox is disassociating it from the archive, effetively removing the EV hidden message. It is not really necessary, but eases enabling mailboxes in the new EV.
You can find information on EVPM (EV Policy Manager) in the Utilities guid. Link to Utilities EV10 guide. Works the same in your new EV btw. You can also run EVPM from the new EV.
In short, syntax would be like below. Create an INI file. Run EVPM from CMD (as Admin).
Create INI file, save as UNICODE
Content:
[Directory]
DirectoryComputerName = fqdn or alias for EV server
SiteName = your sitename
[Mailbox]
DistinguishedName = ALL
zap = true
syntax:
EVPM -e Exchange_server -m mailbox_alias -f input_file
Where Exchange_Server is the Exchangeserver where the mailboxes are
Where Mailbox_Alias is the smtp-address of EV System Mailbox
Where input_file is the path and name of the INI file
also go through the compatibility chart of enterprise vault. maybe you have components that aren't supported afterwards.
You will probably also want to migrate the archives from the old EV to new EV system.
You will need probably need a new SQL version...
