Lync Mobility, lyncdiscoverinternal or lyncdiscover

Can someone make points, how does
lyncdiscoverinternal make different?
In situation, where lyncdiscover (external) is working, what would I get to setup lyncdiscoverinternal?
Does ANYTHING changes?
- Meitzi [MCITP]

Firstly, I invite ANYONE who is not happy with our docs to provide feedback. We invite it and encourage it.
[email protected] for Lync Server 2010,
[email protected] for Lync Server 2013.
Secondly, We intentionally don't go into gory details in the Planning and Deployment docs - not any more than is absolutely necessary. The reason simply is we have a diverse audience and our goal with the Planning and Deployment docs is to
help people PLAN and DEPLOY. Technical depth is available by a number of means: We have the Lync Server 2010 Resource Kit, the NextHop blog (multitudes of articles on in-depth Mobility is there) and a Troubleshooting Lync Mobility Issues white
paper, among a whole bunch of MVPs.
Now, the direct question: Why NOT just avoid the whole lyncdiscoverinternal.<domain> record and just go to the Lyncdiscover.<domain> record for all internal and external users? Three reasons:
A) We have more information in the Autodiscover response than just "Hey! You're inside. Go outside!" "Hey, You're outside! It's all good!" Check the traces....
B) Newer clients that have been released since Cumulative Update for Lync Server 2010 : November 2011 (known affectionately to everyone else and their puppy as CU4) make use of BOTH records to know where they are and to use the correct internal or external
Web services for their purposes. Unless you want ALL clients to be hairpinning at your reverse proxy..... Both records are really needed.
C) We state that we only support DNS where BOTH lyncdiscover and lyncdiscoverinternal are implemented. Why? Refer to B)
Anyone that is questioning IF we want feedback - Drago Totev and Mr. Seeber can both tell you - we're serious when we say we want your feedback on our docs.
Cheers!
Rick Lync Server UA

Similar Messages

Lync Mobility 2013, lyncdiscoverinternal and Internal Certificates.

Hi Everyone,
The last few days i have been racking my brain over the deployment processes of Lync Mobility in a Lync 2013 environment.
What has got me confused is the process of lyncdiscoverinternal and the autodiscover certificate.
As far as I am aware, All lync 2013 clients require either lyncdiscover or lyncdiscoverinternal DNS records to determine whether they are internal or external to the corporate network.
Thats understandable.
What I cant understand, is the fact that the lync 2013 mobile client, when obtaining lyncdiscoverinrternal.domain.com (which points to the internal address of the front end pool) contacts the Lync front end
services for the auto discover record and is prompted for the certificate that's provided from the web services
on the front end. This certificate is signed by my Internal CA. Is that intended behavior?. because 100% that device
is not going to trust it.
Because if after the autodiscover service has succeeded the Mobility client will then return the external UCWA services URL
and then Hairpin via the reveres proxy back in. This part here makes total sense. So now we have the Mobile
client connected to the front end services VIA the reverse porxy. Public Certificate now.
But the autodiscover part is stumping me.
I can understand if I were to push all trusted CA certificates onto devices then this wouldnt be a problem. But is that feasible? I mean what about in BYOD scenarios, EG a college campus or school. Pushing certificates onto unmanaged devices is sometimes
not an option.
Have other people found solutions in getting the lyncdiscoverinternal record to work for mobility without installing trusted Root CA,s on mobility devices?
Or is a feasible option to create a new DNS for a Guest WIFI network and have only the lyncdiscover record exist just like it was an external network?
Or am i doing something wrong and missed and important design or configuration factor?
Is it possible to tell the Lync Mobility client to push ALL requests via the reverse proxy when on the internal network, Just like the old days when we issued "lyncdiscover" to the external Reverse
Proxy address.
Thanks.

After speaking with Microsoft Support, They did indeed inform me to use the "lyncdiscover" record internally.
They stated to remove the lyncdiscoverinternal record from the DNS and point the lyncdiscover record to the external side of the reverse proxy.
they also informed me that all desktop clients would fail upon using the lyncdiscover record and fall back to the SRV records.
Is this true?
Also once the autodiscover service has worked, how does the mobility client then connect to the server?
From what i have found it will use the external UCWA website on IIS address. Which is the Externallync webservices address which is alos pointing to the reverse proxy external address from the internal network.
Now what happens when media traffic is sent to and from the mobility device. Does it use the edge? If so is it fair to say that hairpinning of media traffic is required aswell?
Or does media use peer to peer or media bypass if enbaled?

Lync mobile Dns Qus

i Want to setup mobile device to use lync
My lab is internal area,only front-end server,Not Egle Server.
As my know,i need to setup Proxy Server Change 80 to 8080 and 443 to 4443.
My Front-end server is 192.168.1.102
My Proxy Server is 192.168.1.95
1)I Need Create to two DNS records for lync mob.
lyncdiscoverinternal is my front-end server 192.168.1.102?
lyncdiscover is my proxy server 192.168.1.95?
2)In my mobile apps lync,i find a one items is http proxy,i need type my proxy server any Information?

