Our process for reimaging is to first put the machine in a workgroup (remove it from AD), remove it from SC, reimage, add it back into the domain/OU.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Phil Schwan Sent: Friday, February 17, 2017 7:10 PM To: mssms@lists.myitforum.com Subject: [mssms] RE: computer won't join domain if already in subdomain (sccm MDT TS) Basically, you're trying to join a computer to the domain that already has a computer account in the domain, but because you're specifying a different OU for the join action it's causing the failure. You identified two of the three solutions: use a different name (thus creating a completely new computer account), or delete the original object so it can create a new object in the desired OU. The third option would be to move the object either before or after imaging (or, more specifically, the Setup Windows and ConfigMgr task) and let it use the original account. -Phil From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Chobeaux, Sebastien Sent: Friday, February 17, 2017 12:40 PM To: mssms@lists.myITforum.com<mailto:mssms@lists.myITforum.com> Subject: [mssms] computer won't join domain if already in subdomain (sccm MDT TS) Hello, during our win7 to win10 migration I'd like to have our computers in the main domain under a specific OU. Problem is the majority of those machines are currently under a subdomain, and if we don't change their name or delete the computer object in AD they won't join the domain at all. I'm using SCCM 1610 with mdt2013 Update2 integrated UDI task sequence. The apply network settings doesn't throw errors in smstslog but the netsetup.log state: 02/16/2017 16:44:02:056 NetpModifyComputerObjectInDs: ldap_add_s failed: 0x13 0x21c7 02/16/2017 16:44:02:056 NetpCreateComputerObjectInDs: NetpModifyComputerObjectInDs failed: 0x21c7 02/16/2017 16:44:02:056 NetpDisplayDupeSPNJoinError: Duplicate SPN found in the forest. Please run the following Powershell command to find the source: Any idea of a workaround ? I feel it's something specific to MDT, but can't figure out what to do to correct the issue. Thanks! -- Sébastien Chobeaux Service Informatique / IT department 416 397 6564 x73740 / 416 524 8524 CSDCCS, 110 Drewry Avenue, m2m1c8, toronto. ________________________________ AVIS IMPORTANT: Les renseignements contenus ou joints à ce courriel sont pour l'usage exclusif du destinataire ou de l'institution à qui ce courriel s'adresse et peuvent contenir des renseignements privilégiés, confidentiels et exempts de divulgation conformément à la Loi sur l'accès à l'information municipale et la protection de la vie privée. Dans l'éventualité que le récepteur du présent courriel n'est pas le destinataire concerné ou la personne autorisée à acheminer le message au destinataire concerné, vous êtes, par la présente, avisé(e), que toute divulgation, diffusion, distribution ou reproduction de la présente communication est strictement interdite. Si vous recevez ce message par erreur, veuillez immédiatement en informer l'expéditeur ou l'expéditrice par courriel et détruire celui-ci ainsi que toutes les pièces jointes qu'il comporte. Merci de votre collaboration.
