tag:blogger.com,1999:blog-3105431236986649233.post4902228169535209564..comments2024-03-26T05:18:54.770-04:00Comments on Lync Me - Unified Communications Blog: OWA Integration with Lync - Wildcard issuesTim Day - MCP, MCITP, MCSE, FCNSAhttp://www.blogger.com/profile/15981859744273688876noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-3105431236986649233.post-8944628685037325062017-03-04T02:24:39.104-05:002017-03-04T02:24:39.104-05:00I glad reading this post, thank you for updating a...I glad reading this post, thank you for updating and sharing useful article with us<br /><a href="https://hostingsafety.com/ssl-certificates.php" rel="nofollow"><b>Website Security Certificate</b></a> | <a href="https://hostingsafety.com/ssl-certificates.php" rel="nofollow"><b>SSL certificate Prices</b></a> | <a href="https://hostingsafety.com/ssl-certificates.php" rel="nofollow"><b>SSL Certificate Integration Service</b></a>Hostingsafetyhttps://www.blogger.com/profile/13170593378519311885noreply@blogger.comtag:blogger.com,1999:blog-3105431236986649233.post-60186731517153635082015-01-26T04:46:01.670-05:002015-01-26T04:46:01.670-05:00Hi, thank you for this article.
I've followed...Hi, thank you for this article.<br /><br />I've followed the steps. and couldn't get it to work. I've checked everything, the web.config files on both CAS and Mailbox servers. For some reason, I couldn't see the thumbprint of the new certificate in there. Though, it is available in IIS Manager.<br /><br />Any other tips?<br /><br />Thanks.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3105431236986649233.post-3501953901714760672015-01-22T16:30:09.785-05:002015-01-22T16:30:09.785-05:00Nice article! I couldn't get this to work, bu...Nice article! I couldn't get this to work, but then I remembered that I had modified the web.config file in C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa to use the wildcard cert thumbprint. After changing the to the thumbprint value of the cert requested in your article, recycling the app pool with the following command: C:\Windows\System32\Inetsrv\Appcmd.exe recycle apppool /apppool.name:"MSExchangeOWAAppPool" and having a bunch of users mad at me for kicking them out of Outlook, OWA integration worked. Mix your article with the Microsoft article and it's easy as pie! https://technet.microsoft.com/en-us/library/jj688055.aspxAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3105431236986649233.post-29713158075933015692014-05-22T08:00:58.587-04:002014-05-22T08:00:58.587-04:00Hi Shawn,
Yes Exchange 2013/Lync 2013 integration...Hi Shawn,<br /><br />Yes Exchange 2013/Lync 2013 integration is just as straight forward, apologies for no post as I have been swamped in Exchange projects and Lync has been on the back burner for the last few months. To poke more into your Exchange environment, any reason to have your server FQDNs on the SSL Certificate? Personally I would create the same namespace (mail.company.com) for both internal and external URLs, then do split DNS pointing mail.domain.com internally to your load balancer/DNS round robin, then externally to your public IP Address. makes your deployment much easier to manage and does not expose your internal server FQDN... Sorry to go on an Exchange rant :) <br /><br />As for Lync2013/Exchange 2013 integration great TechNet Wiki article http://social.technet.microsoft.com/wiki/contents/articles/13168.integrating-exchange-2013-owa-and-lync-server-2013.aspx<br />Tim Day - MCP, MCITP, MCSE, FCNSAhttps://www.blogger.com/profile/15981859744273688876noreply@blogger.comtag:blogger.com,1999:blog-3105431236986649233.post-2467658070386318372014-05-22T02:57:40.951-04:002014-05-22T02:57:40.951-04:00Hey Tim,
So I'm assuming this carries over for...Hey Tim,<br />So I'm assuming this carries over for Exchange 2013/Lync 2013?<br /><br />And what would you do around having multiple consolidated role Exchange servers in a DAG. Subject name as CAS Array/OWA URL with alternate names for each internal server FQDN and load it on each server?ShawnCnoreply@blogger.comtag:blogger.com,1999:blog-3105431236986649233.post-74337811016656588572014-05-15T06:51:08.635-04:002014-05-15T06:51:08.635-04:00This comment has been removed by a blog administrator.Rachel Burrhttps://www.blogger.com/profile/07529548569341157571noreply@blogger.comtag:blogger.com,1999:blog-3105431236986649233.post-31686810331316823282013-12-10T08:13:54.278-05:002013-12-10T08:13:54.278-05:00Hi
i have did the same But the OWA integration not...Hi<br />i have did the same But the OWA integration not working.<br />The current Certifcate thumbprint matches with the subject name what is specified in lync<br />but the same error occursAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3105431236986649233.post-66910537974262406412013-01-27T09:37:41.171-05:002013-01-27T09:37:41.171-05:00You are correct, the certificate is only for OWA a...You are correct, the certificate is only for OWA and Lync communication and is not published externally. You will continue to use your wildcard certificate for external access to OWA.<br /><br />Thanks for reading!Tim Day - MCP, MCITP, MCSE, FCNSAhttps://www.blogger.com/profile/15981859744273688876noreply@blogger.comtag:blogger.com,1999:blog-3105431236986649233.post-32242766614807294152013-01-27T06:33:53.383-05:002013-01-27T06:33:53.383-05:00great post !
but i guess this newly created certif...great post !<br />but i guess this newly created certificate is just used for OWA and Lync to communicate right ? i mean will it work from outside your local network ? Anonymousnoreply@blogger.com