Redeployed computers stuck for a long time before OSD finished

jacobccjude 385 Reputation points
2024-10-10T16:32:13.2533333+00:00

I have deployed a new Windows 11 task sequence for some old Windows 10 computers. They finish the OS installation and then will be stuck on the "getting ready" page for a long time, about one hour. After that, I can log in the computers but find they have not joined our domain.

I already give the domain join account proper permissions; the same task sequence works well for bare computers. What's wrong here?

Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
990 questions
Microsoft Configuration Manager
0 comments No comments
{count} votes

Accepted answer
  1. Simon Ren-MSFT 35,311 Reputation points Microsoft Vendor
    2024-10-11T01:28:36.5+00:00

    Hi,

    Thank you for posting in Microsoft Q&A forum.

    1,Please review the smsts.log, setupact.log and setuperr.log on the clients to see if there is any further information.

    2,Do the redeployed computers use the same computer name? If yes, please delete the computer objects in AD and then try again. Per my experience, we cannot re-image a PC with the same name without deleting it.

    Similar thread for your reference: Windows 11 OSD TS getting stuck on "Getting Ready"

    Thanks for your time. Have a nice day!

    Best regards,

    Simon


    If the response is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.