asked on

Deploying Lync 2010 Survivable branch server

I would like to deploy a Lync SBS at customer's branch premise and this would be my first time with Survivable branch server so I would like to know the detailed steps and required hardware and software for this process.

in one of Microsoft KB, there's an article explains the installation process but it's not telling you if you will have to deploy a new DC ? EDG or front end server for this.

http://technet.microsoft.com/en-us/library/gg398849

How would the branch be connected to the central site? and what kind of hostname for the Lync SBS have to be? is it identical as the central one ?

Jeff_Schertz

The SBS is a separate server role that stands alone, so you must supply a unique name for it. It is basically a stripped-down Front End server with only the registrar and proxy components, and no web services, conferencing services, etc.

The branch office needs to be connected back to the central sites and have connectivity to the rest of the environment during normal operation. It is up to you what additional services you deploy in the BO (e.g. AD Domain Controller, local DHCP server, etc) as it depends on what level of redundancy you need to plan for during a WAN outage.

I suggest you read through this series of articles as the SBA operation is identical to the SBS:
http://www.shudnow.net/2012/05/02/lync-2010-central-site-resilience-backup-registrars-failovers-and-failbacks-part-1/

Mohammed Hamada

ASKER

Jeff,

Where do I find the Proxy components ? and with which do I start the installation (Proxy components or Lync server role) ?

Thanks a lot

Jeff_Schertz

You don't deploy any of the components separately, simple follow the SBA/SBS deployment steps in the product documentation:
http://technet.microsoft.com/en-us/library/gg398849

Mohammed Hamada

ASKER

I'm following the link now but when adding the branch site FQDN to the Lync FE topology! what would this FQDN be like? Since the SBS server will not be domain joined !

and if the SBS server doesn't need to be domain Joined, why in the link it states the following "An installation technician at the branch site must be added to the RTCUniversalSBATechnicians group."

Or does this apply to SBA only ?

Mohammed Hamada

ASKER

OK i think i got it but could you please confirm this ? I have to configure the hosts file in the SBS server just like the Edge in order to get access ?

Jeff_Schertz

Normally you wouldn't use a HOSTS file on an Edge Server or an SBS role. You should be leveraging a DNS server for name resolution for both of these services.

The SBA/SBS should be a member of the same Active Directory domain as the rest of your internal Lync servers, only the Edge Server is not domain-joined.

The host FQDN would be in the same format as any of Lync or Windows server in your domain (e.g. sba1.corp.domain.local)

Mohammed Hamada

ASKER

When two locations are on different geo-locations ? How would you join Lync SBS on branch site to AD on central site over WAN ?

Should the Branch be connected to Central site using VPN ? Or is there another method of achieving this ?

Thanks

ASKER CERTIFIED SOLUTION

Jeff_Schertz

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Mohammed Hamada

ASKER

Jeff, Thanks to you I think i'm making a great process. I have joined the Server using VPN and now I'm adding the SBS FQDN to the Lync FE topology. but when reaching to the part where I have to define the PSTN Gateway I read in the MS Documentation as it says "Microsoft Lync Server 2010 communications software must be set up at the central site.
Mediation Server must be deployed at the central site"

I have collocated Mediation Service on Lync FE! Would that be ok ? and what's communications software? my setup is Lync Standard server.

Mohammed Hamada

ASKER

Jeff,

After running the topology on the Lync SBS, I tried to publish it but was getting this error:

The existing topology identifies CentralLyncFE\rtc as the central management store, but the topology that you are trying to publish identifies LyncSBS\rtc as the central management store. The central management stores must match before the topology can be published.

I ran the cmdlet "Get-CsConfigurationStoreLocation" and found it pointing to my central LyncFE. which I think has got it from the AD after I joined the SBS to my central AD.

I then ran the cmdlet "Remove-CsConfigurationStoreLocation" and tried to publish the topology. Topology was published but wasn't enabled and I received this error.

Create Pool: lyncsbs.mydomain.com 1:1 9/3/2012 4:11:31 AM

Error: Multiple pool objects found in Active Directory with the name 1:1 or FQDN lyncsbs.mydomain.com. Ensure your deployment does not use conflicting pool information, and clean up any stale entries from deactivated pools to continue.
¿ Details
9/3/2012 4:11:32 AM
Error
+ Error: An error occurred: "Microsoft.Rtc.Management.Deployment.ActiveDirectoryException" "Multiple pool objects found in Active Directory with the name 1:1 or FQDN lyncsbs.mydomain.com. Ensure your deployment does not use conflicting pool information, and clean up any stale entries from deactivated pools to continue."

Could you please let me know how to solve this ? Thanks

Mohammed Hamada

ASKER

Thanks a lot Jeff, I wasn't well informed of the SBS concept as a term but now I know what it does and how it's deployed.