Lync 2010 Mobility Autodiscover
Recently I have been configuring a Lync 2010 environment as a PoC for IM and presence for my company.
The PoC includes using IM and presence from the desktop and on mobile devices. This requires an edge configuration and reverse proxy using TMG 2010.
I found the following blog post which is great for setting up mobility
http://blog.schertz.name/2011/12/deploying-the-lync-2010-mobility-service/
Everything was configured included DNS names, certificates, software install etc.etc.
Once I had everything configured I found that if I tried to connect using my iPad device it would provide the following error message.
Can't connect to the server. It may be busy or temporarily unavailable. Please try again
I looked at the logging and found that the Lyncdiscover URL wasn't being redirected to the configuration file required to login.
Browsing to https://lyncdiscover.companyname.com would simply produce a error 403 forbidden message.
I went to "more details" and turned auto config off and entered the following URL in the internal and external address
https://lyncdiscover.companyname.com/Autodiscover/AutodiscoverService.svc/root (replace companyname with your relevant address!)
When visiting the above URL in Internet Explorer it will download a configuration file which contains the data required to login.
With this configured the logon worked. This was fine, but I didn't want to provide a massive URL for configuration and wanted autoconfiguration working correctly.
My next stop was IIS URL rewrite rules on the server. These are configured to redirect users with anything with lyncdiscover in the HTTP_HOST header to be redirected to the config file above. I checked the rules and found they were all sound. Also browsing on the localhost didn't redirect so I ruled out the TMG 2010 server being at fault.
Finally I went to add/remove programs and found the following entry.
Clicking repair on this resolved the issue for me.
When visiting https://lyncdiscover.companyname.com I get the configuration file as if I were visiting https://lyncdiscover.companyname.com/Autodiscover/AutodiscoverService.svc/root.
I hope this helps you!
Sam Google +
The PoC includes using IM and presence from the desktop and on mobile devices. This requires an edge configuration and reverse proxy using TMG 2010.
I found the following blog post which is great for setting up mobility
http://blog.schertz.name/2011/12/deploying-the-lync-2010-mobility-service/
Everything was configured included DNS names, certificates, software install etc.etc.
Once I had everything configured I found that if I tried to connect using my iPad device it would provide the following error message.
Can't connect to the server. It may be busy or temporarily unavailable. Please try again
I looked at the logging and found that the Lyncdiscover URL wasn't being redirected to the configuration file required to login.
Browsing to https://lyncdiscover.companyname.com would simply produce a error 403 forbidden message.
I went to "more details" and turned auto config off and entered the following URL in the internal and external address
https://lyncdiscover.companyname.com/Autodiscover/AutodiscoverService.svc/root (replace companyname with your relevant address!)
When visiting the above URL in Internet Explorer it will download a configuration file which contains the data required to login.
With this configured the logon worked. This was fine, but I didn't want to provide a massive URL for configuration and wanted autoconfiguration working correctly.
My next stop was IIS URL rewrite rules on the server. These are configured to redirect users with anything with lyncdiscover in the HTTP_HOST header to be redirected to the config file above. I checked the rules and found they were all sound. Also browsing on the localhost didn't redirect so I ruled out the TMG 2010 server being at fault.
Finally I went to add/remove programs and found the following entry.
Clicking repair on this resolved the issue for me.
When visiting https://lyncdiscover.companyname.com I get the configuration file as if I were visiting https://lyncdiscover.companyname.com/Autodiscover/AutodiscoverService.svc/root.
I hope this helps you!
Sam Google +
wow. That's the weirdest thing ever eh? Glad you fixed it. Never heard of that symptom.
ReplyDelete(via TechNet Forums)
Tell me about it! I was racking my brains for ages trying to fix it!
ReplyDeleteHaving a similar problem but internal network wifi wont connect. We don't have a TMG and if I browse to (internally) https://lyncdiscover.domain.com/Autodiscover/AutodiscoverService.svc/root - i dont get anything. Only works externally.
ReplyDeleteExternal clients are fine connecting, its just internal. I suspect it's the hairpining. Any way to check?
What is your setup like? If you have no TMG how are you enabling external access? It sounds like an IIS issue with dual network cards maybe
DeleteDoes http work?
Mr Unknown, I have the exact opposite problem! Mine will work internally but I cannot for the life of me get it to connect externally.
ReplyDeleteThe oddest part, if I connect internally and then switch off my wifi and go to Mobile Data I'm still able to send and receive messages..
Any clues Samuel?
Hi Johnny
DeleteSounds like the autoconfig from remote is not working properly, especially if it works externally after internal config. Externally can you resolve https://lyncdiscover.companyname.com ? If so what do you get?
Sam
I don't see a prompt to save the configuration file, but after that I am still not able to login. I don't see the "more details" either. Any ideas? I am still getting the 403 forbidden for my internal... thanks!
ReplyDeleteYou should see a prompt for the configuration file? How about if you browse to the full path externally? https://lyncdiscover.companyname.com/Autodiscover/AutodiscoverService.svc/root
ReplyDeleteDoes this provide a cfg file?
On Android you must press the option key to get the "More Options" button. On iOS, it is underneath the logon name.
i get "The resource cannot be found." when trying to access
ReplyDeletehttps://lyncdiscover.companyname.com/Autodiscover/AutodiscoverService.svc/root
I checked the IIS console and found that there is no URL rewrite rule for autodiscover.
ReplyDeleteHow can I create URL rewrite rules for redirect autodiscover ?
Should I repair the "IIS URL Rewrite Module 2"component on front end server ?
TNX.
Hi Sadegh
DeleteYes, hit repair on the IIS URL Rewrite Module on the Front End server.
Sam
I repaired that component but nothing was changed.
ReplyDeleteThis was a life saver. Thanks for your help. I've been beating my head against my desk for a couple of days about this.
ReplyDeleteSolved my problem and my Chistmas. Thanks!
ReplyDelete