Differences & Similarities between Lync 2013 desktop & Lync 2013 mobile

We've got Lync 2013 installed on our desktops. We now want to introduce Lync 2013 for both iPhone's and Android's.
Is there anywhere I can get a list of what functionality the desktop & mobile versions share, as well as what they don't.
If this is in the wrong place, apologies.
Duncan

Sorry, just found the information.
Guess I didn't look very well in the first place. :(

Similar Messages

What port number for Desktop Sharing using in Lync Server 2013 and Lync Online

Dear All,
My environment using Lync Server 2013 and Lync online on Office 365. I don't want my user using Desktop Sharing feature. then I need to know what port number for Desktop Sharing using in Lync Server 2013 and Lync Online.
I will deny this port on personal firewall each client.
Thank you for your advise.

Hi,
I'm not sure you'd be able to do this with ports without impacting other application sharing features such as Q&A, Whiteboard, Poll etc - I'm pretty sure they all come under the same umbrella of ClientAppSharing.
Ordinarily you would create or modify your conferencing policy to restrict sharing to single programs only using a cmdlet similar to below;
Set-CsConferencingPolicy -Identity "Global" -EnableAppDesktopSharing SingleApplication
This would disable desktop sharing but enable users to continue sharing other single programs. If you want to remove that functionality too, then replace the 'SingleApplication' parameter with 'None'. Then users won't be able to share any programs either.
This is the correct way to do it as the icons will be greyed out for the users. Doing it your way, they would still be able to click them, and it would throw an error - this will lead to a lot more support calls and people assuming a service is broken.
I hope that helps some.
Kind regards
Ben

External Meetings using Lync Web App vs Lync 2013 Desktop client

We have LYNC Server 2013 deployed on premise. Our clients are LYNC 2013. When someone external to our organization sends us a Lync meeting request we are able to connect with our Lync 2012 desktop client but only Audio is available. We cannot share
the desktop. If however we connect to the external meeting using the Lync Web App (by specifying
?sl=1 at the end of the meeting url) we are able to use all the services like audio, desktop sharing etc.
I've found the following articles that suggest that the desktop clients are not the preferred choice to connect to external meetings.
http://blog.schertz.name/2011/11/forcing-lync-web-app/
http://www.computer-talk.com/en/blog/item/attendees-cannot-join-your-lync-web-conference
Can anyone advise as to why the desktop clients are restrictive and if there is a fix and if not how can we force users to use the Lync Web App to connect to external meetings?
Our lync 2013 desktop clients use the following ports:
PS C:\Users\am03744ad> Get-CsConferencingConfiguration
Identity                           : Global
MaxContentStorageMb                : 500
MaxUploadFileSizeMb                : 500
MaxBandwidthPerAppSharingServiceMb : 375
ContentGracePeriod                 : 15.00:00:00
ClientMediaPortRangeEnabled        : True
ClientMediaPort                    : 5350
ClientMediaPortRange               : 40
ClientAudioPort                    : 50020
ClientAudioPortRange               : 20
ClientVideoPort                    : 58000
ClientVideoPortRange               : 20
ClientAppSharingPort               : 42000
ClientAppSharingPortRange          : 20
ClientFileTransferPort             : 42020
ClientFileTransferPortRange        : 20
ClientSipDynamicPort               : 7100
ClientSipDynamicPortRange          : 3
Organization                       :
HelpdeskInternalUrl                :
HelpdeskExternalUrl                :
ConsoleDownloadInternalUrl         :
ConsoleDownloadExternalUrl         :

