Lync 2013: Multiple sites topology

Hi,
I have 9 locations worldwide. Currently I have 2 locations (Site A and B) on Lync enterprise (On prem). I have standard edition server in both locations in paired pool configuration for resiliency.
My other locations are on office 365.
I need to add voice to my other locations and hence need to implement on prem installations for them.
I have a single SIP domain for all locations.
My , Edge, RP, Web APP reside in my Site A, site B only has a front End pool.
to introduce additional two sites (Standard Lync) in my other two Site (C and D) and have failover between them, what would my topology look like. Would I be able to have Edge servers for them so that their outside conferencing wont have to traverse through
WAN?
Thanks,

Sure, you could have an edge pool at each additional site and in the topology builder associate it with the local front end pool as the edge pool for media. Federated traffic would still be assigned to a single edge pool for all users, but if users in
site C were having a conference, external attendees over the Internet would receive media traffic from the site C edge.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Similar Messages

Lync 2013 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

Lync 2013 certificate requirements for multiple SIP domains

Hi All,
I am engaged with a client in respect of a Lync 2013 implementation initially as a conferencing platform with a view to enabling EV functions (inc. PSTN conferencing) in the future. They initially need to support 30 SIP domains and eventually
around 100 SIP domains which is proving to be either not possible or severely cost prohibitive. Their current certificate provider, Thawte, can only support up to 25 SANs and have quoted them 5 figures. We tend to use GeoTrust as they are cheaper but they
appear to have a limit of 25 SANs. GoDaddy appear to support up to 100 SANs for a pretty reasonable cost. My questions are as follows:
Is there a way that I’m missing of reducing the number of SANs required on the Edge server?
Use aliases for access edge FQDNs - Supported by desktop client but not by other devices so not really workable
Don’t support XMPP federation therefore removing the need for domain name FQDNs for each SIP domain
Is there a way that I’m missing of reducing the number of SANs required on the Reverse Proxy server?
Friendly URL option 3 from this page:
http://technet.microsoft.com/en-us/library/gg398287.aspx
Client auto-configuration:
i.
Don’t support mobile client auto-configuration in which case no lyncdiscover.sipdomain1.com DNS records or SANs would be required.
ii.
Support mobile client auto-configuration over HTTP only in which case CNAME records are required for each SIP domain (lyncdiscover.sipdomain1.com, etc. pointing to lyncdiscover.designateddomain.com) but no SANs are required.
iii.
Support mobile client auto-configuration over HTTPS in which case DNS records are required for each SIP domain and a SAN entry for each SIP domains is also required. This is because a DNS CNAME to another domain is not supported over
HTTPS.
If the answer to 1 and/or 2 is no, are there certificate providers that support over 100 SANs?
How do certificate requirements differ when using the Lync 2013 hosting pack? I would think that this issue is something that a hosting provider would need to overcome.
Would the Lync 2013 Hosting Pack work for this customer? The customer uses SPLA licensing so I think is eligible to use the hosting pack but not 100% sure it will work in their environment given that client connections are supposed
to all come through the Edge where their tenants will be internal and also given the requirement for an ACP for PSTN conferencing.
Many thanks,

