Lync 2013 standard server for 3000

Planning to deploy Lync 2013 standard server for 3000 users, IM/presence, Audio/video, persistence chat, monitoring/archive. external access required so 1 edge server in DC and 1 in DR. No enterprise voice. DC and DR are corrected with dark fiber
one lync 2013 standard server in DC and 1 in DR. 1 edge server in DC and 1 Edge server in D R.have couple of queries.
1. can i get HA while doing server pairing in DC and DR?
2. how much time will it take for frontend failover if my frontend server is down in DC.
3. how much time will take for external access failover in DC and DR?
4. are there any potential risks if using standard version instead of enterprise?
Basically client need cost effective solution as lync is not critical for him, does not want to use 3 FE servers in DC and 3 FE in DR to achive HA. want to achieve the solution with standard servers.

1) HA typically refers to automatic failover, so not with Standard edition, but you can get manual failover with this with nearly full functionality.
2) Again, this is manual, but once invoked less than 20 minutes I'd think, possibly faster, only testing invoke-failover will tell you for sure but it won't be too bad.
3) This involves a topology change to change the federation route, possibly next hop for the edge, and possibly media path for a front end pool. That can be completed and replicated in under a minute. You may want to point your external simple
URLs and such (lyncdiscover) at the remaining server, this may be a DNS change to point to a separate reverse proxy. Your _sipfederationtls._tcp SRV record can have a lower matching partner as well, but I typically prefer to keep low TTLs on the external
DNS records so they can be changed quickly.
4) Sure, no automatic failover, your scalability is limited without building out new pools later, no SQL backend that can be mirrored for a bit more resiliency. But again, you can manually failover without issue, you just have to be able to tolerate
a short outage.
Technically, you'd only need 1 FE in the DR site. You have to match Ent/Ent or Std/Std in a pool pair, but the number of servers don't need to match. Still, the HLB and SQL requirements can be costly so I understand this.
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 standard edition server disadvantages

I have 3000 users, client is so cost effective , wanna insisting on Lync 2013 standard edition server. no enterprise voice
Feature required :- IM.presence, A/V conf, persistence chat, external access.
planned servers :- 1 Standard server in DC, 1 in DR. 1 edge server in DC and 1 in DR
1. if i make a pool of standard servers, then will it serve as HA, if yes how much time wil take for failover and what would be the impact on users?
2. If complete DC is down how mch time would take for fail-over and what is the procedure, impact on users?
3. can i collocate persistence chat role on standard edition? any limitation? how backend sizing would be for persistence chat as sql express would be there
4. can i suggest any better solution with standard servers where HA in DC .

For 3000 users Standard Edition will be fine. Use the capacity planner to size out your environment. http://www.microsoft.com/en-us/download/details.aspx?id=36828
1. It won't really serve as HA, as pool pairing is the only option it's more of a DR solution. The RTO for a pool failover is 30mins. So it could take anywhere up to 30mins. http://technet.microsoft.com/en-us/library/jj205079.aspx
2. Same as above. Here is how you failover http://technet.microsoft.com/en-us/library/jj204678.aspx
3. Yes, you can co-locate Persistent Chat on the Front End with Standard Edition. If sized correctly, there should be no performance issues.
4. The only option with Standard is Pool Pairing, so no better suggestions.
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)
This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Do we need License for Lync 2013 Edge server?

Hello Team,
We are currently running Lync 2013 Standard Edition Server. We are planning to enable users for External access and planning to deploly Lync 2013 edge server.
1. Do we need License for Lync 2013 Edge server?
2. Any other client licenses needed?
Please advise.

Hi,
No you don't required any additional License in order to install Lync Edge server. the only license required at OS level i mean windows server licence in terms of Lync concern you don't require any additional License
check this
https://products.office.com/en-us/lync/microsoft-lync-licensing-overview-lync-for-multiple-users
http://lyncuc.blogspot.in/2013/02/lync-2013-licensing-guide-how-to.html
And for client also you don't require any additional license with your existing client license will work for externally as well
Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

