Lync 2010 Recurring meetings don't work post-migration when 2010 server is shut down

Question

I've got an interesting issue here. I completed my Lync Server 2010 -> 2013 migration about 6 months ago, and everything has been going fine as far as I can tell. I left one of the servers up and running in the 2010 pool for a while. I finally decided
it was time to fully decommission Lync Server 2010, so I shut down my 2010 server. I did not delete from the topology just yet, in case something bad happened. Well, when I shut it down, I got reports from some users that they couldn't get into their Lync
Meetings.
The only conclusion I have been able to draw is that this happens for recurring meetings that were scheduled before the Lync Server 2013 migration. It seems that those meetings did not get migrated with the users. Does anyone have any guidance for this situation?
I'm guessing there's no way to actually move the meetings. At best, I'd like to simply be able to identify users who are in this situation and have them reschedule their meetings. I think there are few enough of them that we can handle that.

Answer 1

That's seems odd per:
http://technet.microsoft.com/en-us/library/jj688011.aspx 
What is the user experience?
Have you followed all the decommission steps? Have you tried Move-CsConferenceDirectory:
http://technet.microsoft.com/en-us/library/gg412968.aspx
"When you create a dial-in conferencing Uniform Resource Identifier (URI), those URIs are assigned unique SIP addresses. However, SIP addresses are difficult to translate to devices that are not SIP-aware; for example, a public switched telephone network
(PSTN) telephone can’t translate a SIP address. Because of that, Lync Server uses conference directories as a way to help these devices locate, and connect to, dial-in conferences. This is done by creating a SIP conference directory that is associated with
each dial-in conferencing URI, and is identified by an integer value rather than a SIP URI. PSTN telephones and other devices can then use these numbers instead of a SIP URI when connecting to conferences; the directory number is included in the PSTN conference
identification users enter when connecting to a dial-in conference.
Occasionally, you might need to move a conference directory from one pool to another; for example, if you decommission a pool you might need to move your existing conference directories to a new location. The
Move-CsConferenceDirectory cmdlet enables you to move conference directories to a different pool."
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications