locked
Cannot publish new topology RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    The error message: "System.InvalidOperationException" "Cannot publish topology changes. Users or contacts are still homed on a pool that would be deleted. Move or remove the users or contacts before continuing."

     

    Most -- but not all objects -- were moved from Lync 2010 to Lync 2013. The old Lync 2010 server has been decommissioned and is no longer available. I've run the script: FindObjectsInThePool.ps1 Lync-2010.domain.com and can see all those objects in the Lync 2010 pool. For the link to the script, see below.

     

    Is there a way to delete those objects, so we can publish the new topology?

     

    Users or contacts are still homed on a pool that would be deleted

    https://gallery.technet.microsoft.com/Users-or-contacts-are-0d89422b#content

    MCTS: Messaging | MCSE: S+M

    Friday, February 12, 2016 11:08 AM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi

    If you run Get-CsUser -Filter {registrarpool -eq "<lync2010>"} 

    Where Lync 2010 will probably have a registrar pool of a series of numbers as it will be orphaned.

    Then once found your can pipe them in a move request

    Get-CsUser -Filter {registrarpool -eq "<lync2010>"} | Move-CsUser -Target lync2013.domain.com -Force

    This will force all the orphaned users to be moved to the new pool.

    You should then be able to publish the topology.

    thanks

    Note: Please remember to `Mark as Answered` a post that answers your question and/or `Vote as Helpful` posts that have helped you. This will help others find answers to similar problems. For more Skype for Business help visit: http://www.skype4b.uk Please note that answers are based on my experience and opinion only and do not necessarily represent the views of my employer.

    Sunday, February 14, 2016 9:15 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    You can use this script, to find Lync/S4B Orphaned Objects of one pool

    https://gallery.technet.microsoft.com/office/LyncS4B-Orphaned-Objects-03beadd7

    regards Holger Technical Specialist UC

    Sunday, February 14, 2016 11:48 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks a lot for your answers. I used the combination of Get-CsUser –Identity <object>, Disable-CsUser –Identity <object>, just to make sure. I know Exchange quite well, but not Lync, so I was perhaps a bit too careful.

     

    It turned out two more command were needed:

    Get-CsConferenceDirectory

    Which returns all conference directories. Then the one that has to be deleted. 

     Remove-CsConferenceDirectory -Identity 3 -force

    MCTS: Messaging | MCSE: S+M

    Monday, February 15, 2016 8:30 AM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi

    If you run Get-CsUser -Filter {registrarpool -eq "<lync2010>"} 

    Where Lync 2010 will probably have a registrar pool of a series of numbers as it will be orphaned.

    Then once found your can pipe them in a move request

    Get-CsUser -Filter {registrarpool -eq "<lync2010>"} | Move-CsUser -Target lync2013.domain.com -Force

    This will force all the orphaned users to be moved to the new pool.

    You should then be able to publish the topology.

    thanks

    Note: Please remember to `Mark as Answered` a post that answers your question and/or `Vote as Helpful` posts that have helped you. This will help others find answers to similar problems. For more Skype for Business help visit: http://www.skype4b.uk Please note that answers are based on my experience and opinion only and do not necessarily represent the views of my employer.

    Sunday, February 14, 2016 9:15 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    You can use this script, to find Lync/S4B Orphaned Objects of one pool

    https://gallery.technet.microsoft.com/office/LyncS4B-Orphaned-Objects-03beadd7

    regards Holger Technical Specialist UC

    Sunday, February 14, 2016 11:48 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks a lot for your answers. I used the combination of Get-CsUser –Identity <object>, Disable-CsUser –Identity <object>, just to make sure. I know Exchange quite well, but not Lync, so I was perhaps a bit too careful.

     

    It turned out two more command were needed:

    Get-CsConferenceDirectory

    Which returns all conference directories. Then the one that has to be deleted. 

     Remove-CsConferenceDirectory -Identity 3 -force

    MCTS: Messaging | MCSE: S+M

    Monday, February 15, 2016 8:30 AM