Questions in Lync 2013 - HD Photo

Hi,
We have Lync 2013 Enterprise environment for 4000 users.  We ran the script mentioned in the below article to display the HD photo on Lync 2013 client:
http://gallery.technet.microsoft.com/Add-Personal-URL-Photo-in-df0136ea/view/Discussions#content
Outcomes:
The script is working just fine for the users who doesn’t have any photos in AD.
For the users who has photo in AD, the script works just fine until they go to offline. Once they are back to available from offline, Lync client picks up the photo from AD. (Could be because of the Address book changes over night). It tends to run the
script by administrator every day  to keep the HD photo for the users.
Questions:
Is this by design?
If not, is there a way to only keep the photo which got updated through Script rather than getting updated over night after the user went to offline?
Please advise. MANY THANKS.

The entire line I mentioned, looks like this decoded (yes, that's my real pic)
<contactCard xmlns="http://schemas.microsoft.com/2006/09/sip/contactcard">
<title updated="2013-10-18T21:13:22Z">Principal Consultant</title>
<delimiter xmlns="http://schemas.microsoft.com/2006/09/sip/commontypes"></delimiter>
<delimiter xmlns="http://schemas.microsoft.com/2006/09/sip/commontypes"></delimiter>
<displayADPhoto>true</displayADPhoto>
<photo type="enterprise" updated="2014-07-15T20:15:28Z"><uri></uri><hash>5a13f9596e1c9a932982b75e75ba9322</hash></photo>
<photo type="default" updated="2014-09-30T15:44:12Z"><uri>http://m.c.lnkd.licdn.com/media/p/3/000/0a9/284/0f4c3bf.jpg</uri><hash>349073057l</hash></photo>
<photo type="default" updated="2014-09-30T15:44:12Z"><uri>http://m.c.lnkd.licdn.com/media/p/3/000/0a9/284/0f4c3bf.jpg</uri><hash>349073057l</hash></photo>
</contactCard>
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

Similar Messages

  • Lync 2013 Display photos do no display correctly internally

    Hey guys, really need some help with this one so I will provide as much detail as possible (sorry for the lengthy post):
    We have Lync 2013, Exchange 2010 and AD is at a 2003 functional level.
    We are experiencing issues where Lync photos are not updating correctly in the internal clients. I have checked the pre-reqs; Replicate this attribute to the Global Catalog
    is set for the ThumbnailPhoto attribute. We are also forcing photos from AD only (or no photo) by setting the following:
    "Set-CsClientPolicy -Identity PhotosControl -DisplayPhoto PhotosFromADOnly"  
    and finally we are setting the photo in ad using this PS command:
    "Import-RecipientDataProperty -Identity "Test User" -Picture -FileData ([Byte[]]$(Get-Content -Path "C:\pictures\testuser.jpg" -Encoding Byte -ReadCount 0))"
    The pictures being uploaded are under 10KB in size. The initial upload of a photo for a user (IE: a new user that doesn't already have a photo) will generally be displayed in both Outlook and Lync within 24 hours. When we try to update a photo for a user who
    already has a photo it updates within Outlook but never updates on Lync clients. I have also manually tried running the "Update-CsAddressBook" command from Lync and waiting 24hours + but the photo will not update in Lync client. Another interesting
    thing I've found, anyone who set up their Lync in last month or two do not see their OWN photo within Lync (it just shows the default gray/white man) both in the main window and the chat although others can see it.
    I was able to find that on our Lync file store, the cached contacts/photos are being updated daily (as expected) and actually contain the correct photos. I confirmed this be using abserver.exe on the .lsabs file and then locating the contactID for a few users
    I know are not updating properly. Once I have their contact ID I simply look for their .photo file in the cached files, copy it out to a different location and change it to a .jpeg. To my surprise the photos are actually the correctly updated ones, so why
    are these no getting to the users/clients? I have gone through and deleted my local cache folder as well as the registry key HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Lync but unfortunately no change on my Client.
    Another piece of the puzzle; We just implemented a Reverse Proxy to handle mobility with Lync. During my testing I did get Lync client for android running and low and behold the pictures are actually correct on my mobile device!! 
    We are planning to upgrade Exchange from 2010 to 2013 and I hoping that leveraging the Hi-Def photo capabilities for Lync 2013 with Exchange 2013 may fix this issue but I would rather try to get it resolved then hope for the best.
    More info on the environment:
    4 main sites + remote users
    ~7DC's - 2003 DFL (1 at each site + a few at HQ)
    3 Lync Front end servers (2013) (All located at central HQ)
    2 Lync edge server (2013) (All located at central HQ)
    1 - 2010 Exchange server (Located at central HQ)
    2013 Lync Client version 15.0.4675.1000 MSO 15.0.4675.1002 64bit
    About 100 HP 4110 Lync Edition Desk phones
    Users's workstations are either Windows 7 Enterprise or Windows 8.1
    Enterprise

    Can you see the pictures being cached in \users\username\AppData\Local\Microsoft\Office\15.0\Lync\[email protected]\Photo ?  You can see me poking around in a pic here for reference:
    http://www.skypeadmin.com/2014/12/23/missing-pictures-lync-skype/
    If you rename to jpg you should see if they're new or old. 
    I'd like to see if you switch a few users to websearchonly for ABS info, if it would make a difference:
    http://blog.schertz.name/2010/11/forcing-lync-address-book-web-query/
    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
    This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Questions in Lync 2013 HADR

    Hi Team,
    One of the customer raised the query:
    In our scenario, we want Active/Active High availability between different geolocations with RPO=0 and RTO near zero (seconds).
    Questions:
    1. Isn’t this possible with pool pairing and database availability AlwaysOn synchronous commit?
    2. What is the bandwidth needed between both sites?
    3. Do you think to achieve Active/Active high availability (RPO=0, RTO=+/-0) for Lync between 2 datacenters we should go with the following scenario:
    --> Storage: virtualization (stretched LUNs)
    -->Compute: Hyper-v Clustering (failover cluster)
    -->DNS: Global Datacenter Server Load Balancer
    4. What is the RTO and RPO in your proposed solution?
    Please advise. Many Thanks.

    1) No.  Pool paring doesn't automatically failover, therefore it does not meet the requirements.  Also, HA within a pool isn't supported across geographic locations, so I don't believe this requirement can be met within the supported model. 
    It's possible if you have a solid enough pipe between the locations with very low latency that you could go unsupported with the old Metropolitan Site Resiliency model:
    https://technet.microsoft.com/en-us/library/gg670905(v=ocs.14).aspx but not supported in 2013.
    2) This can't be answered easily, it depends on what they're doing and using. How many users, how much archived data... the SQL mirroring will be quite a bit, as well as the shared presence data on front ends.  Will they use video between sites?  
    Too many questions to get any kind of reliable answer.
    3) If RTO/RPO is this critical, then I'm assuming it's voice.  If it's not, then a short outage should be more tolerable.  If it is voice, do not leave the supported model... just don't.  You don't want to be in that
    situation when systems are down and it's your phone.  No live migrations, just what's supported via TechNet and virtualization whitepapers.
    4) My proposed solution would be HA pools in both datacenters, built big enough it's unlikely to go down.   If the site does go down, pool failover can happen in a reasonable amount of time, perhaps 15 minutes if you're well prepared,
    but phones could potentially stay online during this time. 
    -Anthony
    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
    This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Questions in Lync 2013 Pool failover behaviour

    Hello Team,
    Please let us know answers for the below questions:
    If
    Pool A fails over to Pool B in disaster mode.
    Then the original front ends for Pool A are recovered successfully, and services start. Is it expected that  User Services, Conference services and CMS would continue to backup via the backup service for pool A routing Groups,
    back to their original Pool A servers for the fail back? Or does the fail back, obtain all information from the SQL databases / the pool A user groups in Pool B? Is Pool pairing inactive after a fail over has occurred?
    MANY THANKS.

    The Failback will sync any changes that were made while users are running on Pool B.  My understanding is that Pool pairing resume once Pool A was back online and attempt to sync the data ahead of the actual Pool Failback command. 
    Have a look at this preso for more details - http://bit.ly/120Ogls  View the powerpoint in presentation mode and you will see that when Pool A is repaired, mirroring operations resume even though Pool A users are
    still running off Pool B.
    Of course the devil is in the details so I would test this out if you can and observe behavior and queuing the health of the pool mirroring process.
    Hope this helps.
    Dino
    Dino Caputo, BA | MCSE | MCTS:OCS/Lync http://www.ucguys.com http://www.enableUC.com

  • Lync 2013 External Mobility Not Working

    Hello,
    The issue I seem to be having is in regards to the external mobility access. 
    So far everything else in our environment seems to be functioning properly. 
    The Lync desktop client works both internally as well as externally. 
    The Lync internal mobility also works.  The only issue seems to be with the external mobility part.
    I tried going to the external autodiscover address for our system, https://lyncdiscover.mydomain.com but it doesn’t return anything either. 
    I think the issue lies somewhere with DNS or my reverse proxy, however I’m having a hard time being able to just start changing settings seeing as how I don’t want to break everything that is currently working for our users.
    I’ve been through a lot of the post here but I still can’t seem to find the settings to fix the issue I’m having.
    Here is a breakdown of my settings I feel are in question:
    1 – Lync 2013 FE Server (LYNC01)
    1 – Lync Edge Server (EDGE01)
    1 – Reverse Proxy Server (RPROXY01)
    Public DNS:
    A Records
    SIP.mydomain.com                          
    205.XXX.XXX.91 (Access Service on EDGE01)
    AccessEdge.mydomain.com              
    205.XXX.XXX.91 (Access Service on EDGE01)
    WebConfEdge.mydomain.com            205.XXX.XXX.92 (WebConf Service on EDGE01)
    AVEdge.mydomain.com                    
    205.XXX.XXX.93 (A/VEdge Service on EDGE01)
    meet.mydomain.com                        
    205.XXX.XXX.94 (Reverse Proxy Server)
    dialin.mydomain.com                        
    205.XXX.XXX.94 (Reverse Proxy Server)
    lync.mydomain.com                          
    205.XXX.XXX.94 (Reverse Proxy Server)
    lyncdiscover.mydomain.com               205.XXX.XXX.94 (Reverse Proxy
    Server)
    SRV
    _sip._tls.mydomain.com:443                                     
    AccessEdge.mydomain.com
    _sipfederationtls._tcp.mydomain.com:5061             
    AccessEdge.mydomain.com
    _xmpp-server._tcp.mydomain.com                          
    AccessEdge.mydomain.com
    Private DNS:
    A Records
    LYNC01                                            
    172.XXX.XXX.65 (LYNC01 FE Server)
    Admin                                              
    172.XXX.XXX.65 (LYNC01 FE Server)
    Dialin                                               
    172.XXX.XXX.65 (LYNC01 FE Server)
    LyncDiscoverInternal                         
    172.XXX.XXX.65 (LYNC01 FE Server)
    Meet                                                
    172.XXX.XXX.65 (LYNC01 FE Server)
    Sip                                                  
    172.XXX.XXX.65 (LYNC01 FE Server)
    EDGE01                                            
    172.XXX.XXX.66 (EDGE01 Server)
    RPROXY01                                        
    172.XXX.XXX.70 (Reverse Proxy Server)
    Lync                                                 
    205.XXX.XXX.94 (Reverse Proxy Server)
    LyncDiscover  
    (CNAME)                    
    lync.gmsd.k12.pa.us
    SRV
    _xmpp-server._tcp.mydomain.com                          
    Sip.mydomain.com
    _sipinternaltls._tcp.mydomain.com:5061                 
    LYNC01.mydomain.com
    Lync Server Services Addresses
    Lync FE Server:                      \\
    LYNC01.mydomain.com (172.XXX.XXX.65)
    File Store:                              \\
    LYNC01.mydomain.com\Share
    Office Web Apps Server:
             \\lyncowa.mydomain.com
    External Web Services:
               \\lync.mydomain.com
    Edge Server Services Addresses
    Edge Server:                  
    \\ EDGE01.mydomain.com (172.XXX.XXX.66)
    Access Edge Service:       
    \\AccessEdge.mydomain.com (172.XXX.XXX.67, 205.XXX.XXX.91)
    Web Conference Service:  \\WebConfEdge.mydomain.com (172.XXX.XXX.68, 205.XXX.XXX.92)
    A/V Edge Service:            \\WebConfEdge.mydomain.com
    (172.XXX.XXX.69, 205.XXX.XXX.93)
    Reverse Proxy Server Addresses
    Reverse Proxy Server:            
    RPROXY01.mydomain.com (172.XXX.XXX.70, 205.XXX.XXX.94)
    Server Farms:
    Dialin.mydomain.com:
    Dialin.mydomain.com (LYNC01)
    Meet.mydomain.com:
    Meet.mydomain.com (LYNC01)
    LyncDiscover.mydomain.com:
               LYNC01.mydomain.com (LYNC01)
    Lync.mydomain.com:                       
    LYNC01.mydomain.com (LYNC01)
    Edge External Cert
    AccessEdge.mydomain.com
    Sip.mydomain.com
    WebConfEdge.mydomain.com
    Reverse Proxy Cert
    lync.mydomain.com
    meet.mydomain.com
    dialin.mydomain.com
    lyncdiscover.mydomain.com
    lyncowa.mydomain.com
    With everything else working as it should, this external mobility part is just not really making sense to me.  I have also verified that the correct ports are being using on the reverse proxy as well for the server farms,
    8080 and 4443.  Any help would be greatly appreciated.  Thank you.

    I'm also attaching the log file from running Lync Connectivity Analyzer if it helps.
    [6/10/2014 7:30:18 AM] [DEBUG] Logging test parameters:
    [6/10/2014 7:30:18 AM] [DEBUG] SIP Uri: [email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] User Name:
    [6/10/2014 7:30:18 AM] [DEBUG] Discovery Type: Automatic Discovery
    [6/10/2014 7:30:18 AM] [DEBUG] Network access: NetworkAccessExternal
    [6/10/2014 7:30:18 AM] [DEBUG] Selected client: ApplicationLyncMobile2010
    [6/10/2014 7:30:18 AM] [SUBHEADING] Starting Lync server autodiscovery
    [6/10/2014 7:30:18 AM] [INFO] Please wait; this test may take several minutes to complete...
    [6/10/2014 7:30:18 AM] [SUBHEADING] Starting automatic discovery for secure (HTTPS) internal channel
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to https://lyncdiscoverinternal.mydomain.com/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] 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: LYNC01.mydomain.com
      X-Content-Type-Options: nosniff
      Cache-Control: no-cache
      Date: Tue, 10 Jun 2014 11:30:18 GMT
      Server: Microsoft-IIS/7.5
      X-AspNet-Version: 4.0.30319
      X-Powered-By: ASP.NET
      Content-Length: 670
      Content-Type: application/vnd.microsoft.rtc.autodiscover+xml; v=1
      Expires: -1
    [6/10/2014 7:30:18 AM] [DEBUG] Parsing the response for URL https://lyncdiscoverinternal.mydomain.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="Internal"><Root><Link token="Domain" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/domain" /><Link token="User" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user"
    /><Link token="OAuth" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/oauth/user" /><Link token="Self" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /></Root></AutodiscoverResponse>
    [6/10/2014 7:30:18 AM] [DEBUG] Autodiscover URL https://lyncdiscoverinternal.mydomain.com/[email protected] redirected to https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Cookie  found in autodiscover response: StatusCode: 401, ReasonPhrase: 'Unauthorized', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
      X-MS-WebTicketURL: https://lync01.mydomain.com/WebTicket/WebTicketService.svc
      X-MS-WebTicketSupported: cwt,saml
      X-MS-Server-Fqdn: LYNC01.mydomain.com
      X-Content-Type-Options: nosniff
      Date: Tue, 10 Jun 2014 11:30:18 GMT
      Server: Microsoft-IIS/7.5
      X-Powered-By: ASP.NET
      Content-Length: 1293
      Content-Type: text/html
    [6/10/2014 7:30:18 AM] [DEBUG] Authorization required for https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Obtaining WebTicket from https://lync01.mydomain.com/WebTicket/WebTicketService.svc
    [6/10/2014 7:30:18 AM] [DEBUG] On-premises WebTicket server: https://lync01.mydomain.com/WebTicket/WebTicketService.svc/Auth
    [6/10/2014 7:30:18 AM] [DEBUG] AcquireTicketAsync succeeded for https://lync01.mydomain.com/WebTicket/WebTicketService.svc/Auth
    [6/10/2014 7:30:18 AM] [DEBUG] WebTicket: <saml:Assertion MajorVersion="1" MinorVersion="1" AssertionID="SamlSecurityToken-4e51bf2a-2849-4779-a595-a5040c22ff1b" Issuer="https://lync01.mydomain.com/63b16135-930c-5e0b-998c-7ed6bc68b6f8" IssueInstant="2014-06-10T11:30:18.173Z"
    xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion"><saml:Conditions NotBefore="2014-06-10T11:30:18.173Z" NotOnOrAfter="2014-06-10T19:23:01.173Z"><saml:AudienceRestrictionCondition><saml:Audience>https://lync01.mydomain.com/</saml:Audience></saml:AudienceRestrictionCondition></saml:Conditions><saml:AuthenticationStatement
    AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:unspecified" AuthenticationInstant="2014-06-10T11:30:18.173Z"><saml:Subject><saml:NameIdentifier Format="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/uri">sip:[email protected]</saml:NameIdentifier><saml:SubjectConfirmation><saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:holder-of-key</saml:ConfirmationMethod><KeyInfo
    xmlns="http://www.w3.org/2000/09/xmldsig#"><e:EncryptedKey xmlns:e="http://www.w3.org/2001/04/xmlenc#"><e:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#kw-aes256"></e:EncryptionMethod><KeyInfo><KeyName>63b16135-930c-5e0b-998c-7ed6bc68b6f8:8d152b04ce7ddbf</KeyName></KeyInfo><e:CipherData><e:CipherValue>7M3R6naVg1ifGvuQKTMS+4EjHlJrdZeQqsqobNZUhMxHE9y7klUmXw==</e:CipherValue></e:CipherData></e:EncryptedKey></KeyInfo></saml:SubjectConfirmation></saml:Subject></saml:AuthenticationStatement><Signature
    xmlns="http://www.w3.org/2000/09/xmldsig#"><SignedInfo><CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></CanonicalizationMethod><SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"></SignatureMethod><Reference
    URI="#SamlSecurityToken-4e51bf2a-2849-4779-a595-a5040c22ff1b"><Transforms><Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"></Transform><Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></Transform></Transforms><DigestMethod
    Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"></DigestMethod><DigestValue>otvulmCO6kY0HQdwfqQXUZT/pdmKSdVZJTU0f/MS0N8=</DigestValue></Reference></SignedInfo><SignatureValue>WUGQOtUzu6RtuSKdHHCQZWxiOFVf8HT181U6tS8IVifyyAzA046lm0SBKbFpLzwMEAXsf3ZmkHQkzK/AfS6WJ92WkAz3LLEsqSqGBGQoxe5WPXMlfA9J4+1lnT6Zsfq7fb9aLqZch2oSga3yj0CeQgsbcmppQhQO86zJ468YskVyAk4Y/oIOyThKg/+Ce8V4tFw575+zYatuSzKvUtgHq+DKJRO7T2M8r0aoCx65ZgfCxJpA+bqalDz3BesqOzMKfWTn33fwArVh8JMF1ohNkliwOegTeEEq4aH2Sg04N7ZfLrhoFlWeXuZWn1AzWppyl+FBfwlbLOVbQgP6/3NdMQ==</SignatureValue><KeyInfo><o:SecurityTokenReference
    xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><o:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA1">/YVCIdf+YFyKopRflv61uWov2vs=</o:KeyIdentifier></o:SecurityTokenReference></KeyInfo></Signature></saml:Assertion>
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] 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: LYNC01.mydomain.com
      X-Content-Type-Options: nosniff
      Cache-Control: no-cache
      Date: Tue, 10 Jun 2014 11:30:18 GMT
      Server: Microsoft-IIS/7.5
      X-AspNet-Version: 4.0.30319
      X-Powered-By: ASP.NET
      Content-Length: 1646
      Content-Type: application/vnd.microsoft.rtc.autodiscover+xml; v=1
      Expires: -1
    [6/10/2014 7:30:18 AM] [DEBUG] Parsing the response for URL https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[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"><User><SipServerInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipClientInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipServerExternalAccess
    fqdn="AccessEdge.mydomain.com" port="5061" /><SipClientExternalAccess fqdn="AccessEdge.mydomain.com" port="443" /><Link token="Internal/Autodiscover" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /><Link token="Internal/AuthBroker"
    href="https://lync01.mydomain.com/Reach/sip.svc" /><Link token="Internal/WebScheduler" href="https://lync01.mydomain.com/Scheduler" /><Link token="External/Autodiscover" href="https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root"
    /><Link token="External/AuthBroker" href="https://lync.mydomain.com/Reach/sip.svc" /><Link token="External/WebScheduler" href="https://lync.mydomain.com/Scheduler" /><Link token="Internal/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc"
    /><Link token="External/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc" /><Link token="Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications" /><Link token="Internal/Ucwa" href="https://lync01.mydomain.com/ucwa/v0/applications"
    /><Link token="External/Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications" /><Link token="Self" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user" /></User></AutodiscoverResponse>
    [6/10/2014 7:30:18 AM] [INFO] Server discovery has completed for https://lyncdiscoverinternal.mydomain.com/.
    [6/10/2014 7:30:18 AM] [DEBUG] Autodiscover full response for URL https://lyncdiscoverinternal.mydomain.com/ is <?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"><User><SipServerInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipClientInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipServerExternalAccess fqdn="AccessEdge.mydomain.com" port="5061"
    /><SipClientExternalAccess fqdn="AccessEdge.mydomain.com" port="443" /><Link token="Internal/Autodiscover" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /><Link token="Internal/AuthBroker" href="https://lync01.mydomain.com/Reach/sip.svc"
    /><Link token="Internal/WebScheduler" href="https://lync01.mydomain.com/Scheduler" /><Link token="External/Autodiscover" href="https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /><Link token="External/AuthBroker" href="https://lync.mydomain.com/Reach/sip.svc"
    /><Link token="External/WebScheduler" href="https://lync.mydomain.com/Scheduler" /><Link token="Internal/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc" /><Link token="External/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc"
    /><Link token="Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications" /><Link token="Internal/Ucwa" href="https://lync01.mydomain.com/ucwa/v0/applications" /><Link token="External/Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications"
    /><Link token="Self" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user" /></User></AutodiscoverResponse>
    [6/10/2014 7:30:18 AM] [DEBUG] SendRequest failed for https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [INFO] Automatic discovery results for https://lyncdiscoverinternal.mydomain.com/
    [6/10/2014 7:30:18 AM] [INFO] Access Location                          : Internal
    [6/10/2014 7:30:18 AM] [INFO] SIP Server Internal Access               : LYNC01.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] SIP Server External Access               : AccessEdge.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] SIP Client Internal Access               : LYNC01.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] SIP Client External Access               : AccessEdge.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] Internal Auth broker service             : https://lync01.mydomain.com/Reach/sip.svc
    [6/10/2014 7:30:18 AM] [INFO] External Auth broker service             : https://lync.mydomain.com/Reach/sip.svc
    [6/10/2014 7:30:18 AM] [INFO] Internal Auto discover service           : https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root
    [6/10/2014 7:30:18 AM] [INFO] External Auto discover service           : https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root
    [6/10/2014 7:30:18 AM] [INFO] Internal MCX service                     : https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:30:18 AM] [INFO] External MCX service                     : https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:30:18 AM] [INFO] Internal UCWA service                    : https://lync01.mydomain.com/ucwa/v0/applications
    [6/10/2014 7:30:18 AM] [INFO] External UCWA service                    : https://lync.mydomain.com/ucwa/v0/applications
    [6/10/2014 7:30:18 AM] [INFO] Internal Webscheduler service            : https://lync01.mydomain.com/Scheduler
    [6/10/2014 7:30:18 AM] [INFO] External Webscheduler service            : https://lync.mydomain.com/Scheduler
    [6/10/2014 7:30:18 AM] [INFO] Total server discovery time: 0.1 seconds
    [6/10/2014 7:30:18 AM] [SUMMARY_SUCCESS] Server discovery succeeded for secure (HTTPS) internal channel against URL https://lyncdiscoverinternal.mydomain.com/
    [6/10/2014 7:30:18 AM] [SUBHEADING] Starting automatic discovery for unsecure (HTTP) internal channel
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to http://lyncdiscoverinternal.mydomain.com/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] 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: LYNC01.mydomain.com
      X-Content-Type-Options: nosniff
      Cache-Control: no-cache
      Date: Tue, 10 Jun 2014 11:30:18 GMT
      Server: Microsoft-IIS/7.5
      X-AspNet-Version: 4.0.30319
      X-Powered-By: ASP.NET
      Content-Length: 670
      Content-Type: application/vnd.microsoft.rtc.autodiscover+xml; v=1
      Expires: -1
    [6/10/2014 7:30:18 AM] [DEBUG] Parsing the response for URL http://lyncdiscoverinternal.mydomain.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="Internal"><Root><Link token="Domain" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/domain" /><Link token="User" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user"
    /><Link token="OAuth" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/oauth/user" /><Link token="Self" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /></Root></AutodiscoverResponse>
    [6/10/2014 7:30:18 AM] [DEBUG] Autodiscover URL http://lyncdiscoverinternal.mydomain.com/[email protected] redirected to https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Cookie  found in autodiscover response: StatusCode: 401, ReasonPhrase: 'Unauthorized', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
      X-MS-WebTicketURL: https://lync01.mydomain.com/WebTicket/WebTicketService.svc
      X-MS-WebTicketSupported: cwt,saml
      X-MS-Server-Fqdn: LYNC01.mydomain.com
      X-Content-Type-Options: nosniff
      Date: Tue, 10 Jun 2014 11:30:18 GMT
      Server: Microsoft-IIS/7.5
      X-Powered-By: ASP.NET
      Content-Length: 1293
      Content-Type: text/html
    [6/10/2014 7:30:18 AM] [DEBUG] Authorization required for https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Obtaining WebTicket from https://lync01.mydomain.com/WebTicket/WebTicketService.svc
    [6/10/2014 7:30:18 AM] [DEBUG] On-premises WebTicket server: https://lync01.mydomain.com/WebTicket/WebTicketService.svc/Auth
    [6/10/2014 7:30:18 AM] [DEBUG] AcquireTicketAsync succeeded for https://lync01.mydomain.com/WebTicket/WebTicketService.svc/Auth
    [6/10/2014 7:30:18 AM] [DEBUG] WebTicket: <saml:Assertion MajorVersion="1" MinorVersion="1" AssertionID="SamlSecurityToken-1b6331e1-4be5-4749-869a-21feb4b7198a" Issuer="https://lync01.mydomain.com/63b16135-930c-5e0b-998c-7ed6bc68b6f8" IssueInstant="2014-06-10T11:30:18.238Z"
    xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion"><saml:Conditions NotBefore="2014-06-10T11:30:18.238Z" NotOnOrAfter="2014-06-10T19:20:24.238Z"><saml:AudienceRestrictionCondition><saml:Audience>https://lync01.mydomain.com/</saml:Audience></saml:AudienceRestrictionCondition></saml:Conditions><saml:AuthenticationStatement
    AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:unspecified" AuthenticationInstant="2014-06-10T11:30:18.238Z"><saml:Subject><saml:NameIdentifier Format="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/uri">sip:[email protected]</saml:NameIdentifier><saml:SubjectConfirmation><saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:holder-of-key</saml:ConfirmationMethod><KeyInfo
    xmlns="http://www.w3.org/2000/09/xmldsig#"><e:EncryptedKey xmlns:e="http://www.w3.org/2001/04/xmlenc#"><e:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#kw-aes256"></e:EncryptionMethod><KeyInfo><KeyName>63b16135-930c-5e0b-998c-7ed6bc68b6f8:8d152b04ce7ddbf</KeyName></KeyInfo><e:CipherData><e:CipherValue>NrQOUA0JAXMmR/4ACrZ8LyVN79jUZbR6Fz+sGlbAdWXgQF/u24DLlw==</e:CipherValue></e:CipherData></e:EncryptedKey></KeyInfo></saml:SubjectConfirmation></saml:Subject></saml:AuthenticationStatement><Signature
    xmlns="http://www.w3.org/2000/09/xmldsig#"><SignedInfo><CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></CanonicalizationMethod><SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"></SignatureMethod><Reference
    URI="#SamlSecurityToken-1b6331e1-4be5-4749-869a-21feb4b7198a"><Transforms><Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"></Transform><Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></Transform></Transforms><DigestMethod
    Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"></DigestMethod><DigestValue>WnZZN/Vbfrget92urYd1+HmyXX/vYQ6CjHN4lLEXxK0=</DigestValue></Reference></SignedInfo><SignatureValue>BiFjeIuG7TW/DqIdklMNdaqRJLgbenphBcb51HGGH4WCdThgj2Oizkvfa6NRAwsE74qmyVLcfJIO2TK+if1yelHzUEde8ZvLwcruIFYWecK3OXDSDiGpYa3WdPwNUZrSRySSiCyb+fyYgz8BvZq3JjQRulOXnFhz4X3wXzoS6xMovmmVsOrdVTMjvT7l7ydEo1ucnEl5zjEnKih7WjCoElYENwEeG2HGf4Xqi43piaWXa9k7GY9k1idyrfJ7too+u7O7fhnhJ9OR0GR1KydbAPdSi5hmpZcziLn6xKCVW64w2bGCsT4N2vr+f5AhknSmjDa+9Wnyiar2uuLk+7eLmQ==</SignatureValue><KeyInfo><o:SecurityTokenReference
    xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><o:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA1">/YVCIdf+YFyKopRflv61uWov2vs=</o:KeyIdentifier></o:SecurityTokenReference></KeyInfo></Signature></saml:Assertion>
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] 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: LYNC01.mydomain.com
      X-Content-Type-Options: nosniff
      Cache-Control: no-cache
      Date: Tue, 10 Jun 2014 11:30:18 GMT
      Server: Microsoft-IIS/7.5
      X-AspNet-Version: 4.0.30319
      X-Powered-By: ASP.NET
      Content-Length: 1646
      Content-Type: application/vnd.microsoft.rtc.autodiscover+xml; v=1
      Expires: -1
    [6/10/2014 7:30:18 AM] [DEBUG] Parsing the response for URL https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[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"><User><SipServerInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipClientInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipServerExternalAccess
    fqdn="AccessEdge.mydomain.com" port="5061" /><SipClientExternalAccess fqdn="AccessEdge.mydomain.com" port="443" /><Link token="Internal/Autodiscover" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /><Link token="Internal/AuthBroker"
    href="https://lync01.mydomain.com/Reach/sip.svc" /><Link token="Internal/WebScheduler" href="https://lync01.mydomain.com/Scheduler" /><Link token="External/Autodiscover" href="https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root"
    /><Link token="External/AuthBroker" href="https://lync.mydomain.com/Reach/sip.svc" /><Link token="External/WebScheduler" href="https://lync.mydomain.com/Scheduler" /><Link token="Internal/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc"
    /><Link token="External/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc" /><Link token="Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications" /><Link token="Internal/Ucwa" href="https://lync01.mydomain.com/ucwa/v0/applications"
    /><Link token="External/Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications" /><Link token="Self" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user" /></User></AutodiscoverResponse>
    [6/10/2014 7:30:18 AM] [INFO] Server discovery has completed for http://lyncdiscoverinternal.mydomain.com/.
    [6/10/2014 7:30:18 AM] [DEBUG] Autodiscover full response for URL http://lyncdiscoverinternal.mydomain.com/ is <?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"><User><SipServerInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipClientInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipServerExternalAccess fqdn="AccessEdge.mydomain.com" port="5061"
    /><SipClientExternalAccess fqdn="AccessEdge.mydomain.com" port="443" /><Link token="Internal/Autodiscover" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /><Link token="Internal/AuthBroker" href="https://lync01.mydomain.com/Reach/sip.svc"
    /><Link token="Internal/WebScheduler" href="https://lync01.mydomain.com/Scheduler" /><Link token="External/Autodiscover" href="https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /><Link token="External/AuthBroker" href="https://lync.mydomain.com/Reach/sip.svc"
    /><Link token="External/WebScheduler" href="https://lync.mydomain.com/Scheduler" /><Link token="Internal/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc" /><Link token="External/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc"
    /><Link token="Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications" /><Link token="Internal/Ucwa" href="https://lync01.mydomain.com/ucwa/v0/applications" /><Link token="External/Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications"
    /><Link token="Self" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user" /></User></AutodiscoverResponse>
    [6/10/2014 7:30:18 AM] [DEBUG] SendRequest failed for https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [INFO] Automatic discovery results for http://lyncdiscoverinternal.mydomain.com/
    [6/10/2014 7:30:18 AM] [INFO] Access Location                          : Internal
    [6/10/2014 7:30:18 AM] [INFO] SIP Server Internal Access               : LYNC01.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] SIP Server External Access               : AccessEdge.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] SIP Client Internal Access               : LYNC01.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] SIP Client External Access               : AccessEdge.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] Internal Auth broker service             : https://lync01.mydomain.com/Reach/sip.svc
    [6/10/2014 7:30:18 AM] [INFO] External Auth broker service             : https://lync.mydomain.com/Reach/sip.svc
    [6/10/2014 7:30:18 AM] [INFO] Internal Auto discover service           : https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root
    [6/10/2014 7:30:18 AM] [INFO] External Auto discover service           : https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root
    [6/10/2014 7:30:18 AM] [INFO] Internal MCX service                     : https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:30:18 AM] [INFO] External MCX service                     : https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:30:18 AM] [INFO] Internal UCWA service                    : https://lync01.mydomain.com/ucwa/v0/applications
    [6/10/2014 7:30:18 AM] [INFO] External UCWA service                    : https://lync.mydomain.com/ucwa/v0/applications
    [6/10/2014 7:30:18 AM] [INFO] Internal Webscheduler service            : https://lync01.mydomain.com/Scheduler
    [6/10/2014 7:30:18 AM] [INFO] External Webscheduler service            : https://lync.mydomain.com/Scheduler
    [6/10/2014 7:30:18 AM] [INFO] Total server discovery time: 0.1 seconds
    [6/10/2014 7:30:18 AM] [SUMMARY_SUCCESS] Server discovery succeeded for unsecure (HTTP) internal channel against URL http://lyncdiscoverinternal.mydomain.com/
    [6/10/2014 7:30:18 AM] [SUBHEADING] Starting automatic discovery for secure (HTTPS) external channel
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to https://lyncdiscover.mydomain.com/[email protected]
    [6/10/2014 7:30:39 AM] [DEBUG] Exception encountered while sending an HTTP request to https://lyncdiscover.mydomain.com/[email protected]: An error occurred while sending the request.. Complete Exception: \r\nSystem.Net.Http.HttpRequestException:
    An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period
    of time, or established connection failed because connected host has failed to respond 205.XXX.XXX.94:443
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       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()
    [6/10/2014 7:30:39 AM] [ERROR] An error occurred while sending the request.
    Unable to connect to the remote server
    A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.XXX.XXX.94:443
    [6/10/2014 7:30:39 AM] [INFO] For troubleshooting, try using a browser to open the server discovery URL https://lyncdiscover.mydomain.com/[email protected]
    [6/10/2014 7:30:39 AM] [DEBUG] System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed
    because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.XXX.XXX.94:443
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       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.<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()
    [6/10/2014 7:30:39 AM] [SUMMARY_ERROR] Server discovery failed for secured external channel against https://lyncdiscover.mydomain.com/
    [6/10/2014 7:30:39 AM] [SUBHEADING] Starting automatic discovery for unsecure (HTTP) external channel
    [6/10/2014 7:30:39 AM] [DEBUG] Sending HTTP request to http://lyncdiscover.mydomain.com/[email protected]
    [6/10/2014 7:31:00 AM] [DEBUG] Exception encountered while sending an HTTP request to http://lyncdiscover.mydomain.com/[email protected]: An error occurred while sending the request.. Complete Exception: \r\nSystem.Net.Http.HttpRequestException:
    An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period
    of time, or established connection failed because connected host has failed to respond 205.XXX.XXX.94:80
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       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()
    [6/10/2014 7:31:00 AM] [ERROR] An error occurred while sending the request.
    Unable to connect to the remote server
    A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.XXX.XXX.94:80
    [6/10/2014 7:31:00 AM] [INFO] For troubleshooting, try using a browser to open the server discovery URL http://lyncdiscover.mydomain.com/[email protected]
    [6/10/2014 7:31:00 AM] [DEBUG] System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed
    because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.XXX.XXX.94:80
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       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.<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()
    [6/10/2014 7:31:00 AM] [SUMMARY_ERROR] Server discovery failed for unsecured external channel against http://lyncdiscover.mydomain.com/
    [6/10/2014 7:31:00 AM] [DEBUG] None, AutoExternalSecureD, AutoExternalUnsecureD, ManualDNSFail, ManualSecureD, ManualUnsecureD, AuthBrokerInternalLMXCheckGET, AuthBrokerInternalLMXCheckPOST, AuthBrokerExternalLMXCheckGET, AuthBrokerExternalLMXCheckPOST, MobilityMCXInternalLMXCheckGET,
    MobilityMCXInternalLMXCheckPOST, MobilityMCXExternalLMXCheckGET, MobilityMCXExternalLMXCheckPOST, LMXSIPServerInternalDNS, LMXSIPServerExternalDNS, MobilityUCWAInternalCheckPOST, MobilityUCWAExternalCheckPOST
    [6/10/2014 7:31:00 AM] [SUMMARY]
    [6/10/2014 7:31:00 AM] [SUMMARY_ERROR] Automatic discovery meant for external network access failed. Please verify the server requirements at http://go.microsoft.com/fwlink/?LinkId=278998 .
    [6/10/2014 7:31:00 AM] [SUMMARY] Automatic discovery meant for internal network access succeeded from an external network which could be a potential security concern.
    [6/10/2014 7:31:00 AM] [MAINHEADING] Starting the requirement tests for Lync Mobile 2010 App
    [6/10/2014 7:31:00 AM] [INFO] Please wait; this test may take several minutes to complete...
    [6/10/2014 7:31:00 AM] [INFO] Testing the app requirements using the following discovery response:
    [6/10/2014 7:31:00 AM] [INFO] Access Location                          : Internal
    [6/10/2014 7:31:00 AM] [INFO] SIP Server Internal Access               : LYNC01.mydomain.com
    [6/10/2014 7:31:00 AM] [INFO] SIP Server External Access               : AccessEdge.mydomain.com
    [6/10/2014 7:31:00 AM] [INFO] SIP Client Internal Access               : LYNC01.mydomain.com
    [6/10/2014 7:31:00 AM] [INFO] SIP Client External Access               : AccessEdge.mydomain.com
    [6/10/2014 7:31:00 AM] [INFO] Internal Auth broker service             : https://lync01.mydomain.com/Reach/sip.svc
    [6/10/2014 7:31:00 AM] [INFO] External Auth broker service             : https://lync.mydomain.com/Reach/sip.svc
    [6/10/2014 7:31:00 AM] [INFO] Internal Auto discover service           : https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root
    [6/10/2014 7:31:00 AM] [INFO] External Auto discover service           : https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root
    [6/10/2014 7:31:00 AM] [INFO] Internal MCX service                     : https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:31:00 AM] [INFO] External MCX service                     : https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:31:00 AM] [INFO] Internal UCWA service                    : https://lync01.mydomain.com/ucwa/v0/applications
    [6/10/2014 7:31:00 AM] [INFO] External UCWA service                    : https://lync.mydomain.com/ucwa/v0/applications
    [6/10/2014 7:31:00 AM] [INFO] Internal Webscheduler service            : https://lync01.mydomain.com/Scheduler
    [6/10/2014 7:31:00 AM] [INFO] External Webscheduler service            : https://lync.mydomain.com/Scheduler
    [6/10/2014 7:31:00 AM] [SUBHEADING] Starting tests for Mobility (MCX) service
    [6/10/2014 7:31:00 AM] [INFO] Verifying internal Mobility (MCX) service: https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:31:00 AM] [INFO] Successfully obtained the WS-Metadata Exchange (MEX) document using GET. The service did not require authorization.
    [6/10/2014 7:31:00 AM] [INFO] Verifying external Mobility (MCX) service: https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:31:00 AM] [INFO] Successfully obtained the WS-Metadata Exchange (MEX) document using GET. The service did not require authorization.
    [6/10/2014 7:31:00 AM] [INFO] Verifying internal Mobility (MCX) service: https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:31:00 AM] [WARNING] Failed to obtain the WS-Metadata Exchange (MEX) document using POST for https://lync01.mydomain.com/Mcx/McxService.svc/mex. The service did not require authorization.
    [6/10/2014 7:31:00 AM] [INFO] Verifying external Mobility (MCX) service: https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:31:00 AM] [WARNING] Failed to obtain the WS-Metadata Exchange (MEX) document using POST for https://lync01.mydomain.com/Mcx/McxService.svc/mex. The service did not require authorization.
    [6/10/2014 7:31:00 AM] [SUMMARY] Completed tests for Mobility (MCX) service
    [6/10/2014 7:31:00 AM] [DEBUG] None, AutoExternalSecureD, AutoExternalUnsecureD, ManualDNSFail, ManualSecureD, ManualUnsecureD, AuthBrokerInternalLMXCheckGET, AuthBrokerInternalLMXCheckPOST, AuthBrokerExternalLMXCheckGET, AuthBrokerExternalLMXCheckPOST, MobilityMCXInternalLMXCheckPOST,
    MobilityMCXExternalLMXCheckPOST, LMXSIPServerInternalDNS, LMXSIPServerExternalDNS, MobilityUCWAInternalCheckPOST, MobilityUCWAExternalCheckPOST
    [6/10/2014 7:31:00 AM] [SUMMARY]
    [6/10/2014 7:31:00 AM] [SUMMARY_SUCCESS]
    Your deployment meets the minimum requirements for Lync Mobile 2010 App.

  • Lync 2013 client connectivity to Lync Edge Pool

    Hi all,
    I have a question regarding Lync 2013 topology deployment
    I have read somewhere that
    The external interfaces of the Edge Server must not be routable by either clients or servers on the internal corporate network. The internal interface of the Edge Server must not be routable from the Internet. These routing principles must be enforced by deploying
    firewalls between the Edge Servers (an internal and an external firewall) or by enforcing strict routing at the network layer.
    Is the statement true? If it is, then there is no way for the internal client to talk directly to Edge server: its internal network interface doesn't have default route, so this interface can't talk to any client/server that is located on different subnet.
    (unless I have to manually add-route in command line for all the subnets in the internal network, which is not preferable)
    Any advise is greatly appreciated. Thanks

    The mentioned statement is true. You need to manually add static routes in to the Edge server. Only the external interface must have a Gateway configured. 
    http://thamaraw.com

  • Does Lync 2013 work with SQL 2012 always on Feature?

    Howdy,
    I'm not that even "ok" when it come to SQL :)
    so my question Does Lync 2013 Enterprise work with SQL 2012 "Always on" Feature or only Mirroring?
    Regards,
    T

     It will not be supported. Mirroring is your only option.
    If a post is helpful, please take a second to hit the green arrow on the left, or mark as answer, thanks.
    Jean-Philippe Breton | Senior Microsoft Consultant | MCTS, MCITP, MCT, Lync MVP

  • Questions on Lync 2010 to 2013 Addressbook Migration

    Hi Team,
    We are in the process of migrating the users from Lync 2010 to Lync 2013 pilot pool.
    https://technet.microsoft.com/en-us/library/jj205160.aspx
    According to the above article, basically the Lync Server 2010 Address Book is migrated along with the rest of your topology and don’t have to worry about the post migration steps if we don’t have customized settings such as GAL partition (By setting
    up an attribute ‘msRTCSIP-GroupingID’), customized AB normalization rules and customized phone normalization rules.
    Questions:
    1. How do we confirm that there is no customized settings of phone normalization, AB normalization and GAL partition in the existing Lync 2010 environment?
    2. Is there any powershell command to validate the current Lync 2010 settings?
    Please advise.
    Many Thanks.

    The grouping ID is not something you'd normally put in.  If all users can search for and see all other users, you'd be fine.
    For the AB normalization look for Company_Phone_Number_Normalization_Rules.txt in your Lync file share in
    X-WebServices-X\ABFiles (replace the X with whatever you see).  If you have one, you could copy it over to your new Lync 2013 file share.  This file is for normalizing phone numbers found in AD.  To validate current settings, you can run
    the BPA http://www.microsoft.com/en-us/download/details.aspx?id=4750 but if you're moving away from it, I wouldn't kill myself resolving issues.  From PowerShell, there
    are many things you could validate, is there something specific you're worried about?
    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
    This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Questions on SEFAutil deployment in Lync 2013

    Hello All,
    We have the following environment:
    Environment
    Background is that 4 geographically dispersed sites, each site has 15000 users, 2 data centres per site, and EE Lync 2013 FE Pool with 6-8 FE servers per data centre.
    Questions
    Does SEFAUtil need a dedicated server for large deployment like ours ? 75,000 users worldwide. 
    Recommendation of dedicated server was on Lync 2010. With Lync 2013 official stand is that you can run it on any FE. 
    But considering the user base, what is official Microsoft recommendation ? 
    Based on the above, if it can be installed on FE's is it best to install it on multiple Front end servers or all FE servers? 
    I'd assume all FE pools created as Application pools and install SEFAutil on all FE servers as you can use any those servers to run the util as long as the server is part of the FE pool defined in the application pool. 
    What is the recommendation for SEFAUtil for a deployment with multiple geographically dispersed sites ? 
    Does it need to be installed on all sites ? 
    What is the official recommendation ? 
    Different ports for all the application pools if we are creating individual application pool for all FE Pools ? 
    Or Can same port be used for all application pools ? 
    What additional load does SEFAUtil create on the FE servers ? Depending on answer to #1. 
    Please advise. MANY THANKS.

    Does SEFAUtil need a dedicated server for large deployment like ours ? 75,000 users worldwide. 
    Yes
    The SEFAUtil tool can be run only on a computer that is a part of a Trusted Application Pool. UCMA 3.0 must be installed on that computer. To run the tool, a new Trusted Application with the SEFAUtil application ID must be created on that pool
    Based on the above, if it can be installed on FE's is it best to install it on multiple Front end servers or all FE servers? 
    Wouldn't recommend that
    What is the recommendation for SEFAUtil for a deployment with multiple geographically dispersed sites ? 
    As long as user is part of Lync pool it will work based on the trusted application pool setting  
    Different ports for all the application pools if we are creating individual application pool for all FE Pools ? 
    NO
    What additional load does SEFAUtil create on the FE servers ? Depending on answer to Not recommended
    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" Regards Edwin Anthony Joseph

  • Questions in setting up Security group policies for Lync 2013 Users

    Hi Team,
    One of our customer looking for the below requirements:
    ü 
    B>>> Being able to split users in to groups. Would like to be able to split in to Departmental groups, the groups will be Service Delivery, Finance, Business Development, Clinical Services, Radiologists,
    SLA Team, Call Handlers.
    ü 
    B>>> Being able to control which users are able to contact or see other users. For example Limit Radiologists to only be able to see Service Delivery and Call Handlers
    We know that RBAC policies can be used by Administrator or Technicians who works remotely. However, a user sitting at a server running Lync Server is not restricted by RBAC.
    Question:
    Is there a way we can fulfill the above customer requirements in Lync 2013 environment?

    Hi,
    On Lync Server side, what you can do is to change the AD attribute msRTCSIP-GroupingID. You can set different value for different groups. Then each group will not able to search the users in other groups with user name. However, they can still search the
    users in other groups with the sip address.
    More details:
    http://blogs.msdn.com/b/jcalev/archive/2012/06/07/partitioning-lync-address-book-using-msrtcsip-groupingid.aspx
    Best Regards,
    Eason Huang
    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]
    Eason Huang
    TechNet Community Support

  • Users are unable to see their own profile photo although everyone else can see it in Lync 2013 client

    We have Lync 2013, Exchange 2010 and several AD
    servers in mixed mode 2003/2008.
    All user are unable to see their own profile photo
    either in the main Lync window, in the settings or in a chat although other user can see that their photo is there and displaying. The user experiencing the issue can go open Outlook 2013 client and will see their photo displaying correctly in the file menu
    (and elsewhere) here.
    I have confirmed this happens with any new users I set up as well. We have gone through a fair amount of troubleshooting with other Lync photo issues and simple fixes such as deleting the SIP cache folder etc proves to be ineffective.
    Our Cs-ClientPolicy Global is set to websearchonly.
     We have "Replicate this attribute to the Global Catalog" set
    for the ThumbnailPhoto attribute in AD.
    We are also forcing photos from AD only (or no photo) by setting the following:
    "Set-CsClientPolicy -Identity PhotosControl -DisplayPhoto
    PhotosFromADOnly"  
    and finally we are importing the photo in ad using this PS command:
    "Import-RecipientDataProperty -Identity "Test User"
    -Picture -FileData ([Byte[]]$(Get-Content -Path "C:\pictures\testuser.jpg" -Encoding Byte -ReadCount 0))"
    The pictures being uploaded are under 10KB in size.
    I have followed many threads and will provide any information I can to help find the problem. Thank you in advance.
    EDIT: I have also tried the following but with no success: https://knowledge.zomers.eu/misc/Pages/How-to-fix-your-photo-not-showing-up-in-the-Lync-client.aspx

    Hi Jdentremont,
    Lync client gets user photos by first querying the Address Book Web Query (ABWQ) service on the server, which is exposed through the Distribution List Expansion web service. The client receives
    the image file and then copies it to the user's cache to avoid downloading the image each time it needs to be displayed. The attribute values returned from the query are also stored in the cached Address Book Service entry for the user. The Address Book Service
    deletes all cached images every 24 hours, which means that it can take up to 24 hours for new user images to be updated in the cache on the server.
    To troubleshoot your problem, please follow the steps below:
    1.  Navigate to
     “X:\share\1-WebServices-1\ABfiles\000000000\000000000” folder. (ABS file share)
    You should see some photo files in this folder as the following screenshot.
    2. Delete all the files in this folder.
    3. On test PC, delete local cache files.
    %userprofile%\AppData\Local\Microsoft\Office\15.0\Lync\[email protected]
    4. Sign-in Lync with the test account.
    5. Go back to the ABS file share, check if there is any Photo file in the folder.
    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]

  • Lync 2013 Photos will not update from AD

    I recently joined a company who has Lync 2013, Exchange 2010 and AD is at a 2003 functional level. We are experiencing issues where Lync photos are not updating from AD correctly. I have checked the pre-reqs;  Replicate this attribute to the Global
    Catalog is set for the ThumbnailPhoto attribute. We are also forcing photos from AD only (or no photo) by setting the following:
    "Set-CsClientPolicy -Identity PhotosControl -DisplayPhoto PhotosFromADOnly"  
    and finally we are setting the photo in ad using:
    "Import-RecipientDataProperty -Identity "Test User" -Picture -FileData ([Byte[]]$(Get-Content -Path "C:\pictures\testuser.jpg" -Encoding Byte -ReadCount 0))"
    The pictures being uploaded are under 10KB and update within Outlook but never updates on Lync. I have also manually tried running the "Update-CsAddressBook" command from Lync and waiting 24hours + but the photo will not update in Lync. I have
    also tried a 3rd party utility that grabs the attribute directly from each DC individually and each node is displaying the correct photo. Any Ideas?
    EDIT: I did some more testing and can say with quite a bit of certainty there is something not quite right on the Lync side of things. I started with the company over a month ago and although users can see my original photo that was added to AD, I myself
    do not even see it loaded in my client yet. I've completly dumped my local Lync cache but no change. Is there a specific Lync Server service that handles retrieving/pushing photos to the Lync clients?

    Thank you so much for your reply, it was very helpful in understanding how the service is suppose to work however I have still not been able to correct the issue.
    What I have found by using your article may have narrowed down the scope of the problem. I was able to find that on our Lync file store, the cached contacts/photos are being updated daily (as expected) and actually contain the correct photos. I confirmed
    this be using abserver.exe on the .lsabs file and then locating the contactID for a few users I know are not updating properly. Once I have their contact ID I simply look for their .photo file in the cached files, copy it out to a different location and change
    it to a .jpeg. To my surprise the photos are actually the correctly updated ones, so why are these no getting to the users/clients? I have gone through and deleted my local cache folder as well as the registry key HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Lync
    but unfortunately no change on my Client. I still see these users original photos.
    Another piece of the puzzle; We are also working on letting mobile devices connect to our Lync infrasructure as well. This is not fully functional yet however during my testing I did get Lync client for android running for a little while and low and behold
    the pictures are actually correct on my mobile device!! Surely this must give some kind of clue?
    We are planning to upgrade Exchange from 2010 to 2013 and I hoping that leveraging the HiDef photo capabilities for Lync 2013 with Exchange 2013 may fix this issue. What do you guys think?
    More info on the environment:
    4 main sites + remote users
    ~7DC's - 2003 DFL (1 at each site + a few at HQ)
    3 Lync Front end servers (2013) (All located at central HQ)
    2 Lync edge server (2013) (All located at central HQ)
    1 - 2010 Exchange server (Located at central HQ)
    2013 Lync Client version 15.0.4675.1000 MSO 15.0.4675.1002 64bit
    About 100 HP 4110 Lync Edition Desk phones
    Users's workstations are either Windows 7 Enterprise or Windows 8.1 Enterprise

  • Lync 2013 do not show own photo

    We have Lync 2013 and Exchange 2010. I imported photos to our AD. In Outlook 2010 we can see our own photo, but Lync 2013 client do not display user own photo, but when user1
    write a message to user2, user2 receive message with user1 photo. This is  a global problem, not for one user.
    Can you help me in this case, because I didn't find any useful information?

    Ben, thank you for quick response.
    Our client policy:
    Identity                                                                        
                              DisplayPhoto
    Global                                                                        
                                   AllPhotos
    I imported only 96x96 pixels size photo. I also tried to import photo manually, but it not make any change in this problem.
    Import-RecipientDataProperty -Identity "Name Lastname" -Picture -FileData ([Byte[]]$(Get-Content -Path "C:\user.jpg" -Encoding Byte -ReadCount 0))
    If Lync 2013 user type his name in Lync search field and open his contact in Lync 2013 client, he able to see
    his photo, company name, phone numbers and etc...
    Lync 2013 clients and server have installed latest updates. 

  • Lync 2013 edge-no reverse proxy question

    I deployed lync 2013 edge server and no reverse proxy yet.I am trying to connect from my windows 7 machine with no luck and I can see a top reset on the firewall,my question is is reverse proxy required for the normal client to connect and do basic IM?
    Plz confirm.thx

    *****Update**********
    now when i am trying to test connevity using microsoft connecvitry analyer i am getting error realted to the external certifictare stating that " certificate couldn't be validated because SSL negotiation
    wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation." with UC troubleshotter i am getting the same.any idea?
    PS certificate is from Digi
    cert and i have checked the installation with thier tool and all was green
    regards
    The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.
    The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.
    The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.
    The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.
    The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.
    The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.
    The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.
    The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with
    the certificate installation.

  • Managing User Photos with On Premise Lync 2013 & Office 365

    Hello, I'm just looking for a little clarity in terms of expected behavior when using the various methods of modifying user images on these systems.
    For example, I've read that Lync 2013 can utilize the high resolution photo that is stored within the user's Exchange mailbox. That would work good in theory, but what about Lync users who do not have an Exchange mailbox (or UM voicemail box)? Presumably
    in that case you could use one of the AD attributes, thumbnailPhoto or jpegPhoto, the latter being preferred as it allows for higher resolution images. However in my experience, when using the jpegPhoto attribute, dirsync does successfully replicate the photo
    and it shows up on the O365 portal, but the on-premise Lync server/clients have inconsistent success displaying them. Some user's can see other user's photos, but they can see eachothers or vice versa and eventually the Lync client stops displaying any of
    these photos. 
    Ideally for us, if we could use the jpegPhoto attribute for all users, as opposed to using exchange attributes for some, that would be best, but is it designed to work this way?

    Hi FuzzMunk,
    I don’t think that Lync Server will
    synchronize the photo from
    JPEGPhoto attribute, as I know
    it only synchronizes the photo from
    thumbnailPhoto attribute in Active Directory.
    You can see the photo displayed on Office365 portal
     because it synchronizes the photo from both the
    thumbailphoto and jpegphoto attributes.
    Some related articles and cases for your reference.
    http://blogs.technet.com/b/nexthop/archive/2010/11/22/microsoft-lync-2010-photo-experience.aspx
    https://technet.microsoft.com/en-us/library/jj688150.aspx
    https://social.technet.microsoft.com/Forums/lync/en-US/3ffc4fcd-eefc-4eca-bc7e-bcd007157199/lync-photo-from-active-directory
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/53859480-a345-4ce0-a04e-9f1fc7a947c2/what-is-the-difference-between-jpegphoto-and-thumbnailphoto-attribute-in-ad?forum=winserverDS
    Best regards,
    Eric