You should be fine using the full Lync client, it's not restricted by default. If there's an issue, it's typically in the networking related to your edge, or the edge of the organization you're federating with.
The reason the web client is preferred by many (not all, and that's not an official Microsoft stance), is simply that if everyone uses the web client, it's a consistent experience for the attendees and you don't have to worry about the status of attendee's Lync
environment or federation.
Can your external users share a desktop with internal users? Can they do it externally in a conference hosted by you? Can the remote organization share desktops with you when connected to your conferences? And in these conferences,
have the marked you as presenter so you can present your desktop?
There's no good way to automatically force users to use the web app each time unfortunately. The other organization would need to hardcode that ?sl=1 into each meeting invite sent.
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

Lync 2013 desktop usesr and Lync Web users.

When i send IM to users within my group using Lync 2013 desktop client, the recipients on Lync Web app does not get my font color or font syle. Is there settings to get the font color and font style I use on the desktop client to appear in the Lync
web app users windows as I send it over.

Hi,
I test in my Lync environment but didn’t find the issue. As Anthony said, there is no set except the setting “Change Font…” on Lync client Options. You can try to download the latest version for Lync client from Microsoft Website
and then test again.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

EWS not deployed anymore to Lync 2013 Desktop Clients, Mobile Clients still working fine

Hello dear community,
the subject of EWS in conjunction with Lync 2013 has been discussed a lot here .
However, I could not find here any solution for my problem and I'm (almost) at my end.
Following scenario - 1 x Lync 2013 BE server, 1 x Lync 2013 Edge server, 1 x reverse proxy (IIS ARR). This Lync 2013 deployment
was installed about two months ago and integrated into existing IT landscape. Everything worked wonderfully - desktop and mobile clients were able to connect from inside and outside our organization, EMS was deployed to both desktop and mobile clients.
After that there are no any configuration changes made on Lync server, and yesterday, shortly before an important presentation
I've found, that EWS is not deployed anymore on all desktop clients. Mobile clients, however, continue to function smoothly.
I have tried the following: restart Lync and reverse proxy servers - without success, Lync Connectivity Analyzer shows all
green (internal and external), all relevant tests with Microsoft Remote Connectivity Analyzer were passed, also analysis using Wireshark brought nothing.
I must to say that a week ago I installed SP3 for Exchange 2010 - can it may be because? Also appears more
times a day the following error message in Event Viewer on the back-end server (language of operation system is German):
Protokollname: Lync Server
Quelle:        LS Storage Service
Datum:         05.12.2013 19:23:14
Ereignis-ID:   32054
Aufgabenkategorie:(4006)
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      SERVER-11.Speedpoint.local
Beschreibung:
EWS-AutoErmittlungsfehler im Speicherdienst.
ExchangeAutodiscoverException: code=ErrorEwsAutodiscover, reason=GetUserSettings
failed, smtpAddress = xxx, Autodiscover Uri=https://autodiscover.xxx.de/autodiscover/autodiscover.svc, Autodiscover WebProxy=<NULL> ---> Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed.
Das Stammelement ist nicht vorhanden. ---> System.Xml.XmlException: Das Stammelement ist nicht vorhanden.
   bei System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
   bei System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   bei System.Xml.XmlCharCheckingReader.Read()
   bei Microsoft.Exchange.WebServices.Data.EwsXmlReader.Read()
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetUserSettings(List`1 smtpAddresses, List`1 settings, Nullable`1 requestedVersion, Uri& autodiscoverUrl)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetSettings[TGetSettingsResponseCollection,TSettingName](List`1 identities, List`1 settings, Nullable`1 requestedVersion, GetSettingsMethod`2 getSettingsMethod, Func`1 getDomainMethod)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(List`1 smtpAddresses, List`1 settings)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetSoapUserSettings(String smtpAddress, List`1 requestedSettings)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(String userSmtpAddress, UserSettingName[] userSettingNames)
   bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
   --- End of inner exception stack trace ---
   bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
   bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.GetUserEwsSettings(StoreContext ctx, String smtpAddress, CacheMode cacheMode)
Ursache: Der AutoErmittlungs-URI war nicht richtig konfiguriert oder nicht erreichbar. Eventuell besteht ein Problem mit dem Proxy, oder andere Fehler liegen
vor.
Lösung:
Überprüfen Sie die Ereignisdetails. Überprüfen Sie, ob der URI des AutoErmittlungsdiensts ordnungsgemäß konfiguriert und erreichbar ist. Prüfen Sie, ob die Proxyeinstellungen ordnungsgemäß konfiguriert sind und der Proxy erreichbar ist. Prüfen Sie die Konfiguration
der AutoErmittlung zwischen Lync und Exchange Autodiscovery anhand des Handbuchs zur Problembehandlung. Wenn das Problem weiterhin besteht, wenden Sie sich mit den Ereignisdetails an das Supportteam Ihrer Organisation.
Ereignis-XML:
< Event xmlns="">
<System>
    <Provider Name="LS Storage Service" />
    <EventID Qualifiers="53158">32054</EventID>
    <Level>2</Level>
    <Task>4006</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-12-05T18:23:14.000000000Z" />
    <EventRecordID>19949</EventRecordID>
    <Channel>Lync Server</Channel>
    <Computer>SERVER-11.Speedpoint.local</Computer>
    <Security />
</System>
<EventData>
    <Data>ExchangeAutodiscoverException: code=ErrorEwsAutodiscover, reason=GetUserSettings failed, smtpAddress=xxx, Autodiscover Uri=https://autodiscover.xxx.de/autodiscover/autodiscover.svc, Autodiscover WebProxy=<NULL> --->
Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed.
Das Stammelement ist nicht vorhanden. ---> System.Xml.XmlException: Das Stammelement ist nicht vorhanden.
   bei System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
   bei System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   bei System.Xml.XmlCharCheckingReader.Read()
   bei Microsoft.Exchange.WebServices.Data.EwsXmlReader.Read()
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetUserSettings(List`1 smtpAddresses, List`1 settings, Nullable`1 requestedVersion, Uri& autodiscoverUrl)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetSettings[TGetSettingsResponseCollection,TSettingName](List`1 identities, List`1 settings, Nullable`1 requestedVersion, GetSettingsMethod`2 getSettingsMethod, Func`1 getDomainMethod)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(List`1 smtpAddresses, List`1 settings)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetSoapUserSettings(String smtpAddress, List`1 requestedSettings)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(String userSmtpAddress, UserSettingName[] userSettingNames)
   bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
   --- End of inner exception stack trace ---
   bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
   bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.GetUserEwsSettings(StoreContext ctx, String smtpAddress, CacheMode cacheMode)
< /Data>
</EventData>
< /Event>
However Event ID
32054
was actually
always there
– even
when everything
worked fine -
but with
some another content.
That's why I
don't know
if I
should take it seriously.
Thanks a lot in advance for your help!

Hi MiF,
The issue may cause by the Network Service account that the Lync Storage Service uses does not have access to the private key in used by the oAuth certificate. Please do with the following steps:
Open MMC and add the “Certificates” Snap-in (Local Computer)
Open Personal | Certificates and find the the Certificate being used for OAuth (use the Lync “Get-CsCertificate -Type OAuthTokenIssuer” cmdlet to find the serial number of the OAuth certificate).
Right-click | “All Tasks” | “Manage Private Keys”
Add Permissions for “Network Service” account (the defaults Full control and Read).
Please also check registry key on client computer.
If the HKCU\Software\Microsoft\ Office\15.0\Lync \[User SMTP Address]\Autodiscovery registry key does not exist on the user’s workstation, then it likely means that one of the following failures
have occurred:
Lync was unable to locate a valid DNS A record or SRV record for the Autodiscover site
Certificate assigned to Autodiscover site is not trusted by the Lync workstation
More details:
http://www.microsoft.com/en-in/download/confirmation.aspx?id=15668
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Move user between two pool in Lync 2013

after Adding Your Second Lync Standard Edition Server 2013 & Creating an Associated Backup Pool for Resiliency, when i am log in to Lync Server Control Panel when go to Once the LSCP is open well click Users | Find | Select [email protected]
| Action .
I cant see Move Selected Users to Pool… |
what do i do?
help

Hi,
Please check if CMS replication update to the latest status with the following cmdlet:
Get-CsManagementStoreReplicationStatus. If the status not to the latest status, you can invoke by the following cmdlet:
Invoke-CsManagementStoreReplication
Also, you can temporary use Windows PowerShell cmdlets to move users from one pool to another.
More details you can refer to the part of “To move users from one pool to another using Windows PowerShell cmdlets” below:
http://technet.microsoft.com/en-us/library/gg182600.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Persistent Chat (Lync Server 2013) with Lync 2010 Group Chat

I have successfully deployed Lync Server 2013 and both 2013 and 2010 desktop clients connect and function as expected.
The problem is with Persistent Chat. It works perfectly with the 2013 desktop client but - whilst 2010 Group Chat connects - I receive the error message "The [LOGON_DOMAIN] is not available". No chat rooms are available and I am unable to search.
I have been unable to locate anything on the web which discusses the problem.
I do not know whether this makes a difference but the 2010 clients use terminals rather than dedicated workstations.
Can anyone shed any light on what the problem may be?

Have you created a CsPersistentChatEndpoint to allow the Group Chat client (2010) to connect to Persistent
Chat server? Please take a look at: http://technet.microsoft.com/en-us/library/jj204901.aspx
Please mark posts as answers/helpful if it answers your question.
Blog
Lync Validator - Used to assist in the validation and documentation of Lync Server 2013.

Lync 2013 for iPad & Windows Mobile Sign in Issue

Hi,
I hope someone can help with a very frustrating issue I'm having with Lync 2013 on iOS & Windows Mobile - it won't sign in with an error message saying 'We can't sign you in. Please check your account info and try again'
I know my account info is right as I use it to sign in to the desktop client when working remotely, and it also works fine on an Android client.
The Lync remote connectivity analyser passes all the tests, I can get to the xml file using https://lyncdiscover.domain.org/autodiscover/autodiscoverservice.svc/root from a laptop, but from the iPad it's just a blank screen.
I've tried using auto detect, and entering details manually, but still no luck. I'm completely stumped. I've trawled blogs, form posts etc, but nothing. HELP!!!
Some details - we have a FE server, and an Edge Server, both running Lync 2013 with latest updates. We use nGinX as the RP and that all seems to be fine. It just doesn't want to authenticate me (or anyone else).
See below part of log file from my iPad that shows an error on the FE server.
</SentRequest>
2014-03-07 08:19:36.200 Lync[1615:74c6000] INFO UTILITIES CHttpStreamPool.cpp/409:Allocating stream 0x589d0a0 for url - http://lyncdiscover.domain.org/ with persistent id as 7
2014-03-07 08:19:36.200 Lync[1615:74c6000] VERBOSE TRANSPORT CHttpProxyHelper.cpp/436:CHttpProxyHelper::discoverProxy : No proxy found for url http://lyncdiscover.domain.org/. Sending over direct connection.
2014-03-07 08:19:36.200 Lync[1615:74c6000] INFO TRANSPORT CHttpStreamPool.cpp/556:Not setting TLS as the url(http://lyncdiscover.domain.org/) is not https
2014-03-07 08:19:36.205 Lync[1615:3bc6218c] INFO UI CMConversationCommon.mm/43:not signed in
2014-03-07 08:19:36.206 Lync[1615:3bc6218c] INFO UI CMConversationCommon.mm/43:not signed in
2014-03-07 08:19:36.206 Lync[1615:3bc6218c] INFO UI CMConversationCommon.mm/43:not signed in
2014-03-07 08:19:36.206 Lync[1615:3bc6218c] INFO UI CMConversationCommon.mm/43:not signed in
2014-03-07 08:19:36.206 Lync[1615:3bc6218c] INFO UI CMConversationCommon.mm/43:not signed in
2014-03-07 08:19:36.595 Lync[1615:74c6000] INFO UTILITIES CHttpConnection.cpp/577:Received kCFStreamEventEndEncountered (UcwaAutoDiscoveryRequest)isHeadersAvailable = true responseHeadersHandle = 58b1930
2014-03-07 08:19:36.596 Lync[1615:74c6000] INFO UTILITIES CHttpConnection.cpp/651:Response status = 200 for request UcwaAutoDiscoveryRequest
2014-03-07 08:19:36.597 Lync[1615:74c6000] INFO UTILITIES CHttpStreamPool.cpp/455:Scheduling stream 0x58812c0 for release.
2014-03-07 08:19:36.597 Lync[1615:74c6000] INFO TRANSPORT CHttpRequestProcessor.cpp/173:Received response of request(UcwaAutoDiscoveryRequest) with status = 0x0
2014-03-07 08:19:36.598 Lync[1615:74c6000] INFO TRANSPORT TransportUtilityFunctions.cpp/925:<ReceivedResponse>
GET https://lyncdiscover.domain.org/?sipuri=sip:[email protected]
Request Id: 0x11d4988
HttpHeader:Cache-Control no-cache
HttpHeader:Connection keep-alive
HttpHeader:Content-Length 1025
HttpHeader:Content-Type application/vnd.microsoft.rtc.autodiscover+xml; v=1
HttpHeader:Date Fri, 07 Mar 2014 08:19:34 GMT
HttpHeader:Expires -1
HttpHeader:Pragma no-cache
HttpHeader:Server nginx/1.4.1
HttpHeader:StatusCode 200
HttpHeader:X-AspNet-Version 4.0.30319
HttpHeader:X-Content-Type-Options nosniff
HttpHeader:X-MS-Server-Fqdn KPPLYN04.ad.domain.org
HttpHeader:X-Powered-By ASP.NET
Ôªø<?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://extwebsvc01.domain.org/Autodiscover/AutodiscoverService.svc/root/domain?originalDomain=domain.org" /><Link token="User" href="https://extwebsvc01.domain.org/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=domain.org"
/><Link token="Self" href="https://extwebsvc01.domain.org/Autodiscover/AutodiscoverService.svc/root?originalDomain=domain.org" /><Link token="OAuth" href="https://extwebsvc01.domain.org/Autodiscover/AutodiscoverService.svc/root/oauth/user?originalDomain=domain.org"
/><Link token="External/XFrame" href="https://extwebsvc01.domain.org/Autodiscover/XFrame/XFrame.html" /><Link token="Internal/XFrame" href="https://ly13webpool.ad.domain.org/Autodiscover/XFrame/XFrame.html"
/><Link token="XFrame" href="https://extwebsvc01.domain.org/Autodiscover/XFrame/XFrame.html" /></Root></AutodiscoverResponse>
</ReceivedResponse>
2014-03-07 08:19:36.599 Lync[1615:74c6000] INFO TRANSPORT CUcwaAutoDiscoveryResponse.cpp/119:location value is external
2014-03-07 08:19:36.600 Lync[1615:74c6000] INFO TRANSPORT CUcwaAutoDiscoveryResponse.cpp/195:User url is https://extwebsvc01.domain.org/autodiscover/autodiscoverservice.svc/root/user?originaldomain=domain.org
2014-03-07 08:19:36.601 Lync[1615:74c6000] INFO TRANSPORT CHttpRequestProcessor.cpp/266:Sending event to main thread for request(0x11d4988)
2014-03-07 08:19:36.602 Lync[1615:3bc6218c] INFO APPLICATION CTransportRequestRetrialQueue.cpp/822:Req. completed, Stopping timer.
2014-03-07 08:19:36.602 Lync[1615:3bc6218c] INFO APPLICATION CUcwaAutoDiscoveryGetUserUrlOperation.cpp/290:Received a root response
2014-03-07 08:19:36.602 Lync[1615:3bc6218c] INFO APPLICATION CUcwaAutoDiscoveryGetUserUrlOperation.cpp/224:UcwaAutoDiscoveryGetUserUrlOperation completed with url = https://lyncdiscover.domain.org/?sipuri=sip:[email protected], userUrl = https://extwebsvc01.domain.org/autodiscover/autodiscoverservice.svc/root/user?originaldomain=domain.org,
status = S_OK (S0-0-0)
2014-03-07 08:19:36.603 Lync[1615:3bc6218c] INFO APPLICATION CTransportRequestRetrialQueue.cpp/725:Response received for req. GET-UnAuthenticatedGet(0x11d4988): S_OK (S0-0-0) (Success); Done with req.; Stopping resend timer
2014-03-07 08:19:36.603 Lync[1615:3bc6218c] INFO APPLICATION CTransportRequestRetrialQueue.cpp/399:Cancelling all requests
2014-03-07 08:19:36.603 Lync[1615:3bc6218c] INFO APPLICATION CTransportRequestRetrialQueue.cpp/409:Cancelling request: 0x1124488
2014-03-07 08:19:36.604 Lync[1615:3bc6218c] INFO TRANSPORT CSessionBase.hxx/158:Cancelling request: 0x1124488
2014-03-07 08:19:36.604 Lync[1615:3bc6218c] INFO TRANSPORT CTransportThread.cpp/163:Added Request(UcwaAutoDiscoveryRequest) to Request Processor queue
2014-03-07 08:19:36.604 Lync[1615:3bc6218c] INFO APPLICATION CUrlRedirectAndTrustResolver.cpp/610:UrlRedirectAndTrustResolver complete with url = http://lyncdiscover.domain.org/, Hops = 1, status = W_Cancelled (W0-0-6)
2014-03-07 08:19:36.605 Lync[1615:74c6000] INFO TRANSPORT CTransportThread.cpp/343:Sent Request(UcwaAutoDiscoveryRequest) to Request Processor
2014-03-07 08:19:36.605 Lync[1615:3bc6218c] INFO APPLICATION CUcwaAutoDiscoveryGetUserUrlOperation.cpp/224:UcwaAutoDiscoveryGetUserUrlOperation completed with url = http://lyncdiscover.domain.org/?sipuri=sip:[email protected], userUrl = , status = W_Cancelled
(W0-0-6)
2014-03-07 08:19:36.605 Lync[1615:74c6000] INFO UTILITIES CHttpStreamPool.cpp/455:Scheduling stream 0x589d0a0 for release.
2014-03-07 08:19:36.606 Lync[1615:3bc6218c] INFO TRANSPORT CCredentialManager.cpp/176:getSpecificCredential for serviceId(1) returning: credType (1) signInName ([email protected]) domain (ad) username (ab00wk) password.empty() (0) certificate.isValid() (0)
privateKey.empty() (1) compatibleServiceIds(1)
2014-03-07 08:19:36.606 Lync[1615:3bc6218c] INFO TRANSPORT CMetaDataManager.cpp/403:Received a request to get the meta data of type 0 for url https://extwebsvc01.domain.org/autodiscover/autodiscoverservice.svc/root/user?originaldomain=domain.org
2014-03-07 08:19:36.606 Lync[1615:3bc6218c] INFO TRANSPORT CMetaDataManager.cpp/467:Sending Unauthenticated get to get the web-ticket url
2014-03-07 08:19:36.607 Lync[1615:3bc6218c] INFO TRANSPORT CTransportThread.cpp/131:Added Request() to Request Processor queue
2014-03-07 08:19:36.607 Lync[1615:3bc6218c] INFO TRANSPORT CAuthenticationResolver.cpp/108:Waiting on Meta Data from https://extwebsvc01.domain.org/autodiscover/autodiscoverservice.svc/root/user?originaldomain=domain.org
2014-03-07 08:19:36.607 Lync[1615:6081000] INFO TRANSPORT CTransportThread.cpp/343:Sent Request() to Request Processor
2014-03-07 08:19:36.607 Lync[1615:3bc6218c] INFO APPLICATION CTransportRequestRetrialQueue.cpp/385:Submitting new req. GET-AuthenticatedUserGetRequest(0x11e6bf8)
2014-03-07 08:19:36.608 Lync[1615:6081000] WARNING TRANSPORT CCredentialManager.cpp/317:CCredentialManager::getSpecificCredential returning NULL credential for serviceId (4) type (1)!
2014-03-07 08:19:36.608 Lync[1615:3bc6218c] INFO APPLICATION CUcwaAutoDiscoveryService.cpp/1194:Submitting Authenticated AutoDiscovery request to https://extwebsvc01.domain.org/autodiscover/autodiscoverservice.svc/root/user?originaldomain=domain.org
2014-03-07 08:19:36.609 Lync[1615:6081000] INFO TRANSPORT TransportUtilityFunctions.cpp/631:<SentRequest>
GET https://extwebsvc01.domain.org/autodiscover/autodiscoverservice.svc/root/user?originaldomain=domain.org
Request Id: 0x1124488
HttpHeader:Accept
HttpHeader:X-MS-WebTicket xxxxxxxxxx
</SentRequest>
2014-03-07 08:19:36.609 Lync[1615:3bc6218c] INFO APPLICATION CUcwaAutoDiscoveryService.cpp/1688:Ignoring GetUserUrlOperation event as current state is 6
2014-03-07 08:19:36.610 Lync[1615:3bc6218c] INFO APPLICATION CUcwaAutoDiscoveryService.cpp/1690:Request url was http://lyncdiscover.domain.org/?sipuri=sip:[email protected]
2014-03-07 08:19:36.610 Lync[1615:6081000] INFO UTILITIES CHttpStreamPool.cpp/409:Allocating stream 0x58bf6c0 for url - https://extwebsvc01.domain.org/autodiscover/autodiscoverservice.svc/root/user with persistent id as 15
2014-03-07 08:19:36.610 Lync[1615:6081000] VERBOSE TRANSPORT CHttpProxyHelper.cpp/436:CHttpProxyHelper::discoverProxy : No proxy found for url https://extwebsvc01.domain.org/autodiscover/autodiscoverservice.svc/root/user?originaldomain=domain.org. Sending over
direct connection.
2014-03-07 08:19:36.941 Lync[1615:6081000] INFO UTILITIES CHttpConnection.cpp/577:Received kCFStreamEventEndEncountered (0x%u0x104bc00)isHeadersAvailable = true responseHeadersHandle = 58b6bd0
2014-03-07 08:19:36.942 Lync[1615:6081000] INFO UTILITIES CHttpConnection.cpp/651:Response status = 401 for request 0x%u0x104bc00
2014-03-07 08:19:36.943 Lync[1615:6081000] INFO UTILITIES CHttpConnection.cpp/718:Not send authenticating request(0x%u0x104bc00). isAuthObjectValid - 0, areCredentialsValid - 0, resendRequestCounter - 1
2014-03-07 08:19:36.943 Lync[1615:6081000] INFO UTILITIES CHttpStreamPool.cpp/455:Scheduling stream 0x58bf6c0 for release.
2014-03-07 08:19:36.943 Lync[1615:6081000] INFO TRANSPORT CHttpRequestProcessor.cpp/173:Received response of request() with status = 0x0
2014-03-07 08:19:36.944 Lync[1615:6081000] INFO TRANSPORT TransportUtilityFunctions.cpp/925:<ReceivedResponse>
GET https://extwebsvc01.domain.org/autodiscover/autodiscoverservice.svc/root/user?originaldomain=domain.org
Request Id: 0x1124488
HttpHeader:Cache-Control no-cache
HttpHeader:Connection keep-alive
HttpHeader:Content-Length 1293
HttpHeader:Content-Type text/html
HttpHeader:Date Fri, 07 Mar 2014 08:19:35 GMT
HttpHeader:Server nginx/1.4.1
HttpHeader:StatusCode 401
HttpHeader:X-Content-Type-Options nosniff
HttpHeader:X-MS-Server-Fqdn KPPLYN04.ad.domain.org
HttpHeader:X-MS-WebTicketSupported cwt,saml
HttpHeader:X-MS-WebTicketURL https://extwebsvc01.domain.org/WebTicket/WebTicketService.svc
HttpHeader:X-Powered-By ASP.NET
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<title>401 - Unauthorized: Access is denied due to invalid credentials.</title>
<style type="text/css">

</style>
</head>
<body>
<div id="header"><h1>Server Error</h1></div>
<div id="content">
<div class="content-container"><fieldset>
<h2>401 - Unauthorized: Access is denied due to invalid credentials.</h2>
<h3>You do not have permission to view this directory or page using the credentials that you supplied.</h3>
</fieldset></div>
</div>
</body>
</html>
If you need any further info, please let me know.
Thanks in advance
Aron

Hi,
Did the sip address name match with User Principle Name?
If not, when you enter the login information please also populate the Username filed using the format domainusername and test again.
Here is a blog may help you, it is for Lync server 2010 but similar for Lync server 2013:
http://blogs.perficient.com/microsoft/2011/12/lync-mobility-understanding-sip-sign-in-address-vs-user-principle-name-upn/
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.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Outlook 2013 and Lync 2013 suddenly cannot run at the same time

We recently switched to Office 365 and up until this month's Tuesday Patch Day, everything was working great. As soon as I installed the patches from 3/12/2013. Ever since then I've had the following issue:
Launch Outlook 2013
Launch Lync 2013
Get the following dialog box: "Outlook Data File: The file <filename> is in use and cannot be accessed. Close any application that is using this file, and then try again. You might need to restart your computer."
Click Ok to dismiss the dialog box. Everything seems to function normally.
About three minutes later I get the following dialog box: "We're sorry, but Outlook has run into an error that is preventing it from working correctly. Outlook will need to be closed as a result. Would you like us to repair now?"
Click Close. Everything seems to function normally.
Steps taken to attempt to a fix:
I deleted the Outlook profile and recreated it from scratch. No improvement.
I rebooted the machine. No improvement.
I repaired the Outlook data file. No improvement.
Other notes:
If I start Outlook 2013 by itself, it works fine and no dialog boxes.
If I start Lync 2013 by itself, it works fine and no dialog boxes.

Hi all,
I had the same problem as the original poster, and I fixed it using the method I'm about to describe. First, let me state that I am using a volume-license version of Office 2013 Standard, installed the conventional way ... we are not using the desktop
apps available with Office 365 plans E3+E4 or "Midsize Business".
I had originally installed Lync 2013 using a 'streaming' installer that you find by logging into the Office 365 Portal site -> Office 365 Settings -> Software -> Lync -> Install.
That installer does not work with the version of Office 2013 I'm using. I uninstalled Lync, and reinstalled using the links below:
(32-bit):
http://www.microsoft.com/en-us/download/details.aspx?id=35451
(64-bit):
http://www.microsoft.com/en-us/download/details.aspx?id=35450
The version of Lync that you choose (32-bit or 64-bit) has to match the version of Office 2013 you already have installed. Upon installing the 64-bit version of Lync at the URL above, the error message "Outlook
Data File: The file <filename> is in use and cannot be accessed." disappeared and Outlook and Lync now happily cooperate.

Lync 2010 and Lync 2013 blinking icon in taskbar not working properly

Hi,
We're experiencing a strange behaviour. Lync IM notifications are supposed to work this way below:
1) Notification bubble on the right-bottom corner
2) After a few seconds, a blinking icon in the task bar
3) After a few seconds, a coloured icon remains in the task bar
Some of our users, both Lync 2010 and Lync 2013, go 1) and 2) but then icon won't remain in the task bar, so they don't realize they have a conversation waiting (Windows XP and Windows 7).
If they open the icon, the conversation is there and coloured, and they can answer.
In my computer, it has also happened but most of the time it works fine (testing it, maybe it works 15 times and fails 1). Nevertheless, a lot of people is suffering from this strange behaviour.
We have looked into the causes but haven't found anything.
Any clue?
Thanks!

