Happy new year all! I will start the year off with the shortest blog ever. You don’t! Ok please keep those cards and letters coming!
As tempted as I am to just leave that as its own punch line, I have that responsibility to write this down for my future old self, who will not recall why I don’t want to delete the Skype for Business Pool and recreate it.
So to put this as mildly as possible, There is generally only one direction with Pools, and that is forward. You may change a pool by introducing another pool, and then moving your desired attributes out of the old pool and into the new pool. There may be various ways to do it in fact. But my experience is the only time you care about a pool name is when you named the pool with a hostname instead of an FQDN. In addition, this is at the beginning of your deployment.
I have learned enough in life to say that if you don’t feel 100% comfortable in the beginning of your Deployment, when are you ever going to be?
So in all my reading I could never pin down Microsoft as saying anything other then the following:
- 1. You cannot rename the Pool
- You have to remove lync and or Move the SFB CMS store.
- Verbal and written word from MS is a consensus that you don’t want to rename the pool.
SO most articles discuss the scorched earth policy and command, enough to just make you want to leave it all alone:
I came up with the commands I use to get back to my install with the least about of trouble. I cant speak for the MS support for this, but I think this is as relevant as any of the other articles you may run into on the subject. Below you will find two steps, and then you can get back to your Deployment.
- 1. Run the SFB command Remove-CsConfigurationStoreLocation
- 2. Remove the RTC service (all inside too) from the ADSIEDIT.MSC configuration partition.
- 3. Start with checking the SFB configuration Wizard to make sure you get your AD schema, Forest and Domain Prepped. It will say partial now.
- 4. Next Create a Clean Topology TBXml and publish it.
- 5. Finally, go back to the Config wizard and Install your Config and the rest of the deployment is yours !
- 6. In a rare circumstance, you may have to go in and correct the name of the file share in the topology, and re-publish the Topology. This should be the only sorts of issues you would find. Otherwise. don’t look for any Drama. Just move on.
Mind you, you really did wipe your environment but it did seem painless didn’t it? Be aware of the SFB users and other items that will also be blown away by the choices.
Have a Great 2017!