none
Move-CSLegacyUser : Object not set to an instance of an Object RRS feed

  • Question

  • Hi,

    I'm currently supporting an OCS to Lync 2013 migration.

    I've recently installed the April 2016 Lync Server 2013 CU on our Lync servers.

    Since this was installed, migrations from OCS to Lync are failing with this error:

    "Object not set to an instance of an Object"

    The user move is then marked as incomplete - we have to use disable-csuser then re-enable then on Lync, but the user loses their buddy list.

    We can also do a force on the move-cslegacyuser command but again the user loses their buddy list.

    Same is true of the latest Lync 2013 CU as well.

    If I roll back these CUs, the migrations start working again.

    Anyone have any suggestions how to fix this?

    Cheers,

    Garry

    Wednesday, June 29, 2016 12:29 PM

Answers

All replies

  • Hab has moved the users using the backup:

    Move-CSLegacyUser : Object not set to an instance of an Object

    (starting from middle of article)


    Petri

    Wednesday, June 29, 2016 7:40 PM
  • Hi Garry, 

    Lets also make sure that we have updated OCS 2007 R2 with the latest update that we  can get. 


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

    Friday, July 1, 2016 9:12 AM
  • Hi Garry N,

    You could try to manually clean up Active Directory OCS properties of legacy users.

    Please reser to the following link, it is Lync 2010 but similar to Lync server 2013

    https://valygreavu.com/2011/03/03/lync-server-2010-move-legacy-users-troubleshooting/

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

    Best regards,

    Alice Wang


    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. <p style="margin:0cm 0cm 0pt"><span lang="EN-US" style="color:#0070c0; font-family:&quot;Segoe UI&quot;,&quot;sans-serif&quot;; font-size:10pt">Alice Wang <br/> TechNet Community Support</span></p> <p style="margin:0cm 0cm 0pt"><a href="http://blogs.technet.com/b/onescript" rel="nofollow"><img src="https://xnoegg.bay.livefilestore.com/y1plmwd9pFqoTZWcmr6-bsBuS7hTcNbr8YdT4WL3RRAuhDPVyUUOVchQt3EexNEBj4xYyornsD1kyLmtVqqsDfKv3PEEg9ejQzT/signature.jpg?psid=1" alt="" width="430" height="30.2"></a></p>

    Monday, July 4, 2016 1:04 AM
    Moderator
  • We didn't find a root cause as we rolled back the updates made by the CU, migrated our remaining OCS users to Lync then applied the CU again.

    Thanks for the suggestions though.

    Wednesday, July 6, 2016 7:56 AM