<div>
<div class="content wysiwyg-content">
These PC's are IBM Kiosks and configured to log onto our domain automatically. &nbsp;Two sites - Los Angeles and New York. <br />
In LA, post imaging with Ghost, a script runs (written by the previous admin) which joins the PC to the domain and changes the SID. &nbsp;After 8 kiosks were imaged and joined to the domain, it was noticed afterwards that those 8 computer names were already allocated in AD and online in NY. (I know...) &nbsp;These 8 kiosks in LA need to be shipped to NY soon to join the other kiosks, and I need to know how to fix this without hopefully requiring any work (rejoining the domain and so forth) to be done on the old, original NY kiosks.<br />
I would expect the original kiosks in NY to fail logging into the domain at their next reboot because their computer object in AD was overwritten when the newer kiosks in LA were joined to the domain. &nbsp;I had thought about renaming the newer kiosks and attempting to reset the computer accounts in AD, but I've never done anything like this before, and am unaware of the ramifications. &nbsp;Would anyone care to assist me through this dilemma please?<br />

</div>
</div>


These PC's are IBM Kiosks and configured to log onto our domain automatically.  Two sites - Los Angeles and New York. 
In LA, post imaging with Ghost, a script runs (written by the previous admin) which joins the PC to the domain and changes the SID.  After 8 kiosks were imaged and joined to the domain, it was noticed afterwards that those 8 computer names were already allocated in AD and online in NY. (I know...)  These 8 kiosks in LA need to be shipped to NY soon to join the other kiosks, and I need to know how to fix this without hopefully requiring any work (rejoining the domain and so forth) to be done on the old, original NY kiosks.
I would expect the original kiosks in NY to fail logging into the domain at their next reboot because their computer object in AD was overwritten when the newer kiosks in LA were joined to the domain.  I had thought about renaming the newer kiosks and attempting to reset the computer accounts in AD, but I've never done anything like this before, and am unaware of the ramifications.  Would anyone care to assist me through this dilemma please?


Joined new PC to domain, unkown that another PC of same name preexists.

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.