Lync 2013 On Prem - Front End Pool - Second server in pool becomes unavailable when first server is offline

We have one front end pool, that contains 2 front end servers running Lync Server 2013.
When the first server, LFE01 goes offline (to be restarted for instance), the second front end server LFE02 in the same pool's Lync services will suddenly stop and will refuse to start until LFE01's Lync services have started again.
During this time, the Lync client will go from full functioning mode whilst LFE01 is up and running, to reduced functionality (when LFE01 is restarting), to the user being signed out of Lync and not able to log back in. As soon as LFE01 comes back up, users
can log back in to Lync.
We'd ideally like LFE02 to take over the front end server role whilst LFE01 is restarting, and vice-versa.
Checking the event logs on LFE02, I can see the following errors when LFE01 is offline:
This process was not able to update its health status
The Audio-Video Conferencing Server failed to send health notifications to the MCU factory at https://frontendpool.contoso.com:444/liveserver/mcufactory/. 
Failure occurrences: 30, since 7/11/2013 3:40:38 PM.
Cause: Either the Front End service is not running, or poor network connectivity.
Resolution:
Verify that the Front End Service is available, and its machine is visible over the network.
This process was not able to update its health status
The IM Conferencing Server failed to send health notifications to the MCU factory at https://frontendpool.contoso.com:444/liveserver/mcufactory/. 
Failure occurrences: 30, since 7/11/2013 3:40:42 PM.
Cause: Either the Front End service is not running, or poor network connectivity.
Resolution:
Verify that the Front End Service is available, and its machine is visible over the network.
Server startup is being delayed because fabric pool manager is initializing.
Cause: This is normal when Pool is bootstrapped and indicates that the Front-End is waiting for a quorum of other Front-Ends to be started.
Resolution:
If this event recurs persistently, ensure that 85% of the Front-Ends configured for this Pool are up and running. For 2 or 3 machine Pools, initial cold-start of the Pool requires all machines to be started. If multiple Front-Ends have been recently
decommissioned, run Reset-CsPoolRegistrarState -ResetType QuorumLossRecovery to enable the Pool to recover from Quorum Loss and make progress.
Does the first server in the pool need to be up at all times for the second server to be running? If so, I may need to re-plan my redundancy.

I can't believe how inaccurate these statements are. 
Yes as per Microsoft it is best practice to have 3 FE in a pool but that absolutely does not mean that if you have 2 FE server in a pool that your pool will stop working!!
In case when you do have 2 FE servers in a pool your Back End primary database server will act as a vote to keep the quorum for single server still left in a pool and all your clients will keep operating in a pool with one FE still running. 
The problem with having 2 FE in a pool as per Microsoft documentation is as follows:
If one of the two Front End Servers goes down, you should try to bring the failed server back up as soon as you can. Similarly, if you need to upgrade one of the two servers, bring it back
online as soon as the upgrade is finished.
If for some reason you need to bring both servers down at the same time, do the following when the downtime for the pool is finished:
The best practice is to restart both Front End Servers at the same time.
If the two servers cannot be restarted at the same time, you should bring them back up in the reverse order of the order they went down.
If you cannot bring them back up in that order, then use the following cmdlet before bringing the pool back up:.
http://technet.microsoft.com/en-us/library/gg412996.aspx
I tested this in my environment which I currently am running with 2 FE servers and I can categorically confirm that pool will continue operating. 
However, with all this said I did notice that clients with connection to FE server that is shut down take anywhere from 2-9 min to reconnect. I was trying to figure out why such a long delay until clients reconnect. Possibly it might be because there are
2 FE servers in a pool and Back End server is taking a while to vote in turn delaying auto reconnect process for clients. Second possibility that I'm looking into is that we deployed HLB for sip traffic internally as well and I'm curious if using DNS LB would
fix this delay.
I'm just so disappointed how inaccurate some of these accepted answers above are.

