11-19-2014 12:09 PM
I’ve been trying to get the EV Office Mail App to work for OWA on Exchange 2013 servers and have some questions I hope might be answered here:
You must configure HTTPS with a suitable certificate on Enterprise Vault servers that serve the Enterprise Vault Office Mail App. Office Mail Apps must be served using Secure Sockets Layer (SSL). We recommend that you obtain a certificate from a certification authority. Otherwise, if the certificate is from another source, a browser may display a warning and require the user to accept the certificate. Prompting for acceptance of a certificate is not available in the Office Mail App. The result is that the user sees a blank window in the Office Mail App. You do not have to configure Enterprise Vault to use HTTPS at site level.
So which web directory do you configure to use the certificate?
$Mbx = get-mailbox "mailbox"
New-App -mailbox $Mbx.LegacyExchangeDN –Url `("http://EV_server/EnterpriseVault/OfficeMailAppManifest.aspx?LegacyMbxDn=" + $Mbx.LegacyExchangeDN)
Should that read HTTPS://EV_Server/.....?
11-19-2014 12:13 PM
you're probably right. that's exactly what they show in the troubleshooting video. check it out
https://www-secure.symantec.com/connect/videos/enterprise-vault-exchange-2013-owa-support-troubleshooting
11-20-2014 01:15 AM
The certificate goes on the standard "EnterpriseVault" virtual directory.
The example powershell script is correct. The configuration can be done with http, if you have https setup then you can also use that, but it not a requirement.
However, https is required for the App to work in OWA - that is a Microsoft requirement for all Mail Apps.
11-20-2014 06:25 AM
Thanks Richard.
One more question: Does the certificate need to be generated with the EV server alias? or the host name? or both?
11-21-2014 09:33 AM
Is it safe to assume that we can use the alias to create the certificate request? Fully qualified name, I assume?
11-21-2014 09:35 AM
i would get a SAN cert and include all the names