Hi,
For Lync mobility function, you need to deploy a Reverse proxy on DMZ zone.
For the DNS requirements of mobility:
Internal DNS records:
You need to create one of the following internal DNS records:
CNAME: lyncdiscoverinternal.<sipdomian>
resolves to internal Web Services FQDN for FE Server.
A: lyncdiscoverinternal.<sipdomain> resolves to internal Web Services IP address of FE Server.
External DNS records
You need to create one of the following external DNS records:
CNAME: lyncdiscover.<sipdomain> resolves to External Web Services FQDN for FE Server
A: lyncdiscover.<sipdomain> resolves to External or Public IP address of the Reverse Proxy
More details:
http://technet.microsoft.com/en-us/library/hh690040.aspx
http://technet.microsoft.com/en-us/library/hh690030.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync Mobile for external users not working

Hello,
We have Lync Server Enterprise pool with 2 front end server, 2 edge server & TMG for reverse proxy.
PC client internally & externally working. Internal mobile users are working. But not working for external mobile users.
I used 2 tools to check this.
Web based connectivity analyser, it runs without any error.
But when I use installed version of lync connectivity analyser its throws error that. Server discovery failed for secured internal channel against
https://lyncdiscoverinternal.mydomain.com
Also, I am able to download a .json file when you access
https://lyncdiscover.mydomain.com

