Correctly decommission an SFB EE pool and site RRS feed

  • Question

  • Hi -

    We are migrating all users out of our APAC site and pool and into our EMEA site and pool.  We've tested individual moves with the -moveconferencedata switch, and things look good (users retain their original meeting URL and conference ID).  We'll pipe a get-csuser with filter into move-csuser with -moveconferencedata this weekend to migrate all users at once.

    My question revolves around proper retirement of the then empty APAC pool.  I know how to break down all of the pieces and parts, such as UMIPGateways, trunks, shared components, etc.  But what about the existing ConferenceDirectory that is bound to the then empty pool?  Will I need to use the move-csconferencedirectory command to lift that existing directory and move it to our EMEA pool as well?

    Thanks in advance.

    Wednesday, June 22, 2016 11:20 AM

All replies

  • Hi Jay, 

    Conference Directory move is very much required as you might encounter trouble when decommissioning the Pool. Did you also move the Dial in conferencing Numbers ( Application Endpoints as well)  if you have hosted Dial in Conference in your organization. You can check the directories exist there in the pool with Get-CsConferenceDirectory,if its there then we need to move them 



    Linus || Please mark posts as answers/helpful if it answers your question.

    Wednesday, June 22, 2016 11:44 AM
  • We do have dial-in, and were planning to migrate conf numbers and other application endpoints right after the user migration.

    Thanks on the confdirectory info.  Will make sure to migrate that as well.

    If anyone else has any input, feel free to comment.  I will most likely mark this response as 'answer' after a couple of days.  Thanks Linus -

    Wednesday, June 22, 2016 11:53 AM
  • Hi,

    Did configure your simple URLs to global scope, or different simple URLs for each central site in your organization?

    If both a global scope simple URL and a site scope simple URL are specified, the site scope simple URL has precedence. Then after users move to the new pool, the scheduled SFB meeting will still be valid.

    If you choose to use site scoped simple URLs, your users won't be able to move between Front-End pools in different sites without those users rescheduling all of their scheduled meetings as the meeting simple URLs are different between sites.  This includes fail-over scenarios where pools in backup relationships are in separate sites.  When you need to fail-over between sites where site scoped simple URLs are deployed, users won't be able to join their meetings because of the scope for URL.

    Best Regards

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Eason Huang
    TechNet Community Support

    Thursday, June 23, 2016 9:13 AM
  • Hi -

    simple URL for all of our sites is the same, globally scoped.  Thanks for your reply.

    Thursday, June 23, 2016 9:35 AM