Certificate Requirement for Lync 2013 Standard Edition

I have successfully run the setup of lync 2013 standard edition now I am stuck due to certificates required for lync 2013. when I generate a csr. it show the subjected urls for that.
hostname.domain.com
sip.domain.com
diali.domain.com
meet.domain.com
admin.domain.com
lyncdiscover.domain.com
lyncdiscoverinternal.domain.com
im.domain.com (External URL)
so if I go for 3 party CA then I need 8 certicate only for internal lync. As I also need to connected federated partner and external user so I need Edge for again I need 3 more certificates
web.domain.com
a/v.domain.com
sip.domain.com
now when I go for these certificate it quit costly and I didn't understand why such certifcates required. can anyone help me to fix such requirement.
Or, what are the necessary url to which I buy 3 party CA rest leave as it is.
I also want to deploy Edge with single adopter as we have only one network so can anyone assist me to proceed it further.
Talha Faraz Malik

To save on the cost of your third party certificates, I would deploy an internal certificate authority to sign certificates for your internal front end. For your third party certificate, you would only need the SANs for the edge and for your
reverse proxy and as Edwin said, this can be a single cert with multiple SANs.
For example, for your edge you would need:
sip.domain.com
web.domain.com
You would not need A/V as this role does not require a SAN on your certificate. On the same certificate, which you could also use on your reverse proxy, you'd likely want the following FQDNs.
lyncdiscover.domain.com
im.domain.com (your external web services FQDN)
meet.domain.com
dialin.domain.com
You may also want to consider your internal web services FQDN and include the following so third party mobile devices can connect without needing a certificate installed:
im_internal.domain.com (your internal web services FQDN)
lyncdiscoverinternal.domain.com
I'm sure that's not entirely clear yet, so feel free to ask more questions or what the purpose of each is.
When you say Edge with a single adapter, you mean a single adapter in a DMZ or internal? You definably want two NICS, both in separate DMZs, but I've managed to get the edge working with a single adapter in a DMZ before. What you don't want is
the edge in your internal network.
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.

Lync 2013 Edge Server Issues

Forgive me if this question sounds rather "entry level", I have never worked with Lync and this project was handed to me by my boss, who hasn't worked with Lync either.
I have been reading various posts and forum messages until I went cross eyed about setting up Lync 2013 Edge server correctly. I am still running into some questions and issues with the Access, Web, and A/V services starting. Here is my main
question, and below is my setup.
Question:
Is there a need for both an external and internal nic card IF all three external IP's for the external services are programmed at the firewall and router to go directly to 1 internal IP address?
Setup:
Currently I have 1 FE-Standard server that also acts as the Mediation Server, and 1 Edge Server both of which are virtual and running Server 2012. Originally I did have 2 network cards setup, as all other documentation suggested, 1 external and 1 internal.
However my boss, who setup the DNS/Firewall entries stated to remove the External Card since the external address that was setup for the 3 services was routed to 1 internal address. The Access Services, Web Services, and A/V services are all running on three
separate ports with their own unique FQDN- 443, 444, and 445. The cert that was deployed is a wild card cert from GoDaddy, this has been used by other servers that point inside and outside without issues.
Issues and Errors Messages:
I have run into a few different issues and error messages from the Event Viewer:
System
Provider
[ Name]
LS Protocol Stack
EventID
14352
[ Qualifiers]
50153
Level
2
Task
1001
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2013-09-09T15:44:51.000000000Z
EventRecordID
2885
Channel
Lync Server
Computer
edgesvr01
Security
EventData
0xC3E93C0A
SIP_E_STACK_TRANSPORT_FAILED
System
Provider
[ Name]
LS Server
EventID
12303
[ Qualifiers]
50152
Level
2
Task
1000
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2013-09-09T15:44:51.000000000Z
EventRecordID
2884
Channel
Lync Server
Computer
edgesvr01
Security
EventData
80072741
The requested address is not valid in its context.
System
Provider
[ Name]
LS Protocol Stack
EventID
14336
[ Qualifiers]
50153
Level
2
Task
1001
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2013-09-09T15:44:51.000000000Z
EventRecordID
2883
Channel
Lync Server
Computer
edgesvr01
Security
EventData
TLS
external IP address that is now used now
5061
Please help, I am at a loss as to where to go from here.