Hello,
Sorry for late response. My TMG server was not functioning, now it is working for lync mobile is still having problem. I am pasting the lync analyser full reports:
Network access: NetworkAccessExternal
Logging test parameters:
SIP Uri: [email protected]
User Name:
Discovery Type: Automatic Discovery
Selected client: ApplicationLyncMobile2013
Starting Lync server autodiscovery
Please wait; this test may take several minutes to complete...
Starting automatic discovery for secure (HTTPS) internal channel
Sending HTTP request to
https://lyncdiscoverinternal.contoso.com/[email protected]
Cookie found in autodiscover response: StatusCode: 403, ReasonPhrase: 'Forbidden ( The server denied the specified Uniform Resource Locator (URL). Contact the server administrator. )', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
Connection: close
Pragma: no-cache
Cache-Control: no-cache
Content-Length: 2040
Content-Type: text/html
Autodiscover: SendRequest(): the URL
https://lyncdiscoverinternal.contoso.com/[email protected] couldn't be connected. Complete HTTP headers:\r\n Connection: close
Pragma: no-cache
Cache-Control: no-cache
Couldn't connect to URL
https://lyncdiscoverinternal.contoso.com/[email protected] (HTTP status code Forbidden)
System.Exception: Couldn't connect to URL
https://lyncdiscoverinternal.contoso.com/[email protected] (HTTP status code Forbidden)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.TerminateAD(String mesg)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
Server discovery failed for secured internal channel against
https://lyncdiscoverinternal.contoso.com/
Starting automatic discovery for unsecure (HTTP) internal channel
Sending HTTP request to
http://lyncdiscoverinternal.contoso.com/[email protected]
Cookie found in autodiscover response: StatusCode: 403, ReasonPhrase: 'Forbidden ( The server denied the specified Uniform Resource Locator (URL). Contact the server administrator. )', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
Connection: close
Pragma: no-cache
Cache-Control: no-cache
Content-Length: 2040
Content-Type: text/html
Autodiscover: SendRequest(): the URL
http://lyncdiscoverinternal.contoso.com/[email protected] couldn't be connected. Complete HTTP headers:\r\n Connection: close
Pragma: no-cache
Cache-Control: no-cache
Couldn't connect to URL
http://lyncdiscoverinternal.contoso.com/[email protected] (HTTP status code Forbidden)
System.Exception: Couldn't connect to URL
http://lyncdiscoverinternal.contoso.com/[email protected] (HTTP status code Forbidden)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.TerminateAD(String mesg)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
Server discovery failed for unsecured internal channel against
http://lyncdiscoverinternal.contoso.com/
Starting automatic discovery for secure (HTTPS) external channel
Sending HTTP request to
https://lyncdiscover.contoso.com/[email protected]
Cookie found in autodiscover response: StatusCode: 200, ReasonPhrase: 'OK', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
Connection: Keep-Alive
Pragma: no-cache
X-MS-Server-Fqdn: SGRFLYNC1.contoso.com
X-Content-Type-Options: nosniff
Cache-Control: no-cache
Date: Mon, 24 Nov 2014 13:36:49 GMT
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Content-Length: 1065
Content-Type: application/vnd.microsoft.rtc.autodiscover+xml; v=1
Expires: -1
Parsing the response for URL
https://lyncdiscover.contoso.com/[email protected]. Full response: <?xml version="1.0" encoding="utf-8"?><AutodiscoverResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" AccessLocation="External"><Root><Link token="Domain" href="https://lyncdiscover.contoso.com/Autodiscover/AutodiscoverService.svc/root/domain?originalDomain=contoso.com"
/><Link token="User" href="https://lyncdiscover.contoso.com/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=contoso.com"
/><Link token="Self" href="https://lyncdiscover.contoso.com/Autodiscover/AutodiscoverService.svc/root?originalDomain=contoso.com"
/><Link token="OAuth" href="https://lyncdiscover.contoso.com/Autodiscover/AutodiscoverService.svc/root/oauth/user?originalDomain=contoso.com"
/><Link token="External/XFrame" href="https://lyncdiscover.contoso.com/Autodiscover/XFrame/XFrame.html" /><Link token="Internal/XFrame"
href="https://lync.contoso.com/Autodiscover/XFrame/XFrame.html" /><Link token="XFrame" href="https://lyncdiscover.contoso.com/Autodiscover/XFrame/XFrame.html"
/></Root></AutodiscoverResponse>
Autodiscover URL
https://lyncdiscover.contoso.com/[email protected] redirected to
https://lyncdiscover.contoso.com/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=contoso.com
Sending HTTP request to
https://lyncdiscover.contoso.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
Cookie found in autodiscover response: StatusCode: 403, ReasonPhrase: 'Forbidden ( The server denied the specified Uniform Resource Locator (URL). Contact the server administrator. )', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
Connection: close
Pragma: no-cache
Cache-Control: no-cache
Content-Length: 2040
Content-Type: text/html
Autodiscover: SendRequest(): the URL
https://lyncdiscover.contoso.com/Autodiscover/AutodiscoverService.svc/root/[email protected] couldn't be connected. Complete HTTP headers:\r\n Connection: close
Pragma: no-cache
Cache-Control: no-cache
Couldn't connect to URL
https://lyncdiscover.contoso.com/Autodiscover/AutodiscoverService.svc/root/[email protected] (HTTP status code Forbidden)
System.Exception: Couldn't connect to URL
https://lyncdiscover.contoso.com/Autodiscover/AutodiscoverService.svc/root/[email protected] (HTTP status code Forbidden)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.TerminateAD(String mesg)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<ParseResponse>d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
Server discovery failed for secured external channel against
https://lyncdiscover.contoso.com/
Starting automatic discovery for unsecure (HTTP) external channel
Sending HTTP request to
http://lyncdiscover.contoso.com/[email protected]
Cookie found in autodiscover response: StatusCode: 200, ReasonPhrase: 'OK', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
Connection: Keep-Alive
Pragma: no-cache
X-MS-Server-Fqdn: SGRFLYNC1.contoso.com
X-Content-Type-Options: nosniff
Cache-Control: no-cache
Date: Mon, 24 Nov 2014 13:36:49 GMT
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Content-Length: 1065
Content-Type: application/vnd.microsoft.rtc.autodiscover+xml; v=1
Expires: -1
Parsing the response for URL
http://lyncdiscover.contoso.com/[email protected]. Full response: <?xml version="1.0" encoding="utf-8"?><AutodiscoverResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" AccessLocation="External"><Root><Link token="Domain" href="https://lyncdiscover.contoso.com/Autodiscover/AutodiscoverService.svc/root/domain?originalDomain=contoso.com"
/><Link token="User" href="https://lyncdiscover.contoso.com/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=contoso.com"
/><Link token="Self" href="https://lyncdiscover.contoso.com/Autodiscover/AutodiscoverService.svc/root?originalDomain=contoso.com"
/><Link token="OAuth" href="https://lyncdiscover.contoso.com/Autodiscover/AutodiscoverService.svc/root/oauth/user?originalDomain=contoso.com"
/><Link token="External/XFrame" href="https://lyncdiscover.contoso.com/Autodiscover/XFrame/XFrame.html" /><Link token="Internal/XFrame"
href="https://lync.contoso.com/Autodiscover/XFrame/XFrame.html" /><Link token="XFrame" href="https://lyncdiscover.contoso.com/Autodiscover/XFrame/XFrame.html"
/></Root></AutodiscoverResponse>
Autodiscover URL
http://lyncdiscover.contoso.com/[email protected] redirected to
https://lyncdiscover.contoso.com/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=contoso.com
Sending HTTP request to
https://lyncdiscover.contoso.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
Cookie found in autodiscover response: StatusCode: 403, ReasonPhrase: 'Forbidden ( The server denied the specified Uniform Resource Locator (URL). Contact the server administrator. )', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
Connection: close
Pragma: no-cache
Cache-Control: no-cache
Content-Length: 2040
Content-Type: text/html
Autodiscover: SendRequest(): the URL
https://lyncdiscover.contoso.com/Autodiscover/AutodiscoverService.svc/root/[email protected] couldn't be connected. Complete HTTP headers:\r\n Connection: close
Pragma: no-cache
Cache-Control: no-cache
Couldn't connect to URL
https://lyncdiscover.contoso.com/Autodiscover/AutodiscoverService.svc/root/[email protected] (HTTP status code Forbidden)
System.Exception: Couldn't connect to URL
https://lyncdiscover.contoso.com/Autodiscover/AutodiscoverService.svc/root/[email protected] (HTTP status code Forbidden)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.TerminateAD(String mesg)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<ParseResponse>d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
Server discovery failed for unsecured external channel against
http://lyncdiscover.contoso.com/
None, AutoInternalSecureD, AutoInternalUnsecureD, AutoExternalSecureD, AutoExternalUnsecureD, ManualDNSFail, ManualSecureD, ManualUnsecureD, AuthBrokerInternalLMXCheckGET, AuthBrokerInternalLMXCheckPOST, AuthBrokerExternalLMXCheckGET, AuthBrokerExternalLMXCheckPOST,
MobilityMCXInternalLMXCheckGET, MobilityMCXInternalLMXCheckPOST, MobilityMCXExternalLMXCheckGET, MobilityMCXExternalLMXCheckPOST, LMXSIPServerInternalDNS, LMXSIPServerExternalDNS, MobilityUCWAInternalCheckPOST, MobilityUCWAExternalCheckPOST
Automatic discovery of the Lync server failed. Please verify the server requirements at
http://go.microsoft.com/fwlink/?LinkId=278998 . Lync mobile apps do not require automatic discovery. You could enter the server FQDN manually and test connectivity again.
Microsoft Lync Connectivity Analyzer cannot analyze deployment readiness until a discovery test has completed successfully.

