How does lync for mac autodiscover work how to#
How does lync for mac autodiscover work verification#
How does lync for mac autodiscover work windows#

How does lync for mac autodiscover work verification#

The best way to show this is by using the Remote Connectivity Analyzer on http:/In the RCA select the Office 365 tab and check Outlook Autodiscover in the Microsoft Office Outlook Connectivity Tests section.Д®nter email address, user account and password, enter the verification code and click Perform Test. So, Outlook does a request for a user called Autodiscover returns a Mail-Enabled User with target address Next, Outlook wil try an Autodiscover request for this SMTP address. Based on this target address a new Autodiscover request is initiated. an Outlook client does an Autodiscover request to the Exchange environment it detects the user is a Mail-Enabled User, and that a target address is set. This is what happens: when you move a Mailbox from Exchange on-premises to Exchange Online, the Mailbox on-premises is converted to a Mail-Enabled User (Remote Mailbox) and a target address is set to Exchange Online (i.e. This is one of the advantages of an Exchange hybrid scenario. Not a single word on autodiscover though, and even when autodiscover is pointing to your on-premises Exchange environment, it continues to work for Mailboxes that have been migrated to Exchange Online.

How does lync for mac autodiscover work how to#

#log local0.In the previous articles I showed you how to implement DirSync, create an Exchange hybrid environment with a migration endpoint and how to migrate Mailboxes from Exchange on-premises to Exchange Online. In our case we were able to use the aFlex rules to block requests from everything except the clients we wanted to explicitly allow. In this scenario a load balancer such as an F5 BigIP or A10 Networks AX device can be incredibly handy because of their iRules and aFlex engine. That seems like a good idea if you know all the strings for every possible EWS client out there, but what happens when a new client comes out thatвЂ™s not specified here? It would be allowed to connect and bypass the restrictions we were trying to impose. You can see here that TMG is expecting you to explicitly block specific user agents that you don't want to allow:

TMG actually has a User Agent filtering tool built in, but it was very unfortunately written backwards for what we needed.

Lync iOS (iPad and iPhone): Microsoft Lync iPhone.

We started with working out which user agents we actually needed to allow and came up with the following list after running some logs and tracking the user agent headers in sample client connections: We needed some way to block those clients so we settled on filtering based on the User Agent string, which is a unique string within the HTTP header identifying the type of client making a request. This would work great if all you had in the world were PCs, but the challenge here is the Mac Outlook and older Entourage 2008 Web Services clients are entirely based on EWS and by configuring the previous tasks in TMG we were now allowing those remote clients to connect. YouвЂ™ll also want to make sure the ExternalURL property of your EWS virtual directories are populated with the correct FQDN and that public names for that URL and autodiscover are allowed in TMG: Remote Outlook clients will perform a successful autodiscover lookup, but see Outlook Anywhere is disabled (assuming youвЂ™ve disabled it on the CAS!) and not attempt a connection.

This will effectively allow remote users to connect and do autodiscover queries. After using the Outlook Anywhere publishing rule template in TMG simply edit the paths tab and remove everything except /EWS/* and /Autodiscover/*: Publishing only EWS is a straightforward process and can be done through the TMG publishing rules. To work around this issue we started with a goal to publish only Exchange Web Services to support Lync clients, and still prevent all other types of clients from connecting to Exchange remotely. All of those require EWS to be published remotely or there will be some feature loss and very visible errors within the user interface.

How does lync for mac autodiscover work windows#

If EWS is not available a Windows Lync client can fall back to pull some data from Outlook via MAPI, but that does nothing to help a Mac Lync user, Lync mobile devices for iOS, or any Lync Phone Edition clients. This presented some challenges in terms of features available to remote Lync clients since a lot of functionality comes from Exchange Web Services (EWS). They were using Good for all email to mobile devices, and had elected not to publish Outlook Anywhere or Outlook Web app remotely. A recent Lync project for me involved a scenario where the customer who was not publishing any aspect of Exchange remotely.