How long have you seen the problem?
What version of your Lync client? Try to update your Lync client to the latest version.
Try to repair office 2013.
Uninstall and reinstall Lync 2010.
Please install Lync 2013 or Lync 2010 on a fresh installation of Window to check if you can still see this problem.
Lisa Zheng
TechNet Community Support

Lync Online vs Exchange 2013 On Premise

We have Lync 2013 Online and Exchange 2013 SP1/Outlook 2013 SP1 on premise. All work well with RPC over HTTP.
We are trying to get MAPI over HTTP (Outlook 2013 SP1 / Exchange 2013 SP1). But it seems that the MAPI over HTTP no longer respects the Internet Explorer Bypass Proxy List. Therefore the Outlook client tries to connect to the on-premise
Exchange Server CAS via the proxy server. Outlook 2013 Connection status shows DISCONNECTED and AUTHN FAILED.
To reconnect Outlook we can either;
1. Turn off the Proxy Server in IE (Outlook then connects but we cannot browse the web).
2. Remove the Microsoft Online Services assistant (again Outlook then connects, but Lync does not).
To troubleshoot this we've used the Process Monitor and can see Outlook actively reading the registry key (HKCU\software\microsoft\windows\currentversion\internet settings\proxyoverride). Problem is it doesn't appear to use them.
Has anyone else seen this behaviour with MAPI over HTTP and the Online Services Sign In Assistant (MSOIDCLI)?