Lync Mobile Issues ARR IIS Reverse proxy

Hi All
I deployed Lync 2013 and cant seem to get the lync mobile services working.See exctract of Lync 2013 remote connectivity analyzer.
Error 1
An error occurred while sending the request.
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
The remote certificate is invalid according to the validation procedure.
Error 2
Server discovery failed for secured external channel against https://lyncdiscover.domain.co.za/
Error 3
An error occurred while sending the request.
The remote name could not be resolved: 'LFE.domain.local'
Please assist, public certificate is a wild card cert and the android client has the following error.
"Lync is attempting to redirect you to :
Issued bt:Internal CA
Subject:LFE.domain.local
Signature Algorithm: SHA1withRSA.
Sandile

See results of Lync connectivity analyzer.
Logging test parameters:
SIP Uri: [email protected]
User Name: [email protected]
Discovery Type: Automatic Discovery
Network access: NetworkAccessExternal
Selected client: ApplicationLyncMobile2013
Starting Lync server autodiscovery
Please wait; this test may take several minutes to complete...
Starting automatic discovery for secure (HTTPS) internal channel
lyncdiscoverinternal.adoutpost.co.za can't be resolved by the DNS server. Skipping internal discovery.
Starting automatic discovery for secure (HTTPS) external channel
Sending HTTP request to https://lyncdiscover.adoutpost.co.za/[email protected]
Cookie found in autodiscover response: StatusCode: 200, ReasonPhrase: 'OK', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
Pragma: no-cache
X-MS-Server-Fqdn: AD-LC-01.adoutpost.local
X-Content-Type-Options: nosniff
Cache-Control: no-cache
Server: Microsoft-IIS/8.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
X-Powered-By: ARR/2.5
Date: Wed, 08 Apr 2015 20:55:18 GMT
Content-Length: 1087
Content-Type: application/vnd.microsoft.rtc.autodiscover+xml; v=1
Expires: -1
Parsing the response for URL https://lyncdiscover.adoutpost.co.za/[email protected]. Full response: <?xml version="1.0" encoding="utf-8"?><AutodiscoverResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" AccessLocation="Internal"><Root><Link token="Domain" href="https://ad-lc-01.adoutpost.local/Autodiscover/AutodiscoverService.svc/root/domain?originalDomain=adoutpost.co.za"
/><Link token="User" href="https://ad-lc-01.adoutpost.local/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=adoutpost.co.za" /><Link token="Self" href="https://ad-lc-01.adoutpost.local/Autodiscover/AutodiscoverService.svc/root?originalDomain=adoutpost.co.za"
/><Link token="OAuth" href="https://ad-lc-01.adoutpost.local/Autodiscover/AutodiscoverService.svc/root/oauth/user?originalDomain=adoutpost.co.za" /><Link token="External/XFrame" href="https://lyncweb.adoutpost.co.za/Autodiscover/XFrame/XFrame.html"
/><Link token="Internal/XFrame" href="https://ad-lc-01.adoutpost.local/Autodiscover/XFrame/XFrame.html" /><Link token="XFrame" href="https://lyncweb.adoutpost.co.za/Autodiscover/XFrame/XFrame.html" /></Root></AutodiscoverResponse>
Autodiscover URL https://lyncdiscover.adoutpost.co.za/[email protected] redirected to https://ad-lc-01.adoutpost.local/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=adoutpost.co.za
Sending HTTP request to https://ad-lc-01.adoutpost.local/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=adoutpost.co.za?sipuri=sandile@adoutpost.co.za
Exception encountered while sending an HTTP request to https://ad-lc-01.adoutpost.local/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=adoutpost.co.za?sipuri=sandile@adoutpost.co.za: An error occurred while sending the request.. Complete Exception:
\r\nSystem.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The remote name could not be resolved: 'ad-lc-01.adoutpost.local'
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
--- End of inner exception stack trace ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
An error occurred while sending the request.
The remote name could not be resolved: 'ad-lc-01.adoutpost.local'
For troubleshooting, try using a browser to open the server discovery URL https://ad-lc-01.adoutpost.local/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=adoutpost.co.za?sipuri=sandile@adoutpost.co.za
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The remote name could not be resolved: 'ad-lc-01.adoutpost.local'
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
--- End of inner exception stack trace ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<ParseResponse>d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
Server discovery failed for secured external channel against https://lyncdiscover.adoutpost.co.za/
Starting automatic discovery for unsecure (HTTP) external channel
Sending HTTP request to http://lyncdiscover.adoutpost.co.za/[email protected]
Cookie found in autodiscover response: StatusCode: 406, ReasonPhrase: 'Not Acceptable', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
Date: Wed, 08 Apr 2015 20:55:29 GMT
Server: Microsoft-IIS/8.5
Content-Length: 1346
Content-Type: text/html
Autodiscover: SendRequest(): the URL http://lyncdiscover.adoutpost.co.za/[email protected] couldn't be connected. Complete HTTP headers:\r\n Date: Wed, 08 Apr 2015 20:55:29 GMT
Server: Microsoft-IIS/8.5
Couldn't connect to URL http://lyncdiscover.adoutpost.co.za/[email protected] (HTTP status code NotAcceptable)
System.Exception: Couldn't connect to URL http://lyncdiscover.adoutpost.co.za/[email protected] (HTTP status code NotAcceptable)
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.TerminateAD(String mesg)
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
Server discovery failed for unsecured external channel against http://lyncdiscover.adoutpost.co.za/
None, AutoInternalDNSFail, AutoInternalSecureD, AutoInternalUnsecureD, AutoExternalSecureD, AutoExternalUnsecureD, ManualDNSFail, ManualSecureD, ManualUnsecureD, AuthBrokerInternalLMXCheckGET, AuthBrokerInternalLMXCheckPOST, AuthBrokerExternalLMXCheckGET, AuthBrokerExternalLMXCheckPOST,
MobilityMCXInternalLMXCheckGET, MobilityMCXInternalLMXCheckPOST, MobilityMCXExternalLMXCheckGET, MobilityMCXExternalLMXCheckPOST, LMXSIPServerInternalDNS, LMXSIPServerExternalDNS, MobilityUCWAInternalCheckPOST, MobilityUCWAExternalCheckPOST
Automatic discovery of the Lync server failed. Please verify the server requirements at http://go.microsoft.com/fwlink/?LinkId=278998 . Lync mobile apps do not require automatic discovery. You could enter the server FQDN manually and test connectivity again.
Microsoft Lync Connectivity Analyzer cannot analyze deployment readiness until a discovery test has completed successfully.

