“Psst! Avast there! It be too late to alter course, mateys…and there be plundering pirates lurking in every cove, waitin’ to board. Sit closer together, and keep your ruddy hands inboard. That be the best way to repel boarders. And mark well me words, mateys…dead men tell no tales! Ye come seekin’ adventure and salty ol’ pirates, eh? Sure ye come to the proper place. But keep a weather eye open, mates, and hold on tight, with both hands if you please…there be squalls ahead, and Davy Jones waiting for them what don’t obey.”
When you begin, the first steps of your migration from Lync 2010 to Lync 2013 , you should find it well documented and the experience is not one of exasperation. However, I want you to know of a generally undocumented warning. The warning is documented, but the caveat of user objects that may be missed is not. I compare important message below to the Talking skull at the Pirates of the Caribbean. When you Open the Lync 2013 Control panel, you will see this note in the User section:
As it turns out, there is some ambiguity in terms of the final steps of your migration. Think going over the waterfall in Pirates, at the bottom you see the dead mans bones. We don’t want that for anyone. Lest I digress. You are done, you have removed all objects from 2010 , (that are documented) and you try to remove your 2010 pool in Topology builder. If you find It fails because of an error such as: Users or contacts are still homed on a pool that would be deleted. More or remove the users or contacts before continuing
Here is what you need to know:
1. Disabled objects (users) contacts from 2010 may not show up in power shell command (get-csuser), if you run them from Lync 2013
2. You would have to open power shell from Lync 2010 to find a disabled user. that may also not show the user.
3. Tying back to the search term results warning above, I would venture to say there is a grey area where a user was in OCS, migrated to 2010, and then gets disabled. Maybe the objects in AD are correct. Maybe they or not. but regardless, we actually found the disabled Lync user did not come up on radar with any power shell command we ran.
4. The long story short is you really want to scrub you users, to the point of getting a dump of your default context to search for 2010 pool FQDN.
5. This problem prevented us from moving to complete the simple task of removing the last 2010 pool from the topology.
6. To keep it simple you can try this first. The lync user in question would not come up in Lync Server Control Panel. Try this from your 2010 shell and your 2013 shell (although they really are doing the same thing in the background)
get-csuser | ft SipAddress,Registrarpool >C:\output.csv.
7. Finally, Lync Control Panel pulls information from the SQL database, while the Shell command pulls from Active Directory. We need to clean active directory when we see the error like below:
The process to follow; make sure you go to the 2010 machine. to run the get-csuser and other commands (shown in the error above), in search of AD objects that may cause you a problem removing your 2010 pool.
This list of command you need to run is located in this fine article here
You could manually remove the user objects from AD. The main thing to remember is to check disabled AD users. So the short list old OCS users, Old disabled users, old 2010 users when verifying from 2013. This seems like a very easy area to get stuck when trying to decommission. Remember they may not show up anywhere!
Once again- get-csuser | ft SipAddress,Registrarpool >C:\output.csv.
In conclusion, you may find this esoteric when on site, but please remember Pirates of the Caribbean. Simple things up front can become the royal pains at the end. In Pirates, the solution is Rum and Swashbuckling. In Lync, The answer may just be the same!