asked on Exchange 2013/Shared Accounts
I am hosting multiple domain names in my Exchange 2013 environment and require shared mailbox accounts with the same alias, that is
enquiries@domainA.co.uk
enquiries@domainB.co.uk
I have managed to created these shared mailboxes through EAC and all looks good to go.
I can add enquiries@domainA.co.uk to any Outlook clients requiring it using
File-Account Settings-Account-Settings-
but when I try to add enquiries@domainB.co.uk I get an error back stating:
An encrypted connection to your mail server is not available.
Click Next to attempt using an unencrypted connection.
I then get the option to configure the shared mailbox manually, but because it is an Exchange account I am unable to proceed.
I suspect that the Autodiscovery process is failing because I do not have autodiscover.domainB.co.uk
Before I go off and rekey my SSL certificate can anyone confirm my thoughts or offer some other solution?
Thank You
Brian
enquiries@domainA.co.uk
enquiries@domainB.co.uk
I have managed to created these shared mailboxes through EAC and all looks good to go.
I can add enquiries@domainA.co.uk to any Outlook clients requiring it using
File-Account Settings-Account-Settings-
but when I try to add enquiries@domainB.co.uk I get an error back stating:
An encrypted connection to your mail server is not available.
Click Next to attempt using an unencrypted connection.
I then get the option to configure the shared mailbox manually, but because it is an Exchange account I am unable to proceed.
I suspect that the Autodiscovery process is failing because I do not have autodiscover.domainB.co.uk
Before I go off and rekey my SSL certificate can anyone confirm my thoughts or offer some other solution?
Thank You
Brian
Exchange
Last Comment
3D2K
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Hi Brian
Thanks for the update. Yeah it can get very costly for multiple domaisn but as you said a wildcard may be an option for them. Unfortunately a proper SSL is almost a requirement to use all of the Exchange features these days.
Andy
Thanks for the update. Yeah it can get very costly for multiple domaisn but as you said a wildcard may be an option for them. Unfortunately a proper SSL is almost a requirement to use all of the Exchange features these days.
Andy
ASKER
Hi Andy
Run into another issue know that I'm just investigating. I've rekeyed my SSL cert with a new set of SANs and when I come to "Complete" the Certificate WIzard Request it seems to complete but then just sits there with "Request Pending". If I attempt to "Complete" again it tells me the request has already been actioned Doh!
I suspect I should have "Renew"ed the existing certificate.
If I don't find an answer then I'll delete the new request and clear any certificates lying around for it and then try the "Renew" existing certificate option.
Brian
Run into another issue know that I'm just investigating. I've rekeyed my SSL cert with a new set of SANs and when I come to "Complete" the Certificate WIzard Request it seems to complete but then just sits there with "Request Pending". If I attempt to "Complete" again it tells me the request has already been actioned Doh!
I suspect I should have "Renew"ed the existing certificate.
If I don't find an answer then I'll delete the new request and clear any certificates lying around for it and then try the "Renew" existing certificate option.
Brian
Ran the connectivity test and lo and behold came back with an SSL error.
I've rekeyed my SSL certificate with the additional autodiscover domain.
Could turn out to be an expensive business for the company I'm working for as they are looking at more domains so may be into wildcard territory for SSL certificates!
Thanks
Brian