Many thanks for the response.
I was already planning to use option 3 from the below page for simple URLs to cut down on SAN requirement.
http://technet.microsoft.com/en-us/library/gg398287.aspx
What are the security concerns for publishing autodiscover over port 80? I.e. Is this only used for the initial download of the discovery record and then HTTPS is used for authentication? This seems to be the case from the following note on the below page:
http://technet.microsoft.com/en-gb/library/hh690030.aspx
Mobile device clients do not support multiple Secure Sockets Layer (SSL) certificates from different domains. Therefore, CNAME redirection to different domains is not supported over HTTPS. For example, a DNS CNAME record for lyncdiscover.contoso.com that redirects
to an address of director.contoso.net is not supported over HTTPS.
In such a topology, a mobile device client needs to use HTTP for the first request, so that the CNAME redirection is resolved over HTTP. Subsequent requests then use HTTPS. To support this scenario, you need to configure your reverse proxy with a web publishing
rule for port 80 (HTTP).
For details, see "To create a web publishing rule for port 80" in Configuring the Reverse Proxy for Mobility. CNAME redirection to the same domain is supported over HTTPS. In this case, the destination domain's certificate covers the originating
domain.”
I don’t think SRV records for additional SIP domain access edge is a workable solution as this is not supported by some devices.
As per the below article:
http://blog.schertz.name/2012/07/lync-edge-server-best-practices/
“The recommended approach for external client Automatic Sign-In when supporting multiple SIP domains is to include a unique Access Edge FQDN for each domain name in the SAN field. This is no longer a requirement (it was in OCS) as it is possible to
create a DNS Service Locator Record (SRV) for each additional SIP domain yet have them all point back to the same original FQDN for the Access Edge service (e.g. sip.mslync.net).
This approach will trigger a security alert in Windows Lync clients which can be accepted by the user, but some other clients and devices are unable to connect when the Automatic Sign-In process returns a pair of SRV and Host (A) records which do not share
the same domain namespace. Thus it is still best practice to define a unique FQDN for each additional SIP domain and include that hostname in the external Edge certificate’s SAN field”.
===================
1. Basically the requirement is to initially provide Lync conferencing services (minus PSTN conferencing) to internal, external, federated and anonymous participants with a view to providing PSTN conferencing and therefore enterprise voice services later.
2. The customer currently supports close to 100 SMTP domains and wants to align their SIP domains with these existing domains. The structure of their business is such that “XXX IT Services” provide the IT infrastructure for a collection of companies who
fall under the XXX umbrella but are very much run as individual entities.
Question:
Would you agree that I’m going to need a SAN for every SIP domain’s access edge FQDN?
Thanks.

Topology not replicating to Lync 2013 Edge servers

Hello all,
I have installed Lync 2013 with a FE Pool (three servers HW Load Balanced), Director Pool (two servers HW Load Balanced), and an Edge Environment (2 servers, in DMZ, member of a work group, also HW load balanced). All servers are Windows 2012
server (not R2).
I am able to login remotely and have green checks across the board at
https://testconnectivity.microsoft.com. So things are looking good.
My issue is that I am unable to replicate to my Edge servers from the FE. I am not seeing errors in the event viewer, just a big red 'x' on the topology tab in the control panel for the Edge servers. Also, when trying to force replication
the Edge servers continue to show 'False'.
Here are things I have done/checked to resolve this - so I need your assistance please:
1. From the FE, I can visit
https://EdgeFQDN:4443/replicationwebservice - there are no errors, no certificate errors so things look good
2. I have verified that I the Edge servers have the domain suffix added to them. The HW Load balancer is configured as the EdgeInternal.domain.com entry and the physical edge servers are named Edge01 and Edge02 (obviously with the domain suffix added).
So this seems correct based on recommendations.
3. I have added the following reg keys to all Lync Servers in the org
HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL ->DWORD ClientAuthTrustMode Value=2 and SendTrustedIssuerList DWORD Value: 0
I am trying to avoid having to resort to this as possible resolution -
http://ucken.blogspot.com/2012/04/resetting-lync-cms-replication.html, but if this is my next step, please let me know.
May be useless info, but here it is anyway....
One thing I will mention - during my setup, I setup Kerberos Authentication for Lync 2013. I followed
http://howdouc.blogspot.com/2011/07/kerberos-web-authentication-for-lync.html and
http://technet.microsoft.com/en-us/library/gg398976.aspx to configure this.
I am unable to access the RtcReplicaRoot\xds-replica directory on the primary FE server or any other lync server for that matter. I assume this is because it is locked down to the Kerberos account that
was created. However, I am unable to run the command "Set-CsKerberosAccountPassword -FromComputer FEFQDN.Domain.com -ToComputer EdgeFQDN.Domain.com". Obviously
this fails because the Edge servers are in a workgroup and cant see the Kerberos account that was created. Would this break the replication? Just thinking outloud...
Thanks in advance for any input.
Wall