This is a known issue with MAPI/HTTP at this moment. Outlook Team is investigating it for a root cause & possible fix. No ETA is available at this time. I will update this post when we have an update.
Issue: If an Outlook 2013 SP1+ user has 'Bypass proxy server for local addresses' setting enabled in Internet Explorer (Internet Options | Connections | LAN Settings), then Outlook does not connect over MAPI/HTTP to a mailbox on Exchange
2013 SP1+ server. This issue does not happen connecting over RPC/HTTP in the same setup.
I see another known issue mentioned here thus wanted to quickly confirm that as well. Another known issue with MAPI/HTTP is as described below. This issue has been fixed and fix is planned to be deployed in Office 365/Exchange Online soon & is currently
planned to be included with E2013 SP1 CU6 (tentative).
Issue: User1 has full access to User2’s mailbox, User2 also has an Archive mailbox. Using Outlook 2013 SP1+ User1 connects over MAPI/HTTP to Exchange 2013 SP1+. User2’s Primary mailbox is then accessible to User1 in his Outlook thru Auto-mapping,
but User1 cannot see User2’s Archive mailbox. If User1 connects over RPC/HTTP, he does not see this issue.
Sr. Program Manager, Product Quality, Exchange Client Access Server

Lync 2013 to Exchange 2013 Oauth problem - Error:[OAuthTokenBuilder:GetAppToken] unable to continue building token; no locally configured issuer