Thanks for the quick responses.
I have re-enabled the external NIC. All services are running now. When I ran the Remote Connectivity tester this was the outcome.
Testing remote connectivity for user: username@domain... to the Microsoft Lync server.
Specified remote connectivity test(s) to Microsoft Lync server failed. See details below for specific failure reasons.
Test Steps
Attempting to resolve the host name lync.metisconnect.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: xxx.xxx.xxx.xxx (external address)
Testing TCP port 443 on host: host fqdn to ensure it's listening and open.
The port was opened successfully.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server host fqdn on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=*.ourdomain.com, OU=Domain Control Validated, Issuer: SERIALNUMBER=######, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona,
C=US.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
The host name that was found, lync.metisconnect.com, is a wildcard certificate match for common name *.ourdomain.com.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=*.ourdomain.com, OU=Domain Control Validated.
One or more certificate chains were constructed successfully.
Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 7/31/2013 4:02:03 PM, NotAfter = 7/31/2014 4:02:03 PM
Testing remote connectivity for user username@domain to the Microsoft Lync server.
Specified remote connectivity test(s) to Microsoft Lync server failed. See details below for specific failure reasons.
Tell me more about this issue and how to resolve it
Additional Details
Couldn't sign in. Error: Error Message: Operation failed because the network connection was not available..
Error Type: ConnectionFailureException.
External calls from a 3g/4g data connection are not connecting when using the Lync call feature to an internal users Lync Client. Outcome is: Connecting Call and No Audio. Then call ends.

Lync 2013 Standard Edition on Cisco UCS E-Series

Hello,
We have a working Lync 2013 deployment:
- Front-End Enterprise Pool consisting of 3 FE servers
- one Edge Server
- one Back-End server
- one Mediation Server
- one IP PBX gateway, where ITSP's SIP trunks end.
Because we have geographically distributed offices, we are considering deploying of branch offices deployments.
Technet recommends to use SBA for branch offices where there are less than 1000 users. But in case of WAN outage, no conferencing will be available for branch users.
Lync 2013 Standard edition branch deployment would offer all Lync features in case of WAN outage.
In every branch, we consider deploying a Cisco ISR G2 router for terminating branch SIP trunks. This equipment have option to add Cisco UCS E-Series blade that supports CPU with hardware virtualization and supports decent amount of RAM (up to 16GB and up
to 48GB).
Have anyone experience with deploying Lync Standard Edition on this equipment - Cisco UCS E-Series blades? In every branch office there are up to 50 - 500 users that will use Lync.
Thanks,
Andrei Moraru Endava

Hi,
I don’t think you can deploy Lync server 2013 on Cisco UCS E-Series blades.
Here is a link below of “System Requirements for Servers Running Lync Server 2013” may help you:
http://technet.microsoft.com/en-us/library/gg398588.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 Edge Server Deployment

We have already deployed 5 Frontend Server (1 Standard Server and 1 Pool with 4 FE Servers) and one Edge Server some Days ago. Now we are trying to Setup another Lync 2013 Edge Server and get stucked.
When we try to Import the Configuration File, which we had exported from a Frontend Server (export-Csconfiguration..) we get the following error:
Cannot open database "xds" requested by the loging
We can publish the topology on the Frontend Server without Errors.
We have already deinstalled all the lync and SQL componentes and tried again - no success
Best regards
Bueschu
Bueschu