Michael, Thank you for your response. We are currently in coexistence with a Lync 2010 environment.
Our environment consists of a European domain and a North American domain, both in the same forest. The European environment has had 2010 up and running for a couple of years and we (North America) just installed 2013 Lync. The EU domain has
many domain names they support (.uk, .net, .ie, etc.) NAm only manages .com domain name space.
I tell you this because I have configured the NAm environment to support only .com (save $ for SSL UCC licensing) and to provide separate paths to our services. There is a EU site and a NAm site in the Lync topology. The issues are with the FE
servers in NAm.
Based on your response above, the NAm servers are fine with your suggestions in #2 and #3. The CMS database is still on 2010 in the EU site.
Given that the NAm domain is configured to support only .com domain namespace, I am worried that moving the CMS to NAm FE's as it would break EU's ability for federation.
Any guidance or expertise is greatly appreciated.
My ultimate goal is to have NAm employees authenticate to their Edge servers in the site and EU to authenticate to their respective Edge Servers. Also, I have read that we can only have one Edge pool responsible for Federation in the Lync org.
I assume that we will have to keep federation going through EU as they have the SSL certs for all domains configured in their environment. Just a little confused before I make any changes.
Wall

Lync 2013 Topology Publication Failed!

Scenario
Lync Enterprise Edition!
Windows Server 2012R2 - LyncServer 2013
WIndows Server 2008R2 - Sql 2008 R2 Failover Cluster (Multiple Database and Instances Created) 5 Others Application Database also
Created which has been used.
DNS Entries
HOst Name :
LYNCFE.consoto.com
Pool.consoto.com (Host Name Created Same IP as Lync Frontend Server)
dialin.consoto.com
meet.consoto.com
admin.consoto.com
DBLYNC.consoto.com
Virtual Instant Name of Sql Database and Instance name : DBLYNC\Lynccore
Permission Rights:
I am using the Administrator account for Lync 2013 Installation.
Domain Administrator Account Member to CSAdministrator group and RTC Universal Server admin group.
SQL sysadmin Account member Sqladmin and Domain administrator User.
ShareFolder-Lyncshare on Storage.consoto.com
Permission:
Everyone
Read-write
RTCComponentUniversalServices Read-write
RTCHSUniversalServices Read-write
RTCUniversalServerAdmins Read-write
RTCUniversalConfigReplicator Read-write
Virtual Computer Name DBLYNC$
Full control
Issue : I have create one topology and try to publish but getting error.Log Detail Below
Feature: CentralMgmtStore
SQL Instance: domain-name.com\lynccore
Collocated: False
Found "RTCUniversalServerAdmins": True
Found "RTCUniversalConfigReplicator": True
Found "RTCUniversalReadOnlyAdmins": True
TaskFailed: Task execution failed.
Error:The network name cannot be found.
▼ Details
└ Type: IOException
└ ▼ Stack Trace
└ at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)
at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)
at Microsoft.Rtc.Common.Data.DatabaseManager.CreateDatabase(String dbFileBase, String dbPath, String logPath, Int32 dbSizeMB, Int32 logSizeMB, Int32 dbGrowthMB, Int32 logGrowthMB, Int32 maxDbSizeMB, Int32 maxLogSizeMB)
at Microsoft.Rtc.Common.Data.DatabaseManager.CleanInstallDatabase(String dbFileBase, String initialScripfilePath, String
dbPath, String logPath, Int32 dbSizeMB, Int32 logSizeMB, Int32 dbGrowthMB, Int32 logGrowthMB, Int32 maxDbSizeMB, Int32 maxLogSizeMB)
at Microsoft.Rtc.Common.Data.DbSetupBase.CleanInstallDatabase()
at Microsoft.Rtc.Common.Data.DbSetupBase.CreateOrUpdateDatabase()
at Microsoft.Rtc.Common.Data.XdsDatabase.CreateOrUpdateDatabase()
at Microsoft.Rtc.Management.Deployment.Tasks.DatabaseCreator.CreateDatabaseForFeature(String featureName, Boolean clean, Boolean update, String sqlServer, String instanceName, Boolean collocated, Boolean backup, Boolean noreindex,DatabasePathAssignment[]
pathAssignments, Boolean broadCast, String& logfile)
at Microsoft.Rtc.Management.Deployment.installdatabaseCmdlet.CreateDatabaseForFeature(Planitem i)
at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog[T](Action`1 action,T arg)
TaskFailed: An error occurred while creating or updating the database for feature CentralMgmtStore. For details, see the log
file ‘C:\Users\Administrator\AppData\Local\Temp\2\Create-CentralMgmtStore-domain-name.com_lynccore-[2014_07_09]
[11_40_46].log’
TaskFailedResolution: Consult exception information and previous errors for more information on how to resolve this error.
Error: An error occurred: "System.IO.FileNotFoundException" "The network name cannot be found"

SQL Scenario
Windows Server 2008R2 - Sql 2008 R2 Failover Cluster (Multiple Database and Instances Created) 5 Others
Application Database also Created on the Failover Cluster.
Failover SQL Cluster
Active Passive
Computer Name: Cluster1.Consoto.com
Computer Name : Cluster2.Consoto.com
ping cluster1.consoto.com reply IP 192.168.0.30 from Lync FE ping
cluster2.consoto.com reply IP 192.168.0.31 from Lync FE
SQL Database DBLYNC IP is 192.168.0.40 and also reply from Lync Server

Lync 2013 Publish Topology Failed in window server 2012R2

Scenario
Lync Enterprise Edition!
Windows Server 2012R2 - LyncServer 2013
WIndows Server 2008R2 - Sql 2008 R2 Failover Cluster (Multiple Database and Instances Created) 5 Others Application Database also Created which has been used.
DNS Entries
HOst Name :
LYNCFE.consoto.com
Pool.consoto.com (Host Name Created Same IP as Lync Frontend Server)
dialin.consoto.com
meet.consoto.com
admin.consoto.com
DBLYNC.consoto.com
Virtual Instant Name of Sql Database and Instance name : DBLYNC\Lynccore
Permission Rights:
I am using the Administrator account for Lync 2013 Installation.
Domain Administrator Account Member to CSAdministrator group and RTC Universal Server admin group.
SQL sysadmin Account member Sqladmin and Domain administrator User.
ShareFolder-Lyncshare on Storage.consoto.com
Permission:
Everyone Read-write
RTCComponentUniversalServices Read-write
RTCHSUniversalServices Read-write
RTCUniversalServerAdmins Read-write
RTCUniversalConfigReplicator Read-write
Virtual Computer Name DBLYNC$ Full control
Issue : I have create one topology and try to publish but getting error.Log Detail Below
Feature: CentralMgmtStore
SQL Instance: domain-name.com\lynccore
Collocated: False
Found "RTCUniversalServerAdmins": True
Found "RTCUniversalConfigReplicator": True
Found "RTCUniversalReadOnlyAdmins": True
TaskFailed: Task execution failed.
Error:The network name cannot be found.
▼ Details
└ Type: IOException
└ ▼ Stack Trace
└ at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)
at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)
at Microsoft.Rtc.Common.Data.DatabaseManager.CreateDatabase(String dbFileBase, String dbPath, String logPath, Int32 dbSizeMB,
Int32 logSizeMB, Int32 dbGrowthMB, Int32 logGrowthMB, Int32 maxDbSizeMB, Int32 maxLogSizeMB)
at Microsoft.Rtc.Common.Data.DatabaseManager.CleanInstallDatabase(String dbFileBase, String initialScripfilePath, String
dbPath, String logPath, Int32 dbSizeMB, Int32 logSizeMB, Int32 dbGrowthMB, Int32 logGrowthMB, Int32 maxDbSizeMB, Int32
maxLogSizeMB)
at Microsoft.Rtc.Common.Data.DbSetupBase.CleanInstallDatabase()
at Microsoft.Rtc.Common.Data.DbSetupBase.CreateOrUpdateDatabase()
at Microsoft.Rtc.Common.Data.XdsDatabase.CreateOrUpdateDatabase()
at Microsoft.Rtc.Management.Deployment.Tasks.DatabaseCreator.CreateDatabaseForFeature(String featureName, Boolean clean,
Boolean update, String sqlServer, String instanceName, Boolean collocated, Boolean backup, Boolean noreindex,
DatabasePathAssignment[] pathAssignments, Boolean broadCast, String& logfile)
at Microsoft.Rtc.Management.Deployment.installdatabaseCmdlet.CreateDatabaseForFeature(Planitem i)
at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog[T](Action`1 action,T arg)
TaskFailed: An error occurred while creating or updating the database for feature CentralMgmtStore. For details, see the log
file ‘C:\Users\Administrator\AppData\Local\Temp\2\Create-CentralMgmtStore-domain-name.com_lynccore-[2014_07_09]
[11_40_46].log’
TaskFailedResolution: Consult exception information and previous errors for more information on how to resolve this error.
Error: An error occurred: "System.IO.FileNotFoundException" "The network name cannot be found"