Hi,
I am having a problem getting OAuth to work from Exchange 2013 to Lync 2013.
I have read and following the instructions online and cannot see what I am doing wrong.
On the Exchange 2013 server, I get the following error when I run:
Test-OAuthConnectivity -Service EWS -TargetUri
https://exchserver2.domainname.local/ews/ -Mailbox "Jack"
RunspaceId : 920118a3-6ab2-45dc-9b68-de68133de95e
Task : Checking EWS API Call Under Oauth
Detail : The configuration was last successfully loaded at 01/01/0001 00:00:00 UTC. This was 1059263714 minutes
ago.
The token cache is being cleared because "use cached token" was set to false.
Exchange Outbound Oauth Log:
Client request ID: 19ad80f6-7751-429f-aac5-e802105fbbc6
Information:[OAuthCredentials:Authenticate] entering
Information:[OAuthCredentials:Authenticate] challenge from
'https://exchserver2.domainname.local/ews/Exchange.asmx' received: Bearer
client_id="00000002-0000-0ff1-ce00-000000000000",
trusted_issuers="[email protected]",Negotiate,NTLM
Information:[OAuthCredentials:GetToken] client-id: '00000002-0000-0ff1-ce00-000000000000', realm: '',
trusted_issuer: '[email protected]'
Information:[OAuthCredentials:GetToken] start building a token for the user domain 'domainname.co.uk'
Information:[OAuthTokenBuilder:GetAppToken] start building the apptoken
Information:[OAuthTokenBuilder:GetAppToken] checking enabled auth servers
Error:[OAuthTokenBuilder:GetAppToken] unable to continue building token; no locally configured issuer
was in the trusted_issuer list, realm from challenge was also empty. trust_issuers was
[email protected]
Error:The trusted issuers contained the following entries
'[email protected]'. None of them are configured locally.
Exchange Response Details:
HTTP response message:
Exception:
System.Net.WebException: The request was aborted: The request was canceled. --->
Microsoft.Exchange.Security.OAuth.OAuthTokenRequestFailedException: The trusted issuers contained the
following entries '[email protected]'. None of them are
configured locally.
at Microsoft.Exchange.Security.OAuth.OAuthTokenBuilder.GetAppToken(String applicationId, String
destinationHost, String realmFromChallenge, IssuerMetadata[] trustedIssuersFromChallenge, String
userDomain)
at Microsoft.Exchange.Security.OAuth.OAuthTokenBuilder.GetAppWithUserToken(String applicationId,
String destinationHost, String realmFromChallenge, IssuerMetadata[] trustedIssuersFromChallenge, String
userDomain, ClaimProvider claimProvider)
at Microsoft.Exchange.Security.OAuth.OAuthCredentials.GetToken(WebRequest webRequest,
HttpAuthenticationChallenge challengeObject)
at Microsoft.Exchange.Security.OAuth.OAuthCredentials.Authenticate(String challengeString, WebRequest
webRequest, Boolean preAuthenticate)
at Microsoft.Exchange.Security.OAuth.OAuthCredentials.OAuthAuthenticationModule.Authenticate(String
challenge, WebRequest request, ICredentials credentials)
at System.Net.AuthenticationManager.Authenticate(String challenge, WebRequest request, ICredentials
credentials)
at System.Net.AuthenticationState.AttemptAuthenticate(HttpWebRequest httpWebRequest, ICredentials
authInfo)
at System.Net.HttpWebRequest.CheckResubmitForAuth()
at System.Net.HttpWebRequest.CheckResubmit(Exception& e, Boolean& disableUpload)
at System.Net.HttpWebRequest.DoSubmitRequestProcessing(Exception& exception)
at System.Net.HttpWebRequest.ProcessResponse()
at System.Net.HttpWebRequest.SetResponse(CoreResponseData coreResponseData)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.Monitoring.TestOAuthConnectivityHelper.SendExchangeOAuthRequest(ADUser user,
String orgDomain, Uri targetUri, String& diagnosticMessage, Boolean appOnly, Boolean useCachedToken,
Boolean reloadConfig)
ResultType : Error
Identity : Microsoft.Exchange.Security.OAuth.ValidationResultNodeId
IsValid : True
ObjectState : New
It appears to work fine from Lync 2013 to Exchange 2013.
When I run: Test-CsExStorageConnectivity -sipuri [email protected] -Binding Nettcp -Verbose in Lync 2013 I get a successful outcome:
VERBOSE: Successfully opened a connection to storage service at localhost using
binding: NetNamedPipe.
VERBOSE: Create message.
VERBOSE: Execute Exchange Storage Command.
VERBOSE: Processing web storage response for ExCreateItem Success.,
result=Success, activityId=0bbdc565-4a05-4b57-bf95-0c75488a1ef6, reason=.
VERBOSE: Activity tracing:
2015/01/02 19:15:55.616 Autodiscover, send GetUserSettings request,
[email protected], Autodiscover
Uri=https://exchserver2.domainname.local/autodiscover/autodiscover.svc, Web
Proxy=<NULL>
2015/01/02 19:15:55.616 Autodiscover.EWSMA trace,
type=AutodiscoverRequestHttpHeaders, message=<Trace
Tag="AutodiscoverRequestHttpHeaders" Tid="30" Time="2015-01-02 19:15:55Z">
POST /autodiscover/autodiscover.svc HTTP/1.1
Content-Type: text/xml; charset=utf-8
Accept: text/xml
User-Agent: ExchangeServicesClient/15.00.0516.004
</Trace>
2015/01/02 19:15:55.624 Autodiscover.EWSMA trace, type=AutodiscoverRequest,
message=<Trace Tag="AutodiscoverRequest" Tid="30" Time="2015-01-02 19:15:55Z"
Version="15.00.0516.004">
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope
xmlns:a="http://schemas.microsoft.com/exchange/2010/Autodiscover"
xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<a:RequestedServerVersion>Exchange2013</a:RequestedServerVersion>
<wsa:Action>http://schemas.microsoft.com/exchange/2010/Autodiscover/Autodiscove
r/GetUserSettings</wsa:Action>
<wsa:To>https://exchserver2.domainname.local/autodiscover/autodiscover.svc</
wsa:To>
</soap:Header>
<soap:Body>
<a:GetUserSettingsRequestMessage
xmlns:a="http://schemas.microsoft.com/exchange/2010/Autodiscover">
<a:Request>
<a:Users>
<a:User>
<a:Mailbox>[email protected]</a:Mailbox>
</a:User>
</a:Users>
<a:RequestedSettings>
<a:Setting>InternalEwsUrl</a:Setting>
<a:Setting>ExternalEwsUrl</a:Setting>
<a:Setting>ExternalEwsVersion</a:Setting>
</a:RequestedSettings>
</a:Request>
</a:GetUserSettingsRequestMessage>
</soap:Body>
</soap:Envelope>
</Trace>
2015/01/02 19:15:55.704 Autodiscover.EWSMA trace,
type=AutodiscoverResponseHttpHeaders, message=<Trace
Tag="AutodiscoverResponseHttpHeaders" Tid="30" Time="2015-01-02 19:15:55Z">
HTTP/1.1 200 OK
Transfer-Encoding: chunked
request-id: 5917d246-64b0-48e2-ad79-f9b6cffb5bea
X-CalculatedBETarget: exchserver2.domainname.local
X-DiagInfo: EXCHSERVER2
X-BEServer: EXCHSERVER2
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Set-Cookie: ClientId=FTFXWUQWWRJVBMNBG; expires=Sat, 02-Jan-2016 19:15:55 GMT;
path=/;
HttpOnly,X-BackEndCookie=actas1(sid:S-1-5-21-3691024758-535552880-811174816-113
5|smtp:[email protected]|upn:[email protected])=u56Lnp2ejJqBx8jIn
sqbxpvSz8rHx9LLzp7O0sbOzcnSzcqcmZqem8aempmcgYHNz87K0s/N0s/Oq87Gxc7KxcrK;
expires=Sun, 01-Feb-2015 19:15:55 GMT; path=/autodiscover; secure; HttpOnly
Server: Microsoft-IIS/8.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
X-FEServer: EXCHSERVER2
Date: Fri, 02 Jan 2015 19:15:55 GMT
</Trace>
2015/01/02 19:15:55.704 Autodiscover.EWSMA trace, type=AutodiscoverResponse,
message=<Trace Tag="AutodiscoverResponse" Tid="30" Time="2015-01-02 19:15:55Z"
Version="15.00.0516.004">
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:a="http://www.w3.org/2005/08/addressing">
<s:Header>
<a:Action
s:mustUnderstand="1">http://schemas.microsoft.com/exchange/2010/Autodiscover/Au
todiscover/GetUserSettingsResponse</a:Action>
<h:ServerVersionInfo
xmlns:h="http://schemas.microsoft.com/exchange/2010/Autodiscover"
xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<h:MajorVersion>15</h:MajorVersion>
<h:MinorVersion>0</h:MinorVersion>
<h:MajorBuildNumber>1044</h:MajorBuildNumber>
<h:MinorBuildNumber>21</h:MinorBuildNumber>
<h:Version>Exchange2013_SP1</h:Version>
</h:ServerVersionInfo>
</s:Header>
<s:Body>
<GetUserSettingsResponseMessage
xmlns="http://schemas.microsoft.com/exchange/2010/Autodiscover">
<Response xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<ErrorCode>NoError</ErrorCode>
<ErrorMessage />
<UserResponses>
<UserResponse>
<ErrorCode>NoError</ErrorCode>
<ErrorMessage>No error.</ErrorMessage>
<RedirectTarget i:nil="true" />
<UserSettingErrors />
<UserSettings>
<UserSetting i:type="StringSetting">
<Name>InternalEwsUrl</Name>
<Value>https://exchserver2.domainname.local/EWS/Exchange.asmx</Value>
</UserSetting>
<UserSetting i:type="StringSetting">
<Name>ExternalEwsUrl</Name>
<Value>https://exchserver2.domainname.co.uk/EWS/Exchange.asmx</Value>
</UserSetting>
<UserSetting i:type="StringSetting">
<Name>ExternalEwsVersion</Name>
<Value>15.00.1044.000</Value>
</UserSetting>
</UserSettings>
</UserResponse>
</UserResponses>
</Response>
</GetUserSettingsResponseMessage>
</s:Body>
</s:Envelope>
</Trace>
2015/01/02 19:15:55.704 Autodiscover, received GetUserSettings response,
duration Ms=88, response=NoError
2015/01/02 19:15:55.706 Lookup user details,
sipUri=sip:[email protected], [email protected],
sid=S-1-5-21-3691024758-535552880-811174816-1135, [email protected],
tenantId=00000000-0000-0000-0000-000000000000
VERBOSE: Items choice type: CreateItemResponseMessage.
VERBOSE: Response message, class: Success, code: NoError.
VERBOSE: Item: Microsoft.Rtc.Internal.Storage.Exchange.Ews.MessageType, Id:
AAMkADAwNWZkZWI0LWM5NGYtNDUxNy05Nzk3LWZhZjRiY2Y4MTU4NwBGAAAAAADLP1MgTEXdQ7zQSlb
qPl++BwBauhRZTfLbTYZ+hBWtK784ANcdmUYqAACSqIurRqgYSZwMhT/IBw89AACnT6G9AAA=,
change key: CQAAABYAAACSqIurRqgYSZwMhT/IBw89AACnip6b, subject: , body: .
VERBOSE: Is command successful: True.
Test passed.
All my certificates on the Exchange 2013 and Lync 2013 servers are from my local CA.
I use APP with the public certificates as my reverse proxy for people connecting from outside the network.
In Lync, the OAuthTokenIssuer certificate created through the Lync deployment wizard is issued to domainname.local (my primary sip domain) and the Subject Alternative names include domainname.co.uk
I then exported this certificate to the Exchange Server and use the Set-AuthConfig to use this certificate for OAuth.
from what I read this was what I was supposed to do.
is this correct?
I have tried so many things I don't know what do to next.
Should the OAuth certificate in exchange be the one exported from Lync?
In Lync, should the OAuthTokenIssuer certificate include the servername or lyncserver.domainname.local or just be domainname.local like it is at the moment?
thank-you
jack