On reviewing the error and confirming the backup service was started, in order to resolve the issue the following actions were performed.
1. In the Lync Topology Builder remove the front end resiliency settings that were previously applied and publish the topology.
2. Connect to each front end server that comprises the pool pairing and run step two of the deployment wizard, by performing this the replicator and backup services will be removed and essentially the pairing will be broken.
3. In the topology Builder re-apply the resiliency settings and publish the topology in order to recreate the pairing.
4. Connect to each front end server that comprises the pool pairing and run step two of the deployment wizard, by performing this the replicator and backup services will be added again. Once the deployment wizard is completed, ensure the
backup services are started on each front end and ensure the Invoke-CSBackupServiceSync PowerShell commands are run as per the "What to do next" information.
5. In the Lync Server Mangement Shell run the "Get-CsBackupServiceStatus -PoolFqdn yourpool.domain.local" and ensure the services is operating in a normal state for both front end servers.
That's it, the deployment wizard and associated xds database access error should now be cleared.
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"

Lync 2013 Standard backup questions

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

That much would get you back up and running, yes. But it may not be a "full" restore.
For example, if you have persistent chat data, it wouldn't necessarily be included in there. If you have an archiving database where all IMs are sent, that information wouldn't be in the PowerShell exports above. If you don't have a copy of the
certificate and private key, that's lost.
Typically, I run my own custom version of Lasse's backup script https://gallery.technet.microsoft.com/Backup-script-for-Lync-2013-aacbb9b9
That pulls all the data, including your file stores, SQL exports, certificates, and everything into a single folder and zips it for you. If you back those zips up, you'll have most everything.
Restoring directly back into SQL isn't the recommended method, if you did need to get back up you'd want to follow standard restore procedures by using the supported PowerShell, but you'll have other avenues to restore if needed and a more complete copy
of your data.
The LIS export may be complete if you don't have any Lync locations defined. You'd typically enter these for 911 purposes.
Check out Lasse's Channel 9 video as well:
http://channel9.msdn.com/Events/TechEd/Europe/2014/OFC-B331
Check out his backup series docs here as well:
http://tech.rundtomrundt.com/search/label/Backup-Lync2013
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Lync 2013 Edge Server

I have a few questions on setting up a Lync 2013 Edge Server. Let me give a little background into what is going on. My comapny currently still has the old Communicator server(1 user left to migrate to Lync!) and a Lync 2013 that is all setup
and functional. Our current Lync environment is only internal, since we do not have a Edge Server setup. That is what I am task to work on now. I have read alot of guides on how to build this server, where it needs to be placed in the DMZ,
and what is needed for it.
First question - Is there a hardware spec needed for this server?
Second question - I read that 3 public ip are needed. What are they needed for? So I can explain to our network guys why I need this.
Third question - Does it matter if the Edge server is on the domain or not? I read it shouldnt be. I dont think it will be an issue either way for me, but its easier to manage if on the domain.
Fourth question - Should I finish my Communicator server decom before worrying about the Edge server?
Final question - is there a guide on how to get rid of the Communicator Server Connections to our Lync Server?
Thanks in advance.

