LYNC 2010 Enterprise Pool Front End Servers

Can we mix Windows 2008 R2 Enterprise Edition and Standard Edition virtual servers in same LYNC 2010 Front End Pool?
Tek-Nerd

Agree with Lisa,Lync Server virtualization supports a mix of operating systems. For example, a host server running Windows Server 2012 R2 that runs virtual servers that run Windows Server 2008 R2 is supported.
You cannot mix different types of servers within the same pool. All servers within the same pool must either be physical or virtual
Also you can refer below link
http://technet.microsoft.com/en-us/library/gg399035.aspx
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"

Similar Messages

  • Move cms from Lync 2010 enterprise pool to Lync 2013 enterprise pool

    Hi!
    We recently moved all our users from our 2010 ent pool to our new 2013 ent pool.
    we have read the http://technet.microsoft.com/en-us/library/jj688013%28OCS.15%29.aspx
    In step 7, it says that we should run the deployment wizard. Do we have to do this on all servers in the pool?
    regards,
    Uc

    Hi,
    yes you should run it on all front-End servers in the pool
    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

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

  • 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

  • Few users are unable to sign in after we added 2 more front end servers in existing pool?

    Hello, 
    We have recently extended the Lync 2010 Enterprise pool with 2 Front end servers.  Now we have totally 6 Front end servers. 
    After this change some users are unable to login. Error message: "Cannot loggin as server is temporarily unavailable"
    Captured, client logs and received the following:
    ms-diagnostics: 4004;reason="Credentials provided are not authorized to act as specified from URI";
    We have the following security settings on the newly added front end servers:
    Network security: Minimumsecurity for NTLM SSP Based clients - set to - Require 128-bit encryption 
    In other existing front end servers, it has been set to - No minimum. 
    Questions:
    1. Is that the issue for signin failure?
    2. Do we need to change this option to - No minimum in new servers and reboot it?
    Please advise. MUCH THANKS. 

    Hello 
    Those clients running in Windows 7 OS. And the error is different:
    "Cannot loggin as server is temporarily unavailable"
    Thanks

  • Front End servers within same Pool on different subnets

    The customer is looking to have Amazon AWS host Lync 2013, and despite Lync 2013 having built in HA via Pools, Amazon wants to split the Pools across two of their availability zones (AZ ). An AZ is nothing more than a metropolitan area network, or simply
    a data center located a few miles away. Essentially they want to split the Pools between their two AZs.
    I know that for Lync 2013, the only stretch Pool supported is the Persistent Chat server Pool, and that Front End Pools, Edge Pools, or Mediation Pools are not supported.
    Amazon states that the latency between their AZs is from 1 - 5 ms, which is well within tolerance, though they state that the AZs all have unique subnets.
    I know that none of this is supported, though I am being requested as to why it isn't.
    Forgetting about latency, is this not supported because all servers within a Pool must share the same IP subnet? Is this coded within Lync that only Pools within the same subnet will work? I think it is as with Lync 2010, a stretched VLAN was required for
    a FE Pool to work, which implies the same subnet.
    While on this, a Central site does not mirror that of an AD Site, where a Central Site is a reflection of Pools within an area. So can a Central Site span two AD sites? I believe the answer is yes when one considers that a remote branch office can also be
    its own AD site. The reason for asking this question is I am attempting to see if if the Central Site might also have something to do as to why stretched Pools aren't supported.
    Thanks!
    Christian
    Christian Frank

    Hi Guys,
    Just saw both of your responses. I totally agree that it isn't supported, and what Amazon has been proposing is essentially adding their HA via a redundant AZ so that their infrastructure is redundant, which is their HA (I don't agree!).
    What I am looking for is something a bit deeper as to why. For example, when Lync 2010 had the stretched FE Pool between two locations, it was done via a stretched VLAN, which implies that the servers on both ends must be on the same subnet.
    Amazon wants to stretch all the Pools, between their data centers, so they can say that the Lync infrastructure is highly available, though at each data center, the subnets will be different, and that is what I am attempting to validate.
    I know this isn't supported, though is it because the members within the pool would come from different IP subnets, and Lync 2013 is coded to expect fellow members to be within the same subnet? That essentialy is what the case of Lync 2010 FE Pools was when
    they stretched them. And if you go back to Exchange 2007, stretched VLAN was back then a way to create geo-clustering also, which is no longer the way.
    Frankly, I think it has to do with subnet, and I believe it has to do with how the Windows Fabric is written, and what it is expecting to see. I really think this is the case, which explains the whys as to how stretched Pools are no longer supported any
    longer. Yes?
    Thanks!
    Christian Frank

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

  • Could you tell me if it would be supported to pair a two node enterprise edition front end pool inc mirror sql with a one node enterprise edition front end pool inc single sql?

    Hi all,
    Could anyone tell me if it would be supported to pair a two node enterprise edition front end pool inc mirror sql with a one node enterprise edition front end pool inc single sql?
    MUCH THANKS.

    The answer from TechNet found at http://technet.microsoft.com/en-us/library/jj204697.aspx Is, and I quote:-
    Enterprise Edition pools can be paired only with other Enterprise Edition pools. Similarly, Standard Edition pools can be paired only with other Standard Edition pools.
    Also, "Neither Topology Builder nor topology validation will prohibit pairing two pools in a way that does not follow
    these recommendations. For example, Topology Builder allows you to pair an Enterprise Edition pool with a Standard Edition pool.
    However, these types of pairings are not supported."
    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"

  • 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

  • Search on App and Front End servers

    Hi, we migrating from SharePoint 2010 to SharePoint 2013. And I have a question for Search Service Application.
    On SharePoint 2010 Search application we have Crawl hosted on APP server and index partitions hosted on Front-end servers.
    On SharePoint 2013 Search application in Search Application Topology I see only App server with all components marked as OK.
    Is it enough to have only one App server in Search Application Topology. Or should I add Front-end server to Search Application Topology too?

    Hi,
    For a good user experience and performance, it is recommend that WFE servers hold Query processing component, App servers hold Analytics processing component,Content processing component,Crawl component,Search administration component. Here is the PowerShell
    Script for Configuring Enterprise Search Topology:
    $hostWFE = Get-SPEnterpriseSearchServiceInstance -Identity "sp"
    $hostApp = Get-SPEnterpriseSearchServiceInstance -Identity "app"
    Start-SPEnterpriseSearchServiceInstance -Identity $hostWFE
    Start-SPEnterpriseSearchServiceInstance -Identity $hostApp
    Get-SPEnterpriseSearchServiceInstance -Identity $hostWFE
    Get-SPEnterpriseSearchServiceInstance -Identity $hostApp
    $ssa = Get-SPEnterpriseSearchServiceApplication
    $newTopology = New-SPEnterpriseSearchTopology -SearchApplication $ssa
    New-SPEnterpriseSearchAdminComponent -SearchTopology $newTopology -SearchServiceInstance $hostApp
    New-SPEnterpriseSearchCrawlComponent -SearchTopology $newTopology -SearchServiceInstance $hostApp
    New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostApp
    New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostApp
    New-SPEnterpriseSearchIndexComponent -SearchTopology $newTopology -SearchServiceInstance $hostApp -IndexPartition 0
    New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostWFE
    Set-SPEnterpriseSearchTopology -Identity $newTopology
    For more information,you can refer to the articles:
    https://technet.microsoft.com/en-us/library/jj862354.aspx
    https://technet.microsoft.com/en-us/library/dn342836(v=office.15).aspx
    Best Regards,
    Eric
    Eric Tao
    TechNet Community Support

  • 2 edge servers and 2 front end servers?

    Good morning/afternoon/evening Technet,
    We're about to go to production with Lync 2013 standard with the following.
    1. 2 front end servers w/ standard edition
    2. 2 edge servers 
    We want to set it up so that 1 front end and 1 edge server will be at a location of ours a couple miles away. We want to setup the other front end and edge server at our main office. For disaster recovery purposes I know that I can keep the two front ends
    pooled but as far as the Edge servers go, would it be best to have 1 active and the other edge turned passive? Is there a way that I can put the two edge servers in the same pool?
    Thanks for all the help guys and gals!
    -Liqsh0t

    Hi,
    Each Site can use a separate Edge Server to support external login process.
    However, it is possible to use single Edge server for both pools. The user from the other site has to connect to the only edge and then route though the WAN link to go to its own pool. Access Edge is responsible for proxying SIP traffic for remote clients
    to the next hop, which can be a Director or a Lync pool.
    Best Regards,
    Eason Huang
    Eason Huang
    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

  • Uninstall Legacy Lync 2010 enterprise and install Lync 2013

    I have a customer who has Lync 2010 enterprise and decided to install Lync 2013 but don't want migration and instead want to uninstall Lync 2010 . I would like to know in this case how to clean the active directory schema from Lync 2010 ? 
    and If there's anything else to consider before uninstalling Lync 2010 ? I will have to disable/remove all currently Lync enabled users but is there anything else?
    I found this article, but would like to know what's the steps in sequence of removing Lync in this case? 
     https://social.technet.microsoft.com/wiki/contents/articles/9849.how-to-remove-lync-server-2010-from-active-directory.aspx
    for example, do I have to first 
    1- Disable LYnc users.
    2- Uninstall Lync server Application from Control panel
    3- Remove Lync from Active Directory? 
    Would appreciate your help. thanks
    thanks
    Mohammed JH

    Hi 
    Check this to Uninstall Lync 2010
    http://terenceluk.blogspot.nl/2011/01/step-by-step-instructions-for.html
    Check this to remove AD References 
    http://blog.ucmadeeasy.com/2010/11/09/lync-server-2010-active-directory-references-and-how-to-remove-them/
    http://digitalbamboo.wordpress.com/2014/01/28/how-to-clean-your-server-of-old-active-directory-lync-ad-references-in-the-rtc-service-when-removing-the-last-2010-pool-fails-to-publish-in-the-lync/
    Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

  • SharePoint Foundation 2013 - Search Configuration Issue - 2 App Servers and 2 Front-End Servers

    Hi, 
    We have a SharePoint Foundation 2013 with SP1 Environment. 
    In that, we have 2 Front-End Servers and 2 App Servers. In the Front-End Servers, the Search Service is stopped and is in Disabled state and in the 2 App Servers in One App Server, Search is Online and in another Search is Starting but goes to Stopped sooon
    after.
    Originally, we had only 1 App Server and we were running our Search Service and Search Service Application in that. Now since the index location became full and we were unable to increase the drive there, we added one more App Server and now the issue is
    Search is not properly getting configured in either of these App servers. What we want to do is run Search only in the new App Server, because we have a lot of storage space for Index locations here, but in the older App Server, not run Search at all.  We
    tried keeping the Search Service disabled and ran the below PowerShell Scripts, but none of the ones are working. These scripts are creating the Search Service Application, but the error of "Admin Component is not Online", "Could not connect
    to the machine hosting SharePoint 2013 admin component" is coming up. 
    http://www.funwithsharepoint.com/provision-search-for-sharepoint-foundation-2013-using-powershell-with-clean-db-names/
    http://blog.falchionconsulting.com/index.php/2013/02/provisioning-search-on-sharepoint-2013-foundation-using-powershell/
    http://blog.ciaops.com/2012/12/search-service-on-foundation-2013.html
    Can I get some help please?
    Karthick S

    Hi Karthick,
    For your issue, could you provide the
    detail error message of ULS log  to determine the exact cause of the error?
    For SharePoint 2013, by default, ULS log is at      
    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS
    For troubleshooting your issue,  you can try to run the SharePoint Products Configuration Wizard on your WFE servers and run the script for configuring the search service on SharePoint
    Foundation:
    [string]$farmAcct = "DOMAIN\service_Account"
    [string]$serviceAppName = "Search Service Application"
    Function WriteLine
    Write-Host -ForegroundColor White "--------------------------------------------------------------"
    Function ActivateAndConfigureSearchService
    Try
    # Based on this script : http://blog.falchionconsulting.com/index.php/2013/02/provisioning-search-on-sharepoint-2013-foundation-using-powershell/
    Write-Host -ForegroundColor White " --> Configure the SharePoint Foundation Search Service -", $env:computername
    Start-SPEnterpriseSearchServiceInstance $env:computername
    Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance $env:computername
    $appPool = Get-SPManagedAccount -Identity $farmAcct
    New-SPServiceApplicationPool -Name SeachApplication_AppPool -Account $appPool -Verbose
    $saAppPool = Get-SPServiceApplicationPool -Identity SeachApplication_AppPool
    $svcPool = $saAppPool
    $adminPool = $saAppPool
    $searchServiceInstance = Get-SPEnterpriseSearchServiceInstance $env:computername
    $searchService = $searchServiceInstance.Service
    $bindings = @("InvokeMethod", "NonPublic", "Instance")
    $types = @([string],
    [Type],
    [Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool],
    [Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool])
    $values = @($serviceAppName,
    [Microsoft.Office.Server.Search.Administration.SearchServiceApplication],
    [Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool]$svcPool,
    [Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool]$adminPool)
    $methodInfo = $searchService.GetType().GetMethod("CreateApplicationWithDefaultTopology", $bindings, $null, $types, $null)
    $searchServiceApp = $methodInfo.Invoke($searchService, $values)
    $searchProxy = New-SPEnterpriseSearchServiceApplicationProxy -Name "$serviceAppName - Proxy" -SearchApplication $searchServiceApp
    $searchServiceApp.Provision()
    catch [system.exception]
    Write-Host -ForegroundColor Yellow " ->> Activate And Configure Search Service caught a system exception"
    Write-Host -ForegroundColor Red "Exception Message:", $_.Exception.ToString()
    finally
    WriteLine
    ActivateAndConfigureSearchService
    Reference:
    https://sharepointpsscripts.codeplex.com/releases/view/112556
    Thanks,
    Eric
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected].
    Eric Tao
    TechNet Community Support

  • How can i configure Distributed cache servers and front-end servers for Streamlined topology in share point 2013??

    my question is regarding SharePoint 2013 Farm topology. if i want go with Streamlined topology and having (2 distribute cache and Rm servers+ 2 front-end servers+ 2 batch-processing servers+ cluster sql server) then how distributed servers will
    be connecting to front end servers? Can i use windows 2012 NLB feature? if i use NLB and then do i need to install NLB to all distributed servers and front-end servers and split-out services? What will be the configuration regarding my scenario.
    Thanks in Advanced!

    For the Distributed Cache servers, you simply make them farm members (like any other SharePoint servers) and turn on the Distributed Cache service (while making sure it is disabled on all other farm members). Then, validate no other services (except for
    the Foundation Web service due to ease of solution management) is enabled on the DC servers and no end user requests or crawl requests are being routed to the DC servers. You do not need/use NLB for DC.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Maybe you are looking for