/build/static/layout/Breadcrumb_cap_w.png

WIM Imaging system are not getting added to domain

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! :)


0 Comments   [ + ] Show comments

Answers (3)

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
Posted by: SMal.tmcc 11 years ago
Red Belt
2

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


Comments:
  • 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. - andrew_lubchansky 11 years ago
Posted by: andys0123 11 years ago
Orange Senior Belt
1

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).

Posted by: mikesharp1 11 years ago
2nd Degree Black Belt
1

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

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