First question - Is there a hardware spec needed for this server?
Second question - I read that 3 public ip are needed. What are they needed for? So I can explain to our network guys why I need this.
Third question - Does it matter if the Edge server is on the domain or not? I read it shouldnt be. I dont think it will be an issue either way for me, but its easier to manage if on the domain.
Fourth question - Should I finish my Communicator server decom before worrying about the Edge server?
Final question - is there a guide on how to get rid of the Communicator Server Connections to our Lync Server?
First question- HW spec https://technet.microsoft.com/en-us/library/gg398835.aspx
For your reference, my edge servers happen to have 40 GB ram and 2x'E5-2690 2.9GHz' ... they don't have to be physical ... can be virtual however.
Second - 3 IP's are recommended ... it makes it easier because you can use standard ports as opposed to straying from 443 etc. ... and it makes troubleshooting easier. All three of the edge services include a 443 requirement - and, with SSL you can't
just share that socket on a single IP - so, lucky service gets 443. Also, you can segregate the traffic and see exactly what is happening. If you only had 1 IP - many scenarios in Lync would not work (e.g., I'm at a hotel and yoru AV port is not
allowed through the firewall).
Here is a wonderful reference - https://blogs.perficient.com/microsoft/2012/12/lync-scaled-consolidated-edge-public-ip-addresses/
Third - it is recommened that it is NOT domain joined - however, it's ok that it is. Mine IS domain joined because I have a domain in my DMZ and it assists with management (etc.) and may be required for yoru security. Your call. IMO, if
you have a domain , join it. Why not?
RE: OCS - there is a migration path from OCS 2007 R2 to Lync 2013 as per https://technet.microsoft.com/en-us/library/gg425764.aspx and several documents on the Internet that show the process for those who need to do so. It's not trivial.
Another interesting link: http://blogs.technet.com/b/saleesh_nv/archive/2014/04/24/lync-2013-tri-co-existance.aspx

Lync 2013 Mobility - Works for Android, not iOS

Here's the situation I am facing right now.
I have installed Lync 2013 for a client and have everything working finally but have hit a roadblock that I just can't seem to overcome.
The environment is this:
1 Lync 2013 Standard Edition Server (Front End)
1 Lync 2013 Persistent Chat Server
1 Lync 2013 Edge Server
1 Reverse Proxy Server
Like I said everything looks like it's working, save one thing. Clients using iPhones can't connect to the service but Android devices can. That's the only thing.
Here is a log snippet from my test device:
POST https://lync.mydomain.org/webticket/webticketservice.svc
Request Id: 0x70b5f68
HttpHeader:Content-Length 1293
HttpHeader:Content-Type text/html
HttpHeader:Date Wed, 18 Dec 2013 17:40:32 GMT
HttpHeader:Server Microsoft-IIS/7.5
HttpHeader:StatusCode 401
HttpHeader:Www-Authenticate Negotiate, NTLM, Basic realm="lync.mydomain.org"
HttpHeader:X-Powered-By ASP.NET
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<title>401 - Unauthorized: Access is denied due to invalid credentials.</title>
<style type="text/css">

</style>
</head>
<body>
<div id="header"><h1>Server Error</h1></div>
<div id="content">
<div class="content-container"><fieldset>
<h2>401 - Unauthorized: Access is denied due to invalid credentials.</h2>
<h3>You do not have permission to view this directory or page using the credentials that you supplied.</h3>
</fieldset></div>
</div>
</body>
</html>
</ReceivedResponse>
Everything looks like it's going good until it gets there and then at the bottom of the log I see this:
2013-12-18 11:40:47.602 Lync[7237:907] is not a valid email address.
This user has no problems signing on to his computer or Lync there. Also, I can sign on to an Android device with his account.
If anyone has an idea on this I welcome it. Please help.

Hi Okrobpr,
Did you solved the issue with the help of Michael provided?
Basically the IOS clients do not support the basic NTLM Authentication method while Windows Phone and Android clients do. So you can check the UseWindowsAuth option is true running the command in Lync Server Management Shell:
Get-CsWebServiceConfiguration
If it shows NTLM you can run the command:
Set-CsWebServiceConfiguration –UseWindowsAuth Negotiate
Get-CsWebServiceConfiguration to make it to be Negotiate.
Please also make sure you have updated to the latest version for Lync Server and clients.
You can check if there are any errors in event viewer of FE server.
Best Regards,
Eason Huang
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 edge server request certificates

I am deploying Lync 2013 edge server, how to get the certificate request file[certificate
signing request (CSR)] on setp 3: Reques,install or Assign Certficates.
i need your help!
Thanks!

