Using WIM images I'm seeing objects that do not get added to the domain once they are remove if reimaging system. I do however have used the joindomain scripted, anwser file.

But we  have noticed new systems get added without any issues just reimaged systems that have the issues.

We do remove the object from AD or do a dsquery to find the system but no results on a reimage.

 

I have used netbios name, etc. etc.

Best of Luck! :)

Answer Summary:
image machines with a local autologin in the sysprep ans files then join the machine to the domain and autologin it in with post script commands
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

1

I image my machines with a local autologin in the sysprep ans files then join the machine to the domain and autologin it in with post script commands

Answered 03/13/2013 by: SMal.tmcc
Red Belt

  • I also generally suggest the postinstall task method of entering the domain. I have seen reliability issues with using the Sysprep UnattendJoin method of joining the domain.
Please log in to comment

Answers

0

Are the computer accounts being moved to a different OU in AD after new systems are imaged? joindomain will probably try to place the machine in the default OU (e.g. computers) but fail if the machine GUID exists in another OU (RIS used to fail with this).

Answered 03/15/2013 by: andys0123
Orange Senior Belt

Please log in to comment
0

thanks I got it fixed. Using both the answer file and vbs (kace) scripted it works just fine. wierd Microsoft voodoo.

Answered 03/18/2013 by: mikesharp1
Second Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity