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.

Similar Messages

  • 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

  • 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

  • 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.

  • Lync 2013 Standard backup questions

    Hello
    I need to backup our Lync 2013 Standard Edition setup.
    We have Only one server atm.
    Looking at this post for inspiration:
    http://blogs.technet.com/b/heyscriptingguy/archive/2014/06/28/weekend-scripter-basic-lync-server-2013-backup-and-restore-part-1.aspx
    As far as i can understand, i don't need to do SQL backup at all? Or am i missing the point?
    Would I be able to restore my Lync from these 3 commands:
    Export-CSConfiguratiom, Export-CSLisConfiguration and Export-CsUserData - Is that enough for a disasterrecovery?
    And a bonus question:
    When i run Export-CSLisConfiguration . The export only contains the following:
    <?xml version="1.0"?>
    <LisDatabase xmlns="urn:schema:Microsoft.Rtc.Lis.Database.2008"/>
    Is that not incomplete somehow?

    That much would get you back up and running, yes.  But it may not be a "full" restore. 
    For example, if you have persistent chat data, it wouldn't necessarily be included in there.  If you have an archiving database where all IMs are sent, that information wouldn't be in the PowerShell exports above.  If you don't have a copy of the
    certificate and private key, that's lost.
    Typically, I run my own custom version of Lasse's backup script https://gallery.technet.microsoft.com/Backup-script-for-Lync-2013-aacbb9b9
    That pulls all the data, including your file stores, SQL exports, certificates, and everything into a single folder and zips it for you.  If you back those zips up, you'll have most everything. 
    Restoring directly back into SQL isn't the recommended method, if you did need to get back up you'd want to follow standard restore procedures by using the supported PowerShell, but you'll have other avenues to restore if needed and a more complete copy
    of your data.
    The LIS export may be complete if you don't have any Lync locations defined.  You'd typically enter these for 911 purposes.
    Check out Lasse's Channel 9 video as well:
    http://channel9.msdn.com/Events/TechEd/Europe/2014/OFC-B331
    Check out his backup series docs here as well:
    http://tech.rundtomrundt.com/search/label/Backup-Lync2013
    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.

  • Lync 2013 for 8000 user for 6 locations - Topology question

    Hello everyone,
    I have a project for Lync on 6 locations (Central site and 5 other branches) and would like to like to ask some questions regarding the topology of servers. 
    What I initially think would be required for those users is as following:
    1- 2 Pools (Central pool will have 3 Lync FE Enterprise) in the central site)  and another pool will have at least 1 FE Enterprise In each branch.. 
    2- 1 SQL BE +  Mirror + Witness for all the Front ends. 
    3- ONE SQL for Archiving and Monitoring
    4- One SQL for Persistent chat pool
    5- One Mediation server or a Pool with 2 Mediation servers. 
    6- One Edge Pool with 2 Edge Servers.
    The questions that I would like to ask regarding this topology is as following
    1- Would the front end servers distribution as I stated be convenient for such situation to avoid any issues with connectivity or HA ? And do pool pairing between the two pools for HA? 
    2- Would one Backend SQL with Mirror and Witness be enough for all front ends in all locations considering there's a 100 MB MPLS connection between all locations.? or is it better if I deploy SQL BE for each site? 
    3- In case of Edge Pool. how would the Public IPs distribution and the public/Internal DNS configuration be with the presence of Hardware and DNS load balancers?  
    I'm curious in things like 
    A- How many Public IPs would there be? 
    B- What are the Configuration of the Public DNS be like ? e.g. SIP A Name would point to how many IPs.
    C- How would the Hardware load balancer configuration be like ?
    4- Would a hardware load balancer be required to handle the traffic of all those numbers of users? or would one reverse proxy be enough?
    5- Customer required disaster site deployment so Is it possible to deploy Lync on another data center and do Pool pairing ?
    I would appreciate your suggestions and comments.
    Thanks 
    Mohammed JH

    Does that mean I will have to install SQL Backend in all 6 locations for FEs?
    - Each pool of Enterprise Edition FE's will require a SQL backend database.
    Do you mean I'll have to do the failover manually by powershell?
    - Yes, if acceptable you could use the resiliency built in to Lync server
    since you have multiple pools. If you loose SQL in Lync 2013 your front ends will maintain most functionality, if you loose an entire Lync pool PSTN calling can automatically fail over, however you will need to run a couple of PowerShell commands to fail the
    entire pool over.
    I have 6 different locations,
    so I think this means i'll install 6 different pools with one FE in each location and do Pool pairing between 3 of them with the other 3. do you think this make sense?
    - Ideally each pool should
    have 3 FE's. For the smaller sites
    I would look at using Lync Standard Edition. Standard Edition supports up for 5000 users on hardware or about 2500 on VM and it run's SQL locally. You only really need to use Enterprise Edition
    where you require the pool to be highly available.
    Does this mean that I need 6 Edges with each 3 Public IPs on each one? Can't I just deploy 1 pool with 2 Edges on it and associate
    them with all the pools .. I haven't tried that before to be honest.  
    - Yes you can do that. I would deploy 2 edge pools in 2 different sites with1 or 2 servers in each. This will give you failover options
    if you have an entire site go down.
    And btw I wonder how would the SIP, AV and Webconf names point to ....
    in case of all those IPs I think they will be configured on the load balancer right?
    - Youd have the public IP's on the load balancer, then you can use private
    IP's on the edge servers and load balance across the pool.
    I read microsoft says it's recommended for the HTTPS but with the number of users that will be enabled for Lync you mean that the Reverse proxy should handle all the traffic? I will be using IIS ARR should that be enough?
    - Each pool will have its own web services that need a reverse proxy so you could use IIS ARR in each location. Is that what you were thinking, or was the plan to centrally locate the reverse proxy for all pools?
    Hope its all becoming clearer :)
    Andrew Morpeth
    Lync Server Specialist - Auckland, NZ
    Check out my blog

  • Question about adding Distribution Groups to Lync 2013 clients

    Hello Everybody,
       Hopefully somebody can assist me with this issue. I created a Universal Distribution Group within our domain which consists of about 75 people. I logged onto the lync server and ran Update-CsAddressBook waited for it to complete and then
    followed Terence Luk guide to force the lync 2013 client update http://terenceluk.blogspot.com/2013/02/forcing-lync-2013-client-to-download.html However
    even after the update has completed I am unable to locate this group in the lync client any suggestions would be greatly appreciated. 

    Hi,
    Please type the complete sip address to search it.
    If the issue persists, please remove lync profile and sign in again.
    Kent Huang
    TechNet Community Support

  • Uninstall Lync 2013 question

    So I've tried building a new lync environment using sql mirroring and it looks like our DBAs didn't set up SQL correcty.  Now I'm stuck at a point where my topology has been published and it won't connect to sql.  I can't change the location either
    because the SQL location is bound to the CMS.  Since the Lync Front end service won't start, i'm having a hard time uninstalling the topology.  I have 4 front end servers published in my topology but only tried installing on the 1st FE server.
    Can I just wipe the OS and start over or what get thrown into AD that needs to get cleaned up?

    Unfortunately we couldn't do much of anything.  We tried to remove the enviornment via the topology builder, removing any other FE servers first, removing any confrencing (which also wouldn't go unless we used -force) and then tried to remove the environement
    and publish.  We got errors because I'm assuming it couldn't connect to sql in the first place and that the FE service wouldn't start.
    We wound up wiping the server.  We'll need to go in via ADSIEdit and clean up AD.  The problem is that we have an OCS 2007R1 environment that is using the same objects.
    Update:
    We had a backup of AD before the schema was upgraded for Lync 2013.  We mounted that backup and did a compare before/after install of lync.  We then just deleted every object out of AD that was put in by Lync 2013.  Hopefully that will be enough.
    We'll find out when we try to reinstall again.

  • Lync 2013 Enterprise load balancing on the front end and edge pool

    Hi,
    I am setting up a Lync 2013 Enterprise deployment consisting of a Front End pool (x2 FE servers) and an Edge pool (x2 Edge servers).  I'm seeing some conflicting advice regarding load balancing using hardware or DNS for the front end and the edge.
    On the front end I have 2 internal DNS records 'lyncfepool1.contoso.local' each of which map to one of the IPs of the FE servers.  I've used my details to populate the Detailed Design Planner excel spreadsheet and am told that I require a HLB to load
    balance my front end pool.  I'm aware of the need to load balance HTTPS traffic internally (which will be done by TMG) however other traffic to the front end (SIP, etc) can be balanced by DNS only, and not require a HLB?
    Can someone clarify the front end requirement?
    Also - looking now at the edge pool - this site again have two edge servers in a pool.  We are using a total of six private IP addresses, two per edge service (2 x av.contoso.com, 2 x sip.contoso.com and 2 x webcon.contoso.com).  These will be
    NAT'ed by the external firewall and directed to the respective external (DMZ) IP addresses on the Edge servers on port 443.  I know this isn't true roundrobin due to the intelligence of the Lync client when connecting (in that the Lync client will connect
    to one of the public IPs and if it can't connect, it will know to connect to the other service IP), however I want to clarify this set up, particularly the need to direct the external public IP traffic at the DMZ Edge IP specified in the topology builder.
    I've attached a basic diagram of the external/DMZ/Edge side which hopefully helps with this question
    Persevere, Persevere, Per..

    That is because you will always need HLB for a front-end server since it hosts the Lync webservices which use HTTP/HTTPS traffic.
    The description on the calculation tool also describes this correctly:
    Supports Standard and Enterprise pools (up to 12 nodes), with pure device-based load balancing or a combination of DNS load balancing and device-based load balancing (for
    Lync web services)
    You can use either Hardware or DNS loadbalancing for SIP traffic only, but you will always need a HLB for the webservices.  Both are applicable for the Front-End so you have either
    full HLB for both SIP and HTTP(S) traffic
    DNS LB for SIP traffic and HLB for HTTP(S) traffic
    Hope this is more clear :-)
    Lync Server MVP | MCITP Lync Server 2010 | If you think my post is the answer to your question, please mark it as answer so future visitors can easily find it.

