So I have a situation where I have taken over a network support project where the internal domain name is set to server.somedomain.com
The exchange server's full computer name is hence companymail.server.somedomain.com
Now the problem is the company does not own somedomain.com. So when trying to issue an SSL certificate to the Exchange server, godaddy tries to verify ownership of somedomain.com, which obviously cant be done. I have tried to issue the certificate instead to the domain they do own, as outlook.ourdomain.com
but then outlook and mobile mail clients get the annoying certificate warning every time Outlook is opened or mobile devices are set up that the name on the certificate does not match the server name.
I believe there is a workaround for this so that autodiscover can use outlook.ourdomain.com and get the autodiscover info. Both of those are working. But when it gets the server info from autodiscover it gets the server.somedomain.com info and were back to square one. I either end up not being able to connect to the server externally because of the unowned domain or I get the annoying certificate errors pops when the users connect. Any idea how to properly bandaid this? Changing the domain and server name from what I have read is not worth the headache. Thanks.
Edited by bastille, 29 June 2016 - 05:50 AM.