Lync mobile device connection issue

Hello everybody,
I'm implementing Lync Mobility and remote access in our organization. Remote access is workig fine. But mobile devices cannot connecting to Lync Server 2010. My topology is :
Reverse Proxy Server(IIS7 works fine) <--> Front End Server <--> Back End Server
pool : pool1.lynctest.local
internal web srvc : lyncinternalweb.lynctest.local
external web srvc : lyncweb.lynctest.domain.com
All internal and external DNS records created. Deployed internal CA and external internal web service certificates issued from internal CA. Also installed all root certificates on mobile devices and other remote machines. Below is log from android device.
20 Mar 2014 10:53:27 INFO APPLICATION:SignIn. signInAsUserState=0, actualSessionState=0
20 Mar 2014 10:53:27 INFO APPLICATION:Sending AutoDiscovery request (in sign-in sequence)
20 Mar 2014 10:53:27 INFO TRANSPORT:setUsernamePasswordCredential changing credential:
20 Mar 2014 10:53:27 INFO TRANSPORT:Credential information: credType (1) signInName ([email protected]) domain () username ([email protected]) password.empty() (0) compatibleServiceIds(1)
20 Mar 2014 10:53:27 INFO APPLICATION:Serialized sipuri= intUcwa= extUcwa= intADRoot= extADRoot= location=1 networkType=1
20 Mar 2014 10:53:27 INFO APPLICATION:Storing 2 out-of-sync components took 49ms
20 Mar 2014 10:53:27 INFO APPLICATION:Timer cancelled. OnResume = 0
20 Mar 2014 10:53:27 INFO APPLICATION:Discover UCWA urls from https://lyncdiscover.lynctest.golomtbank.com & https://lyncdiscover.lynctest.golomtbank.com for sip:[email protected]
20 Mar 2014 10:53:27 INFO APPLICATION:Extracted lynctest.golomtbank.com from sip:[email protected]
20 Mar 2014 10:53:27 INFO APPLICATION:Starting Auto Discovery with urls https://lyncdiscover.lynctest.golomtbank.com?sipuri=sip:[email protected] and https://lyncdiscover.lynctest.golomtbank.com?sipuri=sip:[email protected]
20 Mar 2014 10:53:27 INFO TRANSPORT:getSpecificCredential returning the following credential for credType (1) serviceId (4)
20 Mar 2014 10:53:27 INFO TRANSPORT:Credential information: credType (1) signInName () domain () username () password.empty() (1) compatibleServiceIds(0)
20 Mar 2014 10:53:27 INFO TRANSPORT:Added Request(UcwaAutoDiscoveryRequest) to Request Processor queue
20 Mar 2014 10:53:27 INFO APPLICATION:Submitting new req. <unknown>
20 Mar 2014 10:53:27 INFO TRANSPORT:Sent Request(UcwaAutoDiscoveryRequest) to Request Processor
20 Mar 2014 10:53:27 INFO APPLICATION:Submitting Unauthenticated AutoDiscovery request to https://lyncdiscover.lynctest.golomtbank.com?sipuri=sip:[email protected]
20 Mar 2014 10:53:27 INFO APPLICATION:CLogonSession::setNewActualState() state=1
20 Mar 2014 10:53:27 INFO UcClientStateManager: New UI State: ActualState = IsSigningIn DesiredState = BeSignedOut DataAvailable = false
20 Mar 2014 10:53:27 INFO TRANSPORT:<SentRequest>
20 Mar 2014 10:53:27 INFO TRANSPORT:To:https://lyncdiscover.lynctest.golomtbank.com?sipuri=sip:[email protected]
20 Mar 2014 10:53:27 INFO TRANSPORT:HttpHeader:Accept application/vnd.microsoft.rtc.autodiscover+xml;v=1
20 Mar 2014 10:53:27 INFO TRANSPORT:
20 Mar 2014 10:53:27 INFO TRANSPORT:</SentRequest>
20 Mar 2014 10:53:27 INFO TRANSPORT:Sending request(UcwaAutoDiscoveryRequest) to server type = 0
20 Mar 2014 10:53:27 VERBOSE HttpConnection: post request: https://lyncdiscover.lynctest.golomtbank.com?sipuri=sip:[email protected]
20 Mar 2014 10:53:27 VERBOSE HttpConnection: send request: https://lyncdiscover.lynctest.golomtbank.com?sipuri=sip:[email protected]
20 Mar 2014 10:53:27 INFO APPLICATION:LogonSession::signIn() succeeded
20 Mar 2014 10:53:27 INFO UcClientStateManager: New UI State: ActualState = IsSigningIn DesiredState = BeSignedIn DataAvailable = false
20 Mar 2014 10:53:27 VERBOSE ActivityMonitor: Activity Create: com.microsoft.office.lync.ui.options.SigningInActivity
20 Mar 2014 10:53:27 VERBOSE ActivityMonitor: Activity Start: com.microsoft.office.lync.ui.options.SigningInActivity
20 Mar 2014 10:53:27 VERBOSE ActivityMonitor: Activity Stop: com.microsoft.office.lync.ui.options.CredentialsActivity
20 Mar 2014 10:53:27 VERBOSE ActivityMonitor: Activity Destroy: com.microsoft.office.lync.ui.options.CredentialsActivity
20 Mar 2014 10:55:33 INFO APPLICATION:Called signOut() in state 1
20 Mar 2014 10:55:33 INFO APPLICATION:Cancelling all requests
20 Mar 2014 10:55:33 INFO APPLICATION:Serialized sipuri=sip:[email protected] intUcwa= extUcwa= intADRoot= extADRoot= location=1 networkType=1
20 Mar 2014 10:55:33 INFO APPLICATION:Storing 2 out-of-sync components took 31ms
20 Mar 2014 10:55:33 INFO APPLICATION:Timer cancelled. OnResume = 0
20 Mar 2014 10:55:33 INFO APPLICATION:CLogonSession canceling all requests
20 Mar 2014 10:55:33 INFO APPLICATION:CLogonSession::setNewActualState() state=0
20 Mar 2014 10:55:33 INFO UcClientStateManager: New UI State: ActualState = IsSignedOut DesiredState = BeSignedOut DataAvailable = false
20 Mar 2014 10:55:34 INFO APPLICATION:Timer cancelled. OnResume = 0
20 Mar 2014 10:55:34 INFO APPLICATION:Storing 1 out-of-sync Object Models took 22ms
20 Mar 2014 10:55:34 VERBOSE ActivityMonitor: Activity Create: com.microsoft.office.lync.ui.options.CredentialsActivity
20 Mar 2014 10:55:34 VERBOSE ActivityMonitor: Activity Start: com.microsoft.office.lync.ui.options.CredentialsActivity
20 Mar 2014 10:55:34 VERBOSE ActivityMonitor: Activity Stop: com.microsoft.office.lync.ui.options.SigningInActivity
20 Mar 2014 10:55:34 VERBOSE ActivityMonitor: Activity Destroy: com.microsoft.office.lync.ui.options.SigningInActivity
20 Mar 2014 10:55:41 VERBOSE ActivityMonitor: Activity Create: com.microsoft.office.lync.ui.options.CredentialsOptionsActivity
20 Mar 2014 10:55:41 VERBOSE ActivityMonitor: Activity Start: com.microsoft.office.lync.ui.options.CredentialsOptionsActivity
20 Mar 2014 10:55:41 VERBOSE ActivityMonitor: Activity Stop: com.microsoft.office.lync.ui.options.CredentialsActivity
20 Mar 2014 10:55:42 INFO APPLICATION:CMcxDataSynchronizer now in mode 1
20 Mar 2014 10:55:42 INFO APPLICATION:Mode 1 scheduled to timeout in 30.000000s
20 Mar 2014 10:55:42 INFO APPLICATION:No SendUpdate schedule action. timerStarted=0, timerNeedsToRun=0, channelState=0, timerAction=0
20 Mar 2014 10:55:42 VERBOSE ActivityMonitor: Activity Create: com.microsoft.office.lync.ui.options.AboutActivity
20 Mar 2014 10:55:42 VERBOSE ActivityMonitor: Activity Start: com.microsoft.office.lync.ui.options.AboutActivity
20 Mar 2014 10:55:43 VERBOSE ActivityMonitor: Activity Stop: com.microsoft.office.lync.ui.options.CredentialsOptionsActivity
Also I tested web services by web browser and they seem fine. I cannot find what's wrong with this. Please help me dears.
Thank you

