What FQDN to use when Setting Up OWA/Lync Integration?

re: What FQDN to use when Setting Up OWA/Lync Integration?

dodeitte — Sun, 29 Jan 2012 15:19:10 GMT

@James Xiong

No, if you have multiple CAS Servers, the Trusted application pool name would be the CAS array FQDN. Listing the CAS Servers under that is telling Lync what FQDNs to accept traffic from.

re: What FQDN to use when Setting Up OWA/Lync Integration?

James Xiong — Sun, 29 Jan 2012 03:26:58 GMT

If one of my CAS servers is down due to the hardware issue, Do I need to change the Trusted application pool name before I put the crased CAS alive?

re: What FQDN to use when Setting Up OWA/Lync Integration?

Rocky — Fri, 27 Jan 2012 18:51:42 GMT

Thank you very much Doug. This helped me fix the issue I was experiencing in my lab.

re: What FQDN to use when Setting Up OWA/Lync Integration?

TechnoMusic — Fri, 27 Jan 2012 12:25:49 GMT

Hi Dough I recently had this issue when I ran a trace it was getting the OWA public address name rejected. I had to add this fqdn to the trusted pool. I know now because of u that it was rejecting this address because it was on the cert SN

Cheers :-)

re: What FQDN to use when Setting Up OWA/Lync Integration?

dodeitte — Thu, 12 Jan 2012 01:46:13 GMT

@Gus

Thanks for the feedback! When you talk about "sub-app", are you talked about the image above that shows my CAS Server (LAB-EX2010.lab.deitterick.com)? If so, that gets created via Topology Builder. When you create the Trusted Application Pool, you want to pick "Multiple computer pool". That will allow you to list your CAS Server(s).

re: What FQDN to use when Setting Up OWA/Lync Integration?

Gus — Tue, 10 Jan 2012 13:47:41 GMT

Hi Doug, great information. I'm running into this issue right now. My question is, what were the commands you used to do this? I can create the pool name no problem using the cert that is registered, but how did you create the sub-app below deitterick.com?

In my case, I have a public cert on my internal exchange server with the public name mail.domain.com. But the internal FQDN is exch.hq.domain.com. Since IIS has the public FQDN, my trace shows the exact same error you have above.

Thanks in advance.