Agree with Jason.
On the Certificate Request File page, type the full path and file name to which the request is to be saved.
After you get Certificate Request File, you need to submit this file to your CA (by email or other method supported by your organization for your enterprise CA) and, when you receive the response file, copy the new certificate to this computer so that it
is available for import.
Check how to set up certificates for the internal edge interface at
http://technet.microsoft.com/en-us/library/gg412750.aspx.
Check how to set up certificates for the external edge interface
http://technet.microsoft.com/en-us/library/gg398409.aspx.
Lisa Zheng
TechNet Community Support

Lync 2013 Edge Server Migration

Hi,
Our organisation is in the process of changing gateway providers, so we have to move our currently deployed Lync 2013 Edge Server and TMG (Lync related sites) to the new provider datacentre. We have new public and DMZ IP addresses allocated for these services
and we can't use the current addresses.
Has someone been through this and is there a best practice to follow to transition these services with minimal outages to the users?
Any help would be appreciated.

the steps that you mentioned would work. I need to add some bits in to it,
1. Take a copy of the current Edge Server (VM) and place into the new datacentre
2. changed the IP addressing (of services) for the Edge Pool in the Topology builder and publish/sync
3. Change the IP address of the edge server and run the deployment wizard with "Add remove Lync server component step"
3. Start services
4. Publish the Lync services on the new TMG reverse proxy
5. Test connectivity
http://thamaraw.com

Lync 2013 Edge server compatibility with Lyn 2010 Front end Pool

Hi All,
Technet article (http://technet.microsoft.com/en-us/library/jj688121.aspx) says the following:
If your legacy Lync Server 2010 Edge Server is configured to use the same FQDN for the Access Edge service, Web Conferencing Edge service, and the A/V Edge service, the procedures in this section are not supported. If the
legacy Edge services are configured to use the same FQDN, you must first migrate all your users from Lync Server 2010 to Lync Server 2013, then decommission the Lync Server 2010 Edge Server before enabling federation on the Lync Server 2013 Edge Server.
Can you tell me why it is you have to change the External Lync Web services URL during a migration to Lync 2013 from Lync 2010. What purpose does this serve?
Also can you clarify this and explain why this is required, why would you have to migrate all of your users, would a Lync 2013 Edge not talk to a Lync 2010 front-end?
Any help would be much appreciated. MANY THANKS.

Thank you very much for all your inputs.
We still have few questions:
Questions:
Can you tell me if Lync 2010 users will be able to login using mobility if we repoint the reverse proxy (TMG) web services publishing rule to the Lync 2013 server? Remember both systems Lync 2010 and 2013 are using the same web
services URL so they will both end up at the Lync 2013 server. Alternatively if not we will migrate all users to 2013, this is not a problem
In addition to this I cannot find anything that states how Exchange UM will operate when you are running from a backup pool and the exchange UM contacts are not available because they are homed on the server that is down. This
configuration is 2 x standard edition servers pool paired. How can we make sure Exchange voice mail works during a pool failover?
Call Park is not clear to me I read the following:
Lync Server 2013 provides new disaster recovery mechanisms in the form of failover and failback processes. These failover and failback processes support recovery of Call Park functionality by allowing
users who are homed in the primary pool to leverage the Call Park application of the backup pool when an outage occurs in the primary pool. Support for disaster recovery of the Call Park application is enabled as part of the configuration and deployment of
paired Front End pools.
Is this saying we need to deploy Call Park in the DR pool and use a different range of orbit numbers, or can we use the same range in the DR pool?
Further, I can see that Common Area Phones will be fine as they will log into the DR pool automatically. Response Groups need to be exported and imported to the DR pool. Incidentally these did not migrate well at all and have
caused us a big headache!
Any inputs will be greatly appreciated. Thanks again for all of your time.

Lync 2013 standard server for 3000

Similar Messages

Maybe you are looking for