Maybe you are looking for

  • Can One Export Contacts w/ iPad2?

    The first thing I wanted to do when I purchased my iPad 2 wasto export my contacts from Backup Assistant to my brand new iPad 2. Only problem is the export feature on the website doesn't seem to be available on my iPad. How can I do this? All I want

  • Weird issue with Jdeveloper

    Hi, I am using jdevloper version Studio Edition Version 11.1.1.2.0 and Build JDEVADF_11.1.1.2.0_GENERIC_091029.2229.5536. I opened my application and opened a project in the application Navigator but i was nt able to view the Project Explorere. Attac

  • I tried updating my iphone with syncing and now it says it is in recovery mode, waht do i do?

    my iphone 4s locked out when i tried to update the OS.  now the macbook says iphone is in recovery mode.  what do i do?

  • Vision builder calibration

    bonjour,  j'ai un projet pour guider un robot à des positions de prehension d'un objet (compteur d'energie) alors je voulais faire le traitement d'image avec VBAI pour traiter l 'image comme suivavt: 1- fixer un repere(X,Y) pour determiner les coordo

  • Crm table

    Hi Master, Pls somebody givr me the list of CRM Tables and transaction codes to view these tables. I'm not able to find out earlier 'crm table thread' posted by me only. If anybody can help me to find it out And points will be definatly rewarded. Tha