SQL Scenario
Windows Server 2008R2 - Sql 2008 R2 Failover Cluster (Multiple Database and Instances Created) 5 Others Application Database
also Created on the Failover Cluster.
Failover SQL Cluster
Active
Passive
Computer Name: Cluster1.Consoto.com
Computer Name : Cluster2.Consoto.com
ping cluster1.consoto.com reply IP 192.168.0.30 from Lync FE
ping cluster2.consoto.com reply IP 192.168.0.31 from Lync FE
SQL Database DBLYNC IP is 192.168.0.40 and also reply from Lync Server

Lync 2013 Mobility not working in MultiSite Topology

Dear All,
I have Lync 2013 Server running in my environment. Below are the details,
1) We have one Lync FrontEnd server as well as one Lync Edge Server installed in Egypt Site & one Lync FrontEnd server as well as one Lync Edge Server installed in Dubai Site in a Single domain.
Users who are in Egypt site pool are able to login through Lync Mobility but unfortunately users in Dubai Site pool are unable to login through Lync mobility.
External webservices are published on both Sites. Furthermore Dubai Site Pool users are able to login through Lync Client from external but they are unable to login through Lync Mobille Client.
Anyone help would be highly appreciated.
Thanks & Regards,
ZB

Is lws.abc.com external web url for Egypt site?
How about lyncaepool.abc.com and communication.abc.com?
I would like to confirm if you pasted two URLs in IE directly. Here are some tips for troubleshooting the issue.
For multiple pools, the Autodiscover traffic can be routed to a single Front End pool as long as both pools have their external Web services published. Once a client connects to the Autodiscover service it will be returned the external web service FQDN for
either pool, depending on which pool the user account belongs to.
Thus, you must have external Lyncdiscover record pointed to Egypt site. Once Dubai external user connects to Egypt Autodiscover service, it will be returned the external web service for Dubai Site Pool and user connects to Dubai Site Autodiscover service(https://<Dubai
ExtPoolFQDN>/Autodiscover/autodiscoverservice.svc/Root) and UCWA. We can check if mobile client is able to resolve Autodiscover service URL of Dubai Site by typing the URL into manual configuration of Lync mobile client.
Here is a great blog about Lync mobility Autodiscover process.
http://blogs.technet.com/b/nexthop/archive/2012/04/25/lync-server-2010-mobility-deep-dive-autodiscover-service.aspx
If the issue persists, please paste the result of Lync Connectivity Analyzer for further troubleshooting.
Kent Huang
TechNet Community Support