Thomas,
thanks for giving this the time. I have run the Configure-EnterpriseApplication.ps1 script following by remove-PartnerApplication so many times that I was wondering if there are other setting that
Configure-EnterpriseApplication.ps1 creates that aer not removed when you run
remove-PartnerApplication.
is there a way to completely remove everything that is confirmed when you run
Configure-EnterpriseApplication.ps1 so I can run Configure-EnterpriseApplication.ps1 without there being any configurations left from when I previously run that command?
thanks
jack
[PS] C:\Windows\system32>Get-PartnerApplication |fl
RunspaceId : cb2fb328-769d-4b32-8b7b-1fa35e2994f5
Enabled : True
ApplicationIdentifier : 00000004-0000-0ff1-ce00-000000000000
CertificateStrings : {MIIGcDCCBVigAwIBAgITPgAAARIHL+ig32UAAQAAAAABEjANBgkqhkiG9w0BAQUFADBcMRUwEwYKCZIm
iZPyLGQBGRYFbG9jYWwxHTAbBgoJkiaJk/IsZAEZFg1HdWlkZUNsb3RoaW5nMSQwIgYDVQQDExtHdWlkZ
UNsb3RoaW5nLUFQUFNFUlZFUjEtQ0EwHhcNMTUwMTEwMTIxODIzWhcNMTcwMTA5MTIxODIzWjB7MQswCQ
YDVQQGEwJHQjEPMA0GA1UECBMGTG9uZG9uMQ8wDQYDVQQHEwZMb25kb24xHzAdBgNVBAoTFkd1aWRlIEN
sb3RoaW5nIExpbWl0ZWQxCzAJBgNVBAsTAkhRMRwwGgYDVQQDExNHdWlkZUNsb3RoaW5nLmNvLnVrMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyzDzaLsjJfktsbwIJ998ihsZM/0rKGdIt8rIx00oc
HA7w0uVyz2UqnP9a8uRi6HkA7djbynlmGG0hKSUUQngXxz7q2dY6q9rcY5Rw2mJOMeppounx44FFp4+4e
5HQKviLTYo+3DBGIR0mYDqxanKPS00d0f7HDLvmVb90hjdrbE372JBdcNNHs2OHRqg37bN2fAbwd22c9x
2kvi0rESFnr+KcIGECVInCTHLJ7fwVqvi4hvRqtz7KLZsMXprpgeVDs45EMMRtwJ5Hw8uZR4CFz4dHSlo
dIVgDPn8Ns2vGhcUK0JU4WkDbjnqo1SJzHlqtNjiu//wGcn77PAiM0yhyQIDAQABo4IDCjCCAwYwCwYDV
R0PBAQDAgWgMCEGCSsGAQQBgjcUAgQUHhIAVwBlAGIAUwBlAHIAdgBlAHIwEwYDVR0lBAwwCgYIKwYBBQ
UHAwEwHQYDVR0OBBYEFOY3whPicRAXNsTDSIg3FexpaCKdMHUGA1UdEQRuMGyCH0x5bmNTZXJ2ZXIyLkd
1aWRlQ2xvdGhpbmcuY28udWuCH0x5bmNTZXJ2ZXIyLkd1aWRlQ2xvdGhpbmcubG9jYWyCE0d1aWRlQ2xv
dGhpbmcuY28udWuCE0d1aWRlQ2xvdGhpbmcubG9jYWwwHwYDVR0jBBgwFoAUDHst3gUSMGwvkiNTPavmi
UEWgtQwggEuBgNVHR8EggElMIIBITCCAR2gggEZoIIBFYaBzWxkYXA6Ly8vQ049R3VpZGVDbG90aGluZy
1BUFBTRVJWRVIxLUNBLENOPURvbVNlcnZlcjIsQ049Q0RQLENOPVB1YmxpYyUyMEtleSUyMFNlcnZpY2V
zLENOPVNlcnZpY2VzLENOPUNvbmZpZ3VyYXRpb24sREM9R3VpZGVDbG90aGluZyxEQz1sb2NhbD9jZXJ0
aWZpY2F0ZVJldm9jYXRpb25MaXN0P2Jhc2U/b2JqZWN0Q2xhc3M9Y1JMRGlzdHJpYnV0aW9uUG9pbnSGQ
2h0dHA6Ly9jcmwuZ3VpZGVjbG90aGluZy5sb2NhbC9jcmxkL0d1aWRlQ2xvdGhpbmctQVBQU0VSVkVSMS
1DQS5jcmwwgdUGCCsGAQUFBwEBBIHIMIHFMIHCBggrBgEFBQcwAoaBtWxkYXA6Ly8vQ049R3VpZGVDbG9
0aGluZy1BUFBTRVJWRVIxLUNBLENOPUFJQSxDTj1QdWJsaWMlMjBLZXklMjBTZXJ2aWNlcyxDTj1TZXJ2
aWNlcyxDTj1Db25maWd1cmF0aW9uLERDPUd1aWRlQ2xvdGhpbmcsREM9bG9jYWw/Y0FDZXJ0aWZpY2F0Z
T9iYXNlP29iamVjdENsYXNzPWNlcnRpZmljYXRpb25BdXRob3JpdHkwDQYJKoZIhvcNAQEFBQADggEBAD
87GUPi02czEMO2Op0CeKBBpGwsfjYR9+RlC2uKAoH8PbWAxYNP3Ke6BtPeFy+95GGAJd5Z0+6LpO/AagA
+zeY/tocZQjy0pYaU4/TPZgD+ZB/8sU982msu+8waO316ipBcf/87n9ZW3Jjk5DcVbtwrZErrGRe9DEn8
QArN0jroLfaRtbDumse1Lp76+dxFuVhlLWcUXtIKaxm+UU9DS94EwJMtN54lDm3EG6hVdiGUR7TYqZU0K
HGm7HciIhuO+2rhAazOBiIAAW6wZRUpFKZONSVD6bKrQCzL12LvynQ7XC6Itgr4JGzNCmoN43dXwVCkWo
amTDdZY4h+QBqUvvY=}
AuthMetadataUrl : https://lyncserver2.domainname.local/metadata/json/1
Realm : domainname.local
UseAuthServer : False
AcceptSecurityIdentifierInformation : True
LinkedAccount : domainname.local/Users/LyncEnterprise-ApplicationAccount
IssuerIdentifier :
AppOnlyPermissions :
ActAsPermissions :
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : LyncEnterprise-786f61476b634278a3c9b9e4ec08b660
DistinguishedName : CN=LyncEnterprise-786f61476b634278a3c9b9e4ec08b660,CN=Partner
Applications,CN=Auth Configuration,CN=domainname,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domainname,DC=local
Identity : LyncEnterprise-786f61476b634278a3c9b9e4ec08b660
Guid : 07495125-ccd4-4443-82d9-74fc3b955cdf
ObjectCategory : domainname.local/Configuration/Schema/ms-Exch-Auth-Partner-Application
ObjectClass : {top, msExchAuthPartnerApplication}
WhenChanged : 10/01/2015 17:14:55
WhenCreated : 10/01/2015 17:14:55
WhenChangedUTC : 10/01/2015 17:14:55
WhenCreatedUTC : 10/01/2015 17:14:55
OrganizationId :
Id : LyncEnterprise-786f61476b634278a3c9b9e4ec08b660
OriginatingServer : DomServer2.domainname.local
IsValid : True
ObjectState : Unchanged