Similar Messages

  • Configuring Lync 2010 Mobility with Front end and Edge Server

    I have been racking my brain the past week trying to figure out how to get the lync edge server working properly and how to get the mobility service working properly.
    Currently I have 1 front end server that is configured and working.  I have one edge server that has been configured according to nearly every online help I could find along with public CERT.
    If I use microsoft's online connectivity test and I run the test for
    Lync Server Remote Connectivity Test everything passes.  I am also able to connect to lync using a windows lync client from outside of the internal network however I have to specify the server name as being sip.ourdomain.com I cannot get connected using
    autodiscover.
    When I run the Lync Autodiscover Web Service Remote Connectivity Test it fails due to SSL error to lyncdiscover.ourdomain.com which then lead me down the path that I needed to install
    the Mobility service but it also tells me that I may need to update our SSL cert as well.
    This is where I am getting confused and would like to be pointed in the correct direction.
    When I installed mobility service on the front end server it created the autodiscover section in IIS.  If I am inside our network I can browse to it without any issue.  Where I am confused at this point is how to either setup DNS or how to configure
    the edge server to use autodiscover.
    Do I need to setup an additional public IP and point lyncdiscover.ourdomain.com to the IP of our front end server or to our edge server?  If I have to point this to our front end server then that would mean that I use one public IP that goes to 443,
    444 and 5061 for our edge server and then I would need one public IP that goes to ports 443 and 80 that get redirected to ports 4443 and 8080 on our front end server?  If that is the case then do I have to get an external cert for the front end server
    that contains lyncdiscover or can clients connect if it is just using the self signed cert from the domain?
    This is where I am getting confused at and hopefully some nice folks out there can clarify this for me so I can get this resolved.
    Thank you
    KK

    You need an additional public IP to point to a reverse proxy, which will listen on port 443 and proxy requests to your front end server on port 4443 (notice the extra 4).  You can use IIS ARR, Web Application Proxy, or whatever else you may have for
    this purpose, but you need to ensure you redirect port 443 to port 4443.  This reverse proxy cannot be collocated on your front end server or edge, you'll need a separate box or appliance. 
    Beyond Lyncdiscover, you'll want to do this for your external web services FQDN as defined in the topology builder and your meet and dialin URLs too.  You'll want a third part cert for all of this (though it doesn't need to be installed on the front
    end, just the reverse proxy) so that you don't need to install any internally signed root certs on anyone's smartphone.
    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.

  • Time out error  on front end ( 60 seconds) developed in web dynpro ABAP

    Hi all
    I am getting TIME OUT error ( ERROR :-  Connection to partner break in 60 seconds) on front end (on web) because in SAP backend there is a function module excuting and taking 3 minutes. But on front end developed in web dynpro ABAP time out is coming in 60 seconds.
    Please help me how can i increase this TIME OUT time on front end more than 60 seconds.
    Please help as soon as possible

    Hi,
    see the <a href="http://help.sap.com/saphelp_nw70/helpdata/en/7b/72092aaa1342c5a3af7ce0b9a11ff9/frameset.htm">Documentation</a> and
    <a href="http://help.sap.com/saphelp_nw70/helpdata/en/78/9852b7c06b11d4ad310000e83539c3/frameset.htm">this</a>
    Regards, Heidi

  • SChannel Errors on Front Ends Affecting Client Connectivity Between Pools

    We have an SE pool in Asia.  A user tried attending a conferencing hosted on the US EE pool but received an error.  Looking in the logs I see the following error (30988) in the Lync events on the Asia server:
    Sending HTTP request failed. Server functionality will be affected if messages are failing consistently.
    Sending the message to https://uslyncpool.company.loc:444/LiveServer/Focus failed. IP Address is xxx.xxx.xxx.xxx. Error code is 2EFE. Content-Type is application/delegateAuthz+xml.
    Http Error Code is 0.
    Cause: Network connectivity issues or an incorrectly configured certificate on the destination server. Check the eventlog description for more information.
    Resolution:
    Check the destination server to see that it is listening on the same URI and it has certificate configured for MTLS. Other reasons might be network connectivity issues between the two servers.
    Followed by the warning (32052):
    An HTTP application request sent to a Service timed-out. Requests will be retried but if this error continues to occur functionality will be affected.
    Url: https://uslyncpool.company.loc:444/LiveServer/Focus
    Cause: Network related error or destination service being non-functional.
    Resolution:
    Ensure that the Service is provisioned and functioning correctly. If any network related errors are reported by the Service ensure that they are resolved.
    On one of the US servers (we will call it serverB) I see this Lync event (14428) around 25 seconds later:
    TLS outgoing connection failures.
    Over the past 28 minutes, Lync Server has experienced TLS outgoing connection failures 2 time(s). The error code of the last failure is 0x80090322 (The target principal name is incorrect.) while trying to connect to the server "serverA.company.loc"
    at address [xxx.xxx.xxx.xxx:5061], and the display name in the peer certificate is "Unavailable".
    Cause: Most often a problem with the peer certificate or perhaps the DNS A record used to reach the peer server. Target principal name is incorrect means that the peer certificate does not contain the name that the local server used to connect. Certificate
    root not trusted error means that the peer certificate was issued by a remote CA that is not trusted by the local machine.
    Resolution:
    Check that the address and port matches the FQDN used to connect, and that the peer certificate contains this FQDN somewhere in its subject or SAN fields. If the FQDN refers to a DNS load balanced pool then check that all addresses returned by DNS refer
    to a server in the same pool. For untrusted root errors, ensure that the remote CA certificate chain is installed locally. If you have already installed the remote CA certificate chain, then try rebooting the local machine.
    We are also seeing the following SChannel (36884) error on our servers (but not at the same time as the errors above):
    The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is serverA.company.loc. The SSL connection
    request has failed. The attached data contains the server certificate.
    We are seeing this periodically and from other locations.
    What is odd is serverA seems to expect to find its name in serverB's certificate.  This is a two server EE pool and I have never seen that requirement.  We have the pool name and each server name in the SANs along with all the other typical names
    (sip, lyncdiscover, etc.) on both servers but I have never seen anything state that the FQDNs of all machines in the pool need to be in the certificate on every server.  I fact, the wizard doesn't even do it.
    Am I wrong on that?
    Lync Server 2010 CU7, hardware load balanced

    You need to install each other’s Root Certificate in local computer’s Trusted Certification Authorities store. Delete the duplicated certificates in personal store on server in both Asia and US.
    Check if you can ping FQDN uslyncpool.company.loc from server in Asia.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Lync 2010 Standard Edition Front-End and Edge Cerificate Renewal issue

    Hi Experts,
    I have a client with Single Standard Edition FE server and 1 Edge server and both are using PUBLIC certificates. It also has a reverse-proxy server (F5 HLB) with wildcard certificate installed. The FE and Edge certificates are about to expire and the client
    now wants the ff.
    1. Internal Certificate from Internal CA server for FE
    2. External Certificate from Public CA for Edge
    What I did was,
    A. For Internal Cert - I generated a CSR from MMC cert manager using custom request from the FE server and have it signed by the Internal CA. Reason I did that was, everytime I requested the CSR from Lync Certificate Wizard, it is getting the certificate
    template not supported by the Internal CA.
    B. For External Cert - I requested the Edge external CSR thru Lync Certicate Wizard and submitted to the client for public CA renewal.
    When I installed both certificates, internal lync works fine but anything external (i.e. external lync access, mobile, federation) do not work anymore.
    So I decided to roll back the certificates and everything went back to normal?
    Question is, what steps or process did i miss or gone wrong? Hope for your response. Thank you in advance.

    Hi DaxZilla,
    You also need to request a certificate to internal interface of Edge Server from internal enterprise certificate authority.
    The certificate for the external edge interface should contain SANs as below:
    SAN=Access Edge service FQDN
    SAN=Web conference service FQDN
    SAN=SIP domain FQDN
    Mobile client goes through reverse proxy server to sign in. It is not related with Edge Server. Check the certificate on reverse proxy is not expired.
    Best Regards,
    Lisa Zheng
    Lisa Zheng
    TechNet Community Support

  • 2 Front End Servers with reporting enabled in topology but only one server shows reports

    Hi,
    We have 2 Front End Standard pool servers with resiliency enabled between them. The monitoring service is configured in the topology so that both Front End Servers point to the same monitoring database. We have half our users homed on 1 Front
    end and half the other users sitting on the other Front End. In the Reports we can only see information on Audio calls made from users that are sitting on our Primary Front End Pool Server however we cannot see call information from users that are sitting
    on the other front end server?
    Thanks, Kevin

    We have applied the backend updates and verified the config by running Test-CSDatabases cmd-let . I ran enable-cstopology and ran bootstrapper.exe and rebooted both Front End Servers, however we are still unable to see monitoring data of users
    homed on our second Lync Front End server.
    Any other suggestions? Thanks for responses so far, appreciate the assistance!
    DatabaseName               ExpectedVersion            InstalledVersion
    xds                        10.13.2                   
    10.13.2
    lis                        3.1.1                     
    3.1.1
    rtcxds                     15.13.1                    15.13.1
    rtcshared                  5.0.1                      5.0.1
    rtcab                      62.42.2                    62.42.2
    rgsconfig                  5.5.1                      5.5.1
    rgsdyn                     2.2.1                     
    2.2.1
    cpsdyn                     1.1.2                     
    1.1.2
    and ......
    DatabaseName               ExpectedVersion            InstalledVersion
    LcsCDR                     39.82.2                    39.82.2
    QoEMetrics                 62.90.1                    62.90.1

  • Lync 2013 Upgrade

    At the moment we have 2 sites each with one Lync 2010 server. We don't have any edge server and don't plan to have any as we won't be federating with any external companies nor want to have
    the ability to access the Lync from internet.
    Can you suggest the Lync 2013 design for High availability and Site resilience. Both should be automatic and shouldn't need any administrator intervention. Also the best pratice in regards to
    splitting the roles.
    Malli Boppe MCITP Enterprise Messaging Exchange 2010

    Very simply, if you want high availability, in each site you'll need three (three is the recommended minimum due to Lync 2013 quorum design) front end servers with the HTTPS services load balanced using a hardware load balancer.  For back
    end high availability, each pool should be mirrored SQL 2012 servers, two in each site.  These two pools will then be paired for site resiliency.  The site failover is not automatic, you will need to invoke the failover with a PowerShell command
    invoke-cspoolfailover (http://technet.microsoft.com/en-us/library/jj205189.aspx).   The failure of a single server in a site otherwise and the reconnection of any clients would
    be automatic.
    I trust that if you're running each site on one server now, then those three should be enough.  For role splitting, it depends on what features you want.  If you want to share PowerPoints, you'll want to split off the Office Web Application role,
    if you want HA, then you'll want multiples for the organization in a farm.  If you're running Enterprise Voice, it's up to you to collocate the mediation role, however I prefer to split it off for ease of troubleshooting. 
    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

  • Mac Lync 2011 and Lync 2013 - Autodiscovery not working

    We're currently setting up a Lync 2013 topology including Front End Pool and Edge Server.  I've been told that the Lync 2011 client should work with lyncdiscover and lyncdiscoverinternal as it does for IOS and Windows.
    However looking at the logs being generated by the Lync 2011 client this doesn't seem to be the case.  I'm seeing
    sipinternal, sip, sipexternal when Lync 2011 is set to AutoConfigure.  I do not have any of these configured.
    If I manually specify lyncdiscover and lyncdiscoverinternal the logs show it's starting to find the Front End Servers, but still errors.
    What am I doing wrong?

    Hi,
    Please add the following SRV records in internal DNS Server:
    _sipinternaltls._tcp.sipdomain.com
     _sipinternal._tcp.sipdomain.com
     _sip._tls.sipdmain.com
    Then flush the DNS cache on the local Mac computer, then test the issue again.
    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- Standard Edition - Persistent Chat

    What is the capacity of the Persistent Chat if it is collocated on Lync 2013 Standard edition front end ?
    ie, number of chat rooms /usage?
    In a Lync 2013 standard edition deployment if Persistent Chat is on separate server, can the SQL be offloaded to central SQL cluster enviornment or  it will be held on the local server?

    I haven't seen a chart that really defines the capacity, and it's difficult to measure because it's difficult to say how active the rooms will be or how much content you'll generate.  That much is different from organization to organization. 
    There are some guidelines in general here:
    https://technet.microsoft.com/en-us/library/gg615006(v=ocs.15).aspx but they don't really touch the standard model.
    The pChat database can be offloaded to a central SQL cluster if you'd prefer, there are no requirements to collocate it with the local Lync databases.
    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 standard number of Backends required and pool paring setup?

    Hi
    I am in the process of putting together a lync 2013 implementation. The plan is to use lync 2013 standard as IM and Presence are the only requirement we have approx. 3000 users
    we have two sites
    Site A (Primary)
    x 2 FE-A1 FE-A2 Lync 2013
    x1 BE-A1 Lync 2013
    Site B (D.R)
    X 2 FE-B1 FE-B2 Lync 2013
    X1 BE-B1 Lync 2013
    what I want to know is
    1. If Site A has two FE servers each will require there own pool if I pair FE-A1 with FE-A2 can I also pair FE-A1 with FE-B1 and the same for 2?
    2. Can the servers FE-A1 and FE-A2 use the same BE server or should I be using a separate server for each?
    3. In this design I was thinking of using two edge servers 1 at each site that would be published using TMG, would this be correct, this would be for IPhone mobile users to use.
    thanks in advance
    J

    1)  If site A has to FE servers, and you go with Standard edition, they would be their own pools.  If you wanted HA you could put three enterprise servers together into a single pool and load balance them.  If you pair FE-A1 with FE-A2, those
    two pools cannot be paired with any other pool.  You also can't Pair FE-A1 to FE-A2, then FE-A2 to FE-B1. 
    2) Your diagram looks like Lync 2013 for the back end, it would actually be SQL, and this would specifically apply if you're using Lync enterprise.  If the Lync front end servers are in the same pool, they can use the same backend, if they're not they
    need separate back ends.
    3) Edge servers would be published with a standard firewall, if TMG is your firewall that would work.  If TMG is only being used as a reverse proxy, you would use it to publish your web services on your front end servers.  Either way, you'll need
    to also publish the web services on your front end servers to the Internet for mobile clients to function.
    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.

  • Front End pool failed over

    Hi all,
    1. I setup a pool with three Front End servers (FQDN of pool is pool.site1.sip96x2.com and it's pointed to IP address of three Front End servers). Everything works fine. But When I disable network interface on FE1 and FE2, the Lync clients are disconnected.
    I haven't understood clearly how the Lync clients failed over in a pool? Please clarify to me.
    2. I have two central site (Root site and Primary site, they have different domain sip96x2.com and site1.sip96x2.com). The simple URL dialin is pointed to Front End server at Root site. So if the link between Root site and Primary site is down, how can the
    users at Primary site connect to dialin URL? 
    3. In building topology for Front End pool, I checked Override FQDN internal web service and the FQDN is "poolint.site1.sip96x2.com". I created three A records "poolint.site1.sip96x2.com" and pointed to three IP addresses of Front End
    servers. Is it right?
    Thanks so much!

    Ah ok, well first thing if I am reading this correctly, pool pairing Standard with Enterprise is not supported. You should only pair Standard with Standard and Enterprise with Enterprise (even though topology builder won't stop you) Take a look here for
    support scenarios http://technet.microsoft.com/en-us/library/jj204697.aspx
    To deal with the simple URLs in the event of failover you need to add them using Powershell. Take a look at this article which explains and gives an example: http://blogs.perficient.com/microsoft/2012/01/configuring-simple-urls-for-multiple-lync-pools/
    If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
    Georg Thomas | Lync MVP
    Blog www.lynced.com.au | Twitter
    @georgathomas
    Lync Edge Port Check (Beta)

  • 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

  • Problems with one of the front-end servers (service wont start)

    Hi,
    Having a pool with two front-end servers (Lync Server 2013 on Windows Server 2012) and I cannot get one of servers to work properly. 
    The Front-End service is not starting.
    Have removed both servers from the topology and installed one at the time. When adding the second server to the pool the service never starts, its in starting state and a bunch of error messages appears:
    - Server startup is being delayed because fabric pool manager is initializing.
    Cause: This is normal when Pool is bootstrapped and indicates that the Front-End is waiting for a quorum of other Front-Ends to be started.
    - Pool Manager failed to connect to Fabric Pool Manager.
    Cause: This could happen because insufficient number of Front-Ends are currently active in the Pool.
    I have tried restarted one at the time, both at the same time...
    Reset-CsPoolRegistrarState -ResetType QuorumLossRecovery
    Reset-CsPoolRegistrarState -ResetType FullReset
    I have also had a look at the kb saying that there could be a certificate issue. So I have ran that script but no certificate is misplaced in any store.
    I have removed the front-end certificates and requested new ones from the internal CA, I have also done the same to the OAuth certificates.
    How to proceed?

    Hi there,
    if you are still receiving, the same error, please try to shutdown the first Front-End Server, and give time for the services to start, however I would like also to add that with Lync server 2013 the Enterprise pool requirements is to have 3 Front-End Servers
    in a pool instead of 2, because  of introducing the brick model  architecture.
    Regards,
    Charbel Hanna
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

  • Front End Service is not starting

    Hi ,
    Any one can help me to resolve this issue.
    I have one enterprise edition front end server .if i try to start the front end service it give the following error
    Server startup is being delayed because fabric pool manager is initializing.
    Cause: This is normal when Pool is bootstrapped and indicates that the Front-End is waiting for a quorum of other Front-Ends to be started.
    Resolution:
    If this event recurs persistently, ensure that 85% of the Front-Ends configured for this Pool are up and running. For 2 or 3 machine Pools, initial cold-start of the Pool requires all machines to be started. If multiple Front-Ends have been recently decommissioned,
    run Reset-CsPoolRegistrarState -ResetType QuorumLossRecovery to enable the Pool to recover from Quorum Loss and make progress.

    If understand the problem Correctly You one Lync enterprise edition installed is that right?
    If yes Please note For a recommended Lync Server 2013 EE pool deployment, there should be at least three Lync Server 2013 front-end servers in the EE pool.
    http://technet.microsoft.com/en-us/library/gg412996.aspx
    We recommend that all your Enterprise Edition Front End pools include at least three Front End Servers
    Also refer Why 3 server pool?
    http://social.technet.microsoft.com/Forums/lync/en-US/1e277415-01b0-4123-a5bc-260909368d5b/why-3-server-pool?forum=lyncdeploy
    If you just want one Lync server please install Lync Standard Edition
    Front End Pools with Two Front End Servers
    We do not recommend deploying a Front End pool that contains only two Front End Servers. If you do ever need to deploy such a pool, follow these guidelines:
    If one of the two Front End Servers goes down, you should try to bring the failed server back up as soon as you can. Similarly, if you need to upgrade one of the two servers, bring it back online as soon as the upgrade is finished.
    If for some reason you need to bring both servers down at the same time, do the following when the downtime for the pool is finished:
    The best practice is to restart both Front End Servers at the same time.
    If the two servers cannot be restarted at the same time, you should bring them back up in the reverse order of the order they went down.
    If you cannot bring them back up in that order, then use the following cmdlet before bringing the pool back up:.
    Reset-CsPoolRegistrarState -ResetType QuorumLossRecovery -PoolFQDN <FQDN>
    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

  • Lync 2013 sign in problem

    well i did setup everything from scratch according to the microsoft free eblook about lync 2013
    and i joined a win 8.1 pc to my domain
    when i try to login it ask me for password but when i enter it it says that 
    cant sign in to lync
    you didnt get signed in .it might be your sign-in address or logon credentials, so try those again. if that doesnt work,contact your support team
    im desperate guys , plz help me

    Hi AliReza Baensaf,
    You can follow the steps below to troubleshoot the issue.
    1. Please check whether or not all the Lync services are running.
    2. Make sure the required DNS records are set up.
    DNS requirements for Front End pool in Lync Server 2013
    DNS requirements for automatic client sign-in in Lync Server 2013
    3. Please try manual configuration to test the issue.
    4. You can enable Lync client logging and use snooper to analyze it.
    5. Install the updates for both Lync server and Lync client.
    Best regards,
    Eric

Maybe you are looking for