The ports will be visible in the Netstat result after a connection has been setup by a mobile device.
For details, you can check http://www.lync-blog.nl/?p=671&lang=en
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Please follow the follow blog to troubleshoot external Lync Mobility connectivity issue step by step:
http://blogs.technet.com/b/nexthop/archive/2012/02/21/troubleshooting-external-lync-mobility-connectivity-issues-step-by-step.aspx
Lisa Zheng
TechNet Community Support

Lync Mobile 2013 not connected.

Hello Guys
I have the following problem with Lync Mobile 2013 ):
- I have running Lync 2013 Standard and configure Lync Mobile for Internal/External Link. When a user need to connect to internal lync with Wifi Connection, the connection is not established. Internal dns records for the url webapps.domain.net and also to
lyncdiscovery.domain.net were created but until now the mobiles are trying to connect for some time without success.
We reviewed the step without finding a solution to the problem of mobiles procedures.
Could someone tell me or help to solve this problem, because I stopped in this detail. We are not using TMG to publish internally and the firewall has open ports on our LAN.
Thanks for your help

For internal access, you will need lyncdiscoverinternal.domain.com an a redirect through your reverse proxy.
Here is a good link from Jeff Schertz:
http://blog.schertz.name/2013/07/understanding-lync-2013-mobility/
regards Holger Technical Specialist UC