Lync Server 2010迁移升级Lync Server 2013时Lync Server控制面板无法打开Lync Server 2013

Lync Server 控制面板打开Lync Server 2010正常，打开Lync Server 2013报错未授权：授权失败。前端服务器日志显示如下：
日志名称:          Lync Server
来源:            LS Remote PowerShell
日期:            2014/4/1 10:40:41
事件 ID:         35005
任务类别:          (3500)
级别:
错误
关键字:
经典
用户:
暂缺
计算机:           lync13fe01.byd.com
描述:
远程 PowerShell
无法从存储中读取 RBAC 角色信息。
远程 PowerShell
在尝试读取用户的 RBAC 角色信息时遇到问题。Retry failed。异常: SqlConnectionException。失败原因:
用户 'DL\LYNC13fe01$' 登录失败。。堆栈跟踪:
在 Microsoft.Rtc.Management.Store.Sql.XdsSqlConnection.ReadDocItems(ICollection`1 key)
在 Microsoft.Rtc.Management.ScopeFramework.AnchoredXmlReader.Read(ICollection`1 key)
在 Microsoft.Rtc.Management.WritableConfig.AnchoredXmlSchemaCache.get_Item(ScopeClass scopeClass)
在 Microsoft.Rtc.Management.Authorization.OcsRunspaceConfiguration.GetRolesFromStore(ManagementConnection connection)
原因:
发生失败可能是由于读取管理存储时出现某个权限问题。
解决方法:
确保服务器是加入域的计算机且能够查询 Active Directory。
事件 Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="LS Remote PowerShell" />
    <EventID Qualifiers="52652">35005</EventID>
    <Level>2</Level>
    <Task>3500</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-01T02:40:41.000000000Z" />
    <EventRecordID>7400</EventRecordID>
    <Channel>Lync Server</Channel>
    <Computer>lync13fe01.byd.com</Computer>
    <Security />