Can I add a two way trusted but in different forest domain to My existing Lync 2013 Topology !

HI !
We have an installed Lync 2013 Std Edt. setup and its working perfectly for one domain. Our network infrastructure ( LAN ) is being shared with our sister company. They have their own forest and domain and a two ways trust relationship with our domain. I
want to add them in our Lync 2013 topology, is it possible ?? if yes, thn what are the requirements and which changes i need to consider.
Response from experts would be greatly appreciated.

Yes, You must establish a two-way trust between the central forest and user forests to enable distribution group expansion when groups from user forests are synchronized as contacts to the central forest.
Also you can refer below link
http://technet.microsoft.com/en-us/library/gg670909%28v=ocs.14%29.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"
Mai Ali | My blog: Technical

Unable to share files when in a IM convo with multiple people Lync 2013

Hello,
I'm in the middle of a migration from lync server 2010 to lync server 2013. The users I have migrated over to lync 2013 are not able to send/share attachments when in a convo with multiple people.
However, users can send/share files when IM'ing with individual people.
I've been researching this issue for quite some time but still having a problem pinpointing the issue.
Any help would be greatly appreciated.
Thanks.

Hi,
Did the issue also happen between users who still in Lync server 2010 pool?
Did the issue happen internal or external?
Please double check if MCU on Lync 2013 FE server works well, when two participants are connected, the session is essentially peer-to-peer. When three or more participants are connected, the Sharing feature depends on the Front End Server Multi Point Control
Unit (MCU) to provide the sharing stream to all parties.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

How to add multiple skype users in Lync 2013?

