Hi there,

currently we run a standard lync2010 deployment and I am in the process of migrating to lync2013 (afterwards in place-upgrade to skype is planned). I build up a new pool named lync2013 and successfully migrated all users. But I found out, that it's not possible to rename the pool. The pools name is the same as the servers FQDN and that doesn't fit the naming convention of our company. 

So I migrated all the users back to the old pool, removed the new servers and the (still unused) database, published the pool, renamed the new lync2013-server, build up a new pool with new fqdn and ended up with a control panel of lync2013, that wouldn't accept my credentials anymore (2010 still worked). I couldn't solve this issue then. I wasted one day and this small issue became a major one after restoring snapshots of the lync2013-server - I forgot that the configuration is stored on the "old" server and now I had a non-existing server in my pool. So I also had to restore the lync2010-server. Afterwards I still couldn't log in to the 2013 control panel, but a reboot of all DCs fixed this somehow.

Now everythings back to normal but I still got a new topology with a "wrong" pool name. I am not sure that it is a wise idea to try everything again (my users where not very pleased because they experienced lots of issues including loss of their contact lists, non-working meetings etc) ... so is there a preferred way to go on?

My last idea is to convince the teamleder to use this FQDN for a while and don't do a skype for business in place upgrade but a side by side migration to skype for business with new servers (and decomission the lync2013 pool finally).

Thanks for reading!

Marcel

To remove a existing pool, you have to remove all users, application, etc. from this pool. Than you can remove this pool from the topology. The CMS should be still on the Lync 2010 pool.

Be sure, that the CMS store is on the Lync 2010!

Or you can add the pool with the correct name and delete the wrong pool after installing the new

I removed all users, removed the new front end and edge server from the pool. I didn't used the button "install or update lync", just changed the topology. I renamed the server, build a new topology (ran into several issues with the fileshare and the conferencingdirectory which I had to remove by powershell with force) and ended up with a control panel that won't open.

So is it necessary to remove the pool AND uninstall all roles from the new server?

First Important thing is, that the Lync CMS store is not moved to the new server.

Check which folder are created on the fileshare

Remove the Conference directory for this server

Remove the server from the topology

run bootsrapper.exe /scorch on this server, same on the edge

delete the folder on the fileshare

If it is a enterprise pool remove the SQL databases