Can't send im to lync mobile client after a period of chating

Thanks for your help first.
I'm setting Lync 2013 server, all internal lan function are working fine, except mobile client.
I've setup edge, reverse proxy (using IIS), FE, BE server.
For IM between between desktop lync client, it is working fine.
For IM between mobile lync client and mobile client with desktop lync cleint, I found the following issue:
- between mobile lync client and lync desktop client: The IM function is working sent between both party, no matter it is initial send from mobile or desktop client, but after a random period of time, may be 5 mins or 7 mins or 10 mins, the desktop client
will not able to send IM to the mobile client but the mobile client still able to send IM to desktop client.
- for between lync mobile client
the issue as above.
- between desktop lync client
no such issue found
I've trouble shoot this issue a lot but still can't the root cause?
Do you have any idea?
Many thanks for your help?
I know that when I testing using my mobile phone, my 3G network provider will continuous change my mobile ip address after a period time, does this behaviour will affect Lync server to find the mobile device?
are there any method will Lync server know what the mobile client status and ip address that let Lync server can find the mobile device effectively?
Patrick

I know that when I testing using my mobile phone, my 3G network provider will continuous change my mobile ip address after a period time, does this behaviour will affect Lync server to find the mobile device?
Hi,
Would you please tell us which edition of mobile did you use (Android, IOS or Windows Phone)?
As IPhone and Windows Phone need push notification function but Android Phone doesn’t need.
If possible, you can test with two Android Phone to check if the issue happen with push notification function.
From your description above, it seems that you use 3G network on mobile to connect Lync mobile client. Please check if the issue cause by IP address of mobile, you can change network to a WIFI to have a test.
Also, please double check if the needed ports open as Edwin provided above.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Telephone numbers (officePhone and homePhone) are missing in a contact card in a Lync Server 2013-based Lync mobile client

In my opinion, the error has not completely fixed in KB2967628. After I install the latest November 2014 cumulative
update. I see the following behavior. User A searches for user B. User B never sign in to the Link. There are three fields in the active directory for User B: officePhone, mobilePhone and homePhone (these fields contain different numbers). When searching on
the mobile client (Android/IOS) for user B – as result user A see only mobile number. If User B At least once will go to Link (sign in) when his search will work, (find officePhone). If User B will change, the privacy settings for user A is in the search will
be displayed homePhone field.
On the Desktop client,
I can find all the fields without those actions performed in the example. If I make a request
to the service UCWA manually like this (below
the text) before
actions, which I performed in example, I did not receive officePhone and homePhone – only mobilePhone field.
GET "https://lync.domainname:443/ucwa/oauth/v1/applications/XXXX/people/search?query=$usename$&limit=200" -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: $USENAMETOKEN$"

Hi,
Based on your description, I’m sorry I’m a little confused about the following you mentioned. I understand the issue is we can only see the mobile number in the contact card on Lync mobile client and that we can search for users based on their office number,
we can see the home phone field in the contact card but there isn’t number showing. I anything I have misunderstood, please feel free to let us know.
“When searching on the mobile client (Android/IOS) for user B – as result user A see only mobile number. If User B At least once will go to Link (sign in) when his search will work, (find officePhone). If User B will
change, the privacy settings for user A is in the search will be displayed homePhone field.”
According to the KB29677628, this issue is caused by UCWA only sending the work number, and we need to install the update for web components server
http://support.microsoft.com/kb/2967628/en-us
August 2014 Cumulative Update 5.0.8308.738 for Lync Server 2013, web components server
https://support.microsoft.com/kb/2937297/en-us?wa=wsignin1.0
Could you please run the following command to check if the web components server version is
5.0.8308.738?
Get-WmiObject
–query 'select * from win32_product' | where {$_.name
–like "Microsoft Lync Server*"} | ft Name, Version
–AutoSize >c:\User\name\Desktop\version.txt
Best Regards,
Cindy

