Thomas.Poett@TEAMS (MVP Teams and Cross-Tenant M&A/D Migration Expert Lead)

I got it finally solved: Well there are more issues compared to simple resting services. Here what you have to do: 1. follow exactly Microsoft setup guide ! : http://technet.microsoft.com/library/2591b1be-92c4-4192-9f5e-e4e6b319170a 2. as its recommended to chose SSL in production environment, you need to validate the discovery point incl HTTPS !! not like described by MSFT with http, if its not enabled. mostly you will see an Certificate Error, because the Cert you requested via IIS is not a valid Cert incl a SAN Name: Make sue you have: the hostname, hostname.domain.com in this certificate and assign it to HTTP80 and HTTP809 SSL Services. 3. run IISRESET 4. you properly see issues with the Watchdog, check the log under: C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS if you see the Watchdog is accessing the WAC Server via HTTP, you need add the Port 80 under HTTP80 WebSite. I believe its a bug here. 5. IISRESET again 6. check now from OWA if it works or not, if n...

Hi all, (This is an updated version 2.2: 09 .07.201 5 ) This blog entry is valid for Lync 2010, Lync 2013 and Skype for Business Server. Generally, I'll write a new blog article, since the conversion history over multiple device and other service have change with Skype for Business 2015 Server. Once this written, I post the link here. there is always confusion in how Lync is crawling Exchange Web Services (EWS). Generally it is necessary to understand how DNS must be implemented: Just remember, identify if you have DNS Split configuration, different internal and external DNS names and what are your SMTP and SIP Domains. Very often you find in Lync/ Exchange deployments an issue, where the Lync configuration show up with empty: EWS Internal URL EWS External URL and EWS Information = EWS not deployed Therefor Exchange Web Service are not connected deployed and several Lync Integration Features are not working, e.g. Presence Information based on your Outlook Calendar....