Kenzii
asked on
Out Of Office restriction for domain name
Hi,
Currently our exchange server has multiple domains to send from, external email users originally were all part of Domain1.com. This has a SAN cert setup for OWA/Mail/Autodiscover
When trying to setup an out of office for Domain2.com Users receive an error saying unable to connect to the server, using test auto configuration, the results showed that domain2.com was trying to access autodiscover.domain2.com, ideally I don’t want to have to buy another SAN certificate, is there a work around to point all of domain2 queries to domain1?
Thanks
Currently our exchange server has multiple domains to send from, external email users originally were all part of Domain1.com. This has a SAN cert setup for OWA/Mail/Autodiscover
When trying to setup an out of office for Domain2.com Users receive an error saying unable to connect to the server, using test auto configuration, the results showed that domain2.com was trying to access autodiscover.domain2.com, ideally I don’t want to have to buy another SAN certificate, is there a work around to point all of domain2 queries to domain1?
Thanks
Oh and yes, you'll need the following SRV record to point to your second domain.
_autodiscover._tcp.domain2 .com to point to your second CAS Server.
Regards,
Exchange_Geek
_autodiscover._tcp.domain2
Regards,
Exchange_Geek
ASKER
We only have the one CAS server.
So, would buying a domain2.com SAN and applying it to the same CAS server work?
So, would buying a domain2.com SAN and applying it to the same CAS server work?
OL is rather unbiased towards how many CAS Servers you have, it is a very stubborn child when it has to work towards Autodiscover and certificates - it simply understands the @domain2.com and its associated SRV and cert.
If it cannot find _autodiscover._tcp.domain2 .com published OR A record for autodiscover.domain2.com - it will start crying. if that wasn't all, it will start crying for the certificate not having any of the following
autodiscover.domain2.com, webmail.domain2.com, CAS Server, CAS Fqdn.
OL 2003 was way better - it never used to cry so much.
Regards,
Exchange_Geek
If it cannot find _autodiscover._tcp.domain2
autodiscover.domain2.com, webmail.domain2.com, CAS Server, CAS Fqdn.
OL 2003 was way better - it never used to cry so much.
Regards,
Exchange_Geek
ASKER
Ok, I'm confused.
So the only way I can work around this is to have 2 seperate CAS servers?
Seem's a bit of a expensive solution just to allow external users of domain2 to be able to set out of office.
I was hoping worse case. That we could just buy the SAN certificate and create the a record for autodiscover.
So the only way I can work around this is to have 2 seperate CAS servers?
Seem's a bit of a expensive solution just to allow external users of domain2 to be able to set out of office.
I was hoping worse case. That we could just buy the SAN certificate and create the a record for autodiscover.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Read the articles for step by step solution
http://marckean.wordpress.com/2009/10/09/install-self-signed-exchange-2010-ssl-certificate/
http://www.tekcrack.com/creating-your-own-self-signed-sans-certificate-for-exchange-2010-and-iis-70-1of3.html
Regards,
Exchange_Geek