Prevent external calls from Lync mobile

I would like to allow people from my compagny to use lync mobile but I don't want them to call external number from lync mobile. ( for cost reasons, in order to avoid phone call initialisation from the compagny)
some precisions:
We are using lync 2010.
All people have a lync account and can call external number from their lync desktop.
So is there a mean to prevent people calling external number from lync mobile?
Thank you

Hi,
Agree with Anthony, If EnableMobility is set to True and EnableOutsideVoice is set to False, the user can run Lync Mobile but will not be able to use Call via Work.
Please make sure when you running the cmdlet you are a member of
RTCUniversalServerAdmins
More details:
http://technet.microsoft.com/en-us/library/hh690021.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync mobile app will not launch after upgrade to lollipop on HTC One (M8)

Lync mobile app will not launch after upgrade to lollipop on HTC One (M8). Is this a known issue or is a fix available?

Hi THGutz,
Did you install the latest version of Lync for Android ?
The current version of Lync for Android is
5.5.3.8935.
I don’t test it on M8, but on other Android 5.0 devices it works fine.
Best regards,
Eric
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Allowing Lync Mobility Access for AD Group

Is there any way to allow the Lync 2010 Mobility access to specific AD Group. Exp. once i add the users to group then they should get Lync Mobility access.
Please advice
Kris

I thought about this a bit more, if you had a scheduled task, you'd also want the inverse. You'd want to turn the policy off for users pulled out of the group. I wrote this up:
http://www.lyncfix.com/?p=574
Of course, the tricker you get, the more you'll probably want a full script. But, here's a command that would take "Your Group" and if a Lync user is not a member, it would set the MobilityDisabled policy. If they are a member, it would
set the MobilityEnabled policy. If you'd rather user the global policy instead of MobilityDisabled, you could set the policy to $null instead.
Get-CsUser | ForEach {$myuser=$_;if (-not (Get-ADGroupMember “Your Group” | Where { $_.samaccountname -eq $myuser.samaccountname } )) { Grant-CsMobilityPolicy $myuser.identity -policyname “MobilityDisabled“} else {Grant-CsMobilityPolicy $myuser.identity -policyname “MobilityEnabled“}}
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

How to disable the prompt for password when receiving a call on Lync mobile on iPhone

We are doing a pilot on Lync 2013. We have mobile phones: i Phones.
When we are receiving a call, we are prompted to enter password to take the call, which in certain cases, might be a real irritant. Is there a way to bypass, or simply removing this prompt?

I am not aware of any password to receive calls (and certainly there's no option I am aware of within Lync mobility policy settings)
Is this a phone password (i.e. such as the PIN code) or do you enter your AD password?
If it's the phone password then you can turn it off through Settings > Passcode, unless it set by company policy (i.e through ActiveSync policies in which case this is set through Exchange). Bear in mind that if it is your phone password then you'll have
no security on your phone.
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
Georg Thomas | Lync MVP
Blog www.lynced.com.au | Twitter
@georgathomas
Lync Edge Port Check (Beta)

Change the ring tone on Lync Mobile 2013

Is there any way to change the ringtone played by the mobile device when a VoIP call comes in to the Lync 2013 mobile device client?
There doesn't appear to be any option within the mobile client to set this. The device in question is iPhone, however I would be interested to see if it is possible to change it on Android and WP clients too.

Hi,
There is no way to change the ringtone played on the lync mobile.
Kent Huang
TechNet Community Support

Lync Mobile unable to sign in using IIS ARR

We have a deployment which currently has no issues using an Apache reverse proxy running on Ubuntu. I am working on switching over to a supported reverse proxy, so IIS ARR is the obvious choice. I have configured IIS ARR by following the steps at:
http://uclobby.com/2013/08/02/configuring-arr-for-lync-server/
http://blogs.technet.com/b/nexthop/archive/2013/02/19/using-iis-arr-as-a-reverse-proxy-for-lync-server-2013.aspx
When I try to sign on externally using Lync 2013 Mobile, I get a message saying "An unknown error occured". The Lync Mobile logs show the following error:
Caused by: java.net.ConnectException: failed to connect to /xxx.xxx.xxx.xxx (port 443) after 60000ms: isConnected failed: ECONNREFUSED (Connection refused)
I have even gone as far as opening all the ports to the IIS ARR server on the firewall and disabling Windows firewall on everything.

To fix issue "502 - Web server received an invalid response while acting as a gateway or proxy server.", you can refer below link
http://support.microsoft.com/kb/2455129/en-us
it's assume reverse proxy configuration issue, please check the following things:
Please make sure your internal web service url and external web service url are not pointed to the same FQDN.
Verify you have update the public certifcates including lyncautodiscover URL in the SAN entries for your reverse proxy server
Check the authenticated delegation is set to "No delegation, but clients may authenticate directly"
Please try to enable internal access and see if it works
If still no luck,please enable Lync server logging tool and reproduce the issues,then use snooper to analyze the log for more specific information
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical

Lync Mobility, lyncdiscoverinternal or lyncdiscover

Similar Messages

Maybe you are looking for