LyncServer 2013 replace edge server

Question

Hi!

I have LyncServer 2013 deployment and I'm tasked with replacing the edge server (for OS upgrade requirement).
The deployment consists of one FE pool and the edge single server pool.
The problem is I can't add the new edge server to singleserver pool to remove then the old server from there.
So the question is about the best strategy for replacing server with minimum effort and minimum downtime.
I think of 4 scenarios:

1. Create new single-server edge pool, add there new server, make new settings for edge (new service fqdns, public ip addresses, dns records, firewall rules, ...) and after that make FE pool the next hop for it (the most clean but the heaviest plan).
2. Same as 1 but with multi-server edge pool containing single server (same difficulties but with easier extending/change pool member in future. Not sure though is it possible to have working multiserver pool with single server in it).
3. Somehow convert sigleserver edge pool to multiserver and add new server there, inheriting pool settings and resources (the easiest plan, but is it possible?)
4. Create new multiserver edge pool with current edge parameters and add to it the existing edge server. If everyting's ok add new server to pool and remove the old one.

Is 3 or 4 feasible?

Thanks

Answer 1

Hi @Roman Annenko ,

Still doubt about multiserver pool with single server in it - will it work or not?

It will work normally. The following picture outlined proved it:

There is no official document to prove it, but it seems work in theory.

In my experience, edge server are pretty easy to remove /add. If you first edge server is added and the pool name matches the FQDN of that edge then, you will need to remove it from the topology and re-add it. When you re-add it, you will need to install the edge again as if you are doing a normal install.

Export config out of FE - Export-CsConfiguration -FileName C:\edge.zip

Copy this file to the edge server and then run Install-CsDatabase -LocalDatabases -Clean

Then Import-CsConfiguration -Filename C:\edge.zip -LocalStore

Then run stage 2 of the deployment wizard or run deploy.exe from the SfB deployment tools in c:\program files\skype for business\deployment

Then because the internal pool name would have changed, you need to request and assign a new internal Edge certificate from your internal CA so the CN and SAN match the pool FQDN.

Add second edge to the pool - make sure the settings are compatible with what you are doing e.g. same FQDNs for Access Edge, Web Conf, AV as the first edge server.

---

If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.