• State Verified Answer
  • Replies 3 replies
  • Subscribers 19 subscribers
  • Views 972 views
  • Users 0 members are here
Options
Related

Move task stuck - domain join not executed

christian woelk
8 months ago

Hey guys,

we are just starting the mass migration for our clients. In some cases we have now seen the issue that the Move task keeps being in status "in progress". At this moment the task already has removed the computer object in the source and created a new one in the target. The user does not receive the popup that he is going to be logged of and so the actual domain join is not executed.

We waited for nearly an hour, but there was no further movement. When we checked on the client side, the user was working without interruption or network change.

Any idea how this can happen? Maybe due to moving to much PCs at the same time? We are talking here about only 10 clients in a batch.

I'm happy for any help.

  • 0 8 months ago

    The first thing I always check is the agent log on the client side - how far is the task actually getting according to the entries in the log?

    If the log mysteriously ends, I would suggest having a look at the Windows event logs on the client host to see if there are any warnings or errors being generated (possibly by some kind of end point protection?)

  • 0 8 months ago in reply to JohnnyQuest

    TBH in the past I have never found anything helpful in the client side log, so maybe I forgot about it. I will check it directly in the morning for the specific machines.

  • +1 8 months ago

    Now I know what happened and it is really hilarious. Indeed we, the migration team, have caused the issue. Unfortunately we have no certificate base authentication for the Wifi. So the user has to enter its AD credentials. Due to the domain change the credentials will not be valid anymore and so we wrote a script which we execute as post script together with the move task. This script will let the client forget the credentials for the Wifi.
    Actually we told the users to stay at the docking station while we are migrating them. But some of them stepped away with the device and so they have been connected to Wifi and the move task did cut off the network connection after the partial domain join. The domain join is finished btw, but the restart is missing. A simple restart and logon to the correct domain is everything what needs to be done.
    We are now chasing the users even more to stay connected to the docking station.