</System>
<EventData>
    <Data>Retry failed</Data>
    <Data>SqlConnectionException</Data>
    <Data>用户
'DL\LYNC13fe01$' 登录失败。</Data>
    <Data>
在 Microsoft.Rtc.Management.Store.Sql.XdsSqlConnection.ReadDocItems(ICollection`1 key)
在 Microsoft.Rtc.Management.ScopeFramework.AnchoredXmlReader.Read(ICollection`1 key)
在 Microsoft.Rtc.Management.WritableConfig.AnchoredXmlSchemaCache.get_Item(ScopeClass scopeClass)
在 Microsoft.Rtc.Management.Authorization.OcsRunspaceConfiguration.GetRolesFromStore(ManagementConnection connection)</Data>
</EventData>
</Event>

Hi,
This forum is only English Supported.
Did you use the same account to open Lync Server 2013 control panel with Lync Server 2010 Control Panel?
If not, please check the account that is assigned to the CsAdministrator role.
On your Lync Server 2013 Front End Server, open IIS, expand Lync Server Internal Web Site. Click cscp, then click Browse *:443 in Actions panel to check if you can open Lync Server 2013 Control Panel.
Check your Domain Controller is available. You can ping it on Lync Server 2013 Front End Server.
Lisa Zheng
TechNet Community Support

Lync 2010 and Outlook 2013 - not talking!

I have problemns with Lync 2010 with Outlook 2013 under Windows 8.
Conversation History is not being saved.
All the patches are installed.
When I click on "show more in Outlook" it complains the accounts are not the same. I have two exchange accounts configured within the one Outlook profile. I never had this issue under Outlook 2010.
ERROR:
The email address used in your default Outlook profile is different from the sign-in address used in Lync 2010.
Change your default Outlook profile to match the sign-in address you are using in Lync, and then sign out and sign back in to Lync.
My default account is the same as my Lync sign-in name.
I have tried everything.

Mate,
There is no issue on conversation history save option, when I use Outlook 2010.
The issue only to Outlook 2013 with Lync 2010? Two observations;
=> Save IM in outlook ( greyed out ) - Lync 2010 client
=> When I check Lync config information - MAPI is not installed - Lync 2010 client
Could you advice.

Unknown Presence in Lync 2010 and Lync 2013 co-existence

I have lync 2010 and lync 2013 in my environment. Everything was working fine except when I moved the DNS of the Lync 2013 pool to the load balancer. When I did that, users on lync2013 could see the presence of users on Lync2010 pool but not vice versa.
I have point the Lyncdiscoverinternal.domain.com to the lync2013 pool DNS. I have opened migration ports on the load balancer but still not working. It works perfectly fine if I point the DNS of the pool to one server directly without going
through the Load balancer VIP.
Am I missing anything here?
Thanks!
Alert from TechNet Posting

Hi Kojo Obeng Antwi,
Please check out the following information.
Deploying DNS load balancing on Front End pools requires you to perform a couple of extra steps with FQDNs and DNS
records.
A pool that uses DNS load balancing must have two FQDNs: the regular pool FQDN that is used by DNS load balancing (such as pool01.contoso.com), and resolves to the physical
IPs of the servers in the pool, and another FQDN for the pool’s Web services (such as web01.contoso.com), which resolves to virtual IP address of the pool.
In Topology Builder, if you want to deploy DNS load balancing for a pool, to create this extra FQDN for the pool’s Web services
you must select the Override internal Web Services pool FQDN check box and type the FQDN, in the Specify the Web Services URLs for this Pool page.
To support the FQDN used by DNS load balancing, you must provision DNS to resolve the pool FQDN (such as pool01.contoso.com) to the IP addresses of all the servers in the pool
(for example, 192.168.1.1, 192.168.1.2, and so on). You should include only the IP addresses of servers that are currently deployed.
Best regards,
Eric

Differences & Similarities between Lync 2013 desktop & Lync 2013 mobile

Similar Messages

Maybe you are looking for