Maybe you are looking for

  • How to select multiple addresses from the contacts list to send an email?

    How do I select multiple addresses from the contacts list at one time to send an email. Each time I select one, the address book closes and I have to touch the "+" key to open it back to select another address. Is there a way to select all of them at

  • Urgh...wrong album cover art...how do I take it off

    I have?a Zen Vision M, 30gb, and I have a problem removing unwanted cover art. I suppose it's not that big of a deal in the grand scheme of things...the songs play, and they're where their supposed to be. But I find this HELLA annoying !!! Since I've

  • If my Mini is running 64 bit can I run more than 4Gb RAM?

    I hear ALL over the place that the mini can not use more than 4Gb RAM. Is this a hardware limitaion of the motherboard/Processor? OR Is this due to the fact that mini's run at 32 bit? You can now easily run modern mini's at 64 bit: http://blog.leanop

  • KE30 - Form Based Report - TDD not appearing

    Dear COPA Experts, I am facing one strange issue with reporting of Top Down Distribution of Actual Data. After executing Top Down Distribution of Actual Data, i have checked T-Code : KE30 - Form Based Report but it does not shows me distributed data

  • I need a excel document to be used on a mac.

    I need a excel document to be used on a mac.  I cannot unlock or use the document.  Is there a way to do this? THANK YOU!