Dear Expert,
I already add skype user but I can only add one by one. How do I add multiple skype users in Lync 2013
Thank you

Hi,
As I konw, there is no native method to add multiple Skype users to Lync 2013 so far.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Understanding Lync 2013 Deployment for Single forest multiple domain Infrastructure

Hello Everyone,
I have an issue in understanding a deployment scenario of Lync 2013 Enterprise edition.
We have a single forest multiple domain infra.
My My question here is, while AD prep, do we need to run Domainprep on every domain in the forest.
Thanks!
Thank You!!! BR, Ammi.

Hi Ammi,
To prepare Active Directory Domain Services for your Lync Server 2013 deployment, you must perform three steps in a specific sequence.
1.
Preparing the Active Directory schema in Lync Server 2013
Extends the Active Directory schema by adding new classes and attributes that are used by Lync Server.
Run once for each forest in your deployment where Lync Server will be deployed.
2. Preparing the forest for Lync Server 2013
Creates global settings and universal groups that are used by Lync Server.
Run once for each forest in your deployment where Lync Server will be deployed.
3. Preparing domains for Lync Server 2013
Adds permissions on objects to be used by members of universal groups.
Run once per user domain or server domain.
Hope it can be helpful.
Best regards,
Eric

Multiple Accounts With Same Display Name Lync 2013

Hi All,
I have a single user in my Lync 2013 environment that sees three different users with the same exact display name. All three users have a different SIP address.
User1 - Melissa A. - [email protected]
User2 - Melissa A. - [email protected]
User3 - Melissa A. - [email protected]
Upon looking at the contact card, each user has the same display name but correct email address. However there is another email address line that appears underneath the original Send Email address line - on other computer's this appears as "IM".
The user is running a Windows Server 2012 Standard on a Hyper-V Virtual Machine. I've tried re-installing the Office 2013 suite as well as forcing an Global Address Book update from his local machine. All data is correct in Lync Server and Active Directory.
Can someone please advise? Could it be a corrupt database?
Thanks in advance,
Adrian

Hi Adrian,
You could try deleting the following data for the user.
1. User profile:
%userprofile%\AppData\Local\Microsoft\Office\15.0\Lync\[email protected]
2. Registry Key:
HKCU\Software\Microsoft\Office\15.0\Lync\[email protected]
3. Outlook Contact
Delete the related Contact Cards in Outlook
Hope it can be helpful.
Best regards,
Eric

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.

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

Multiple sites, multiple Edge servers

How do I configure multiple Edge servers? I am working with a client that has offices in US, Europe, and Asia. There are three sites configured. Each site has it's own internet and voice provider.
Right now they use one Edge server that is located in US. How do I add more Edge servers? Should I use different names for sip.domain.com records?
Any way to configure that if US user in Europe, this user will automatically use Edge server that is located in Europe? Same for Asia.
Can someone help me find documentation and/or explain how to configure it?
Thank you.
Thank you. Eric.

Eric,
Obviously when you get into global Lync deployments things get a bit more complicated. So there are a few things you can do to mitigate issues/failover/etc. So to the questions at hand.
The Lync 2013 Client utilizes the Lync Discover service as the default login method. So as I described in the above post, when the Lync 2013 Client logs in, it will resolve lyncdiscoverinternal.domain.com and lyncdiscover.domain.com before it goes
to the SRV records like OCS/2010 Clients did. The Lync Discover service is a web service that would be published via the reverse proxy. In terms of your example, yes, the first time a user connects to the Lync Server they would connect to where
ever lyncdiscover.domain.com is published. So let's say it's in the US. The client will pass XML files back and forth and go to the edge server defined for the EU Site. The next time the user logs in remotely, they will not go back to the lyncdiscover.domain.com
as the client will cache the location it's supposed to connect in the configuration.cache file. So yes, it would go to the US but only the first attempt (or if it's server was down).
As for the second question. You could utilize a global DNS solution so users in EU get directed to a Reverse Proxy in EU where lyncdiscover.domain.com is published. US folks would go to US, etc. etc.
Thanks,
Richard
Richard Brynteson, Lync MVP | http://masteringlync.com | http://lyncvalidator.com

Lync 2013: Multiple sites topology

Similar Messages

Maybe you are looking for