<div>
definitely NO.<br />
the user and computer accounts have it's own identifier SID which is determining all the permissions and is translated to a name.<br />
so if you just reinstall the server the computer accounts will not update as this process of creating computer account in AD is done when joining the PC into the domain when the new SID for the workstation is generated.<br />
Equal behaviour is when logging with a &quot;new&quot; username which is the same as the allready used - there will be a username.000 profile in the documents and settings folder created with new settings.
</div>


<div>
Huh...good thought, I have never tried this. &nbsp;But I would think there is a good chance that the profile on the desktop will re-link itself when in the new (same named) domain.<br />
<br />
I'm not sure what type of problem you are experiencing. &nbsp;You might try fixing the problem by doing something like this:<br />
<br />
Say you had 3 domain controllers...<br />
<br />
1) Move the FSMO roles to the best DC. &nbsp;Make sure that this server is a GC as well<br />
2) Run DCPROMO on the other two servers to remove the DC role<br />
3) format the old DC's.<br />
4) Get AD back in good shape on the remaining DC. &nbsp;DCDIAG can analyse this for you...also make sure no Event viewer are showing. &nbsp;At this point, the domain still lives and clients are untouched. &nbsp;(make sure you move DNS/WINS/DHCP/etc to this server if it doesn't already have it)<br />
5) On the old DC hardware, install fresh Windows 2003 and add these servers back as DC's...<br />
<br />
just a thought.
</div>


<div>
(I stand corrected...seems like the profile will not link itself) &nbsp;Would have to copy profile...or change name and security of profile folder...
</div>


<div>
I'm with NJComputerNetworks on this one.... its seems to me the best thing would be to fix their existing AD rather than start over from scratch. &nbsp;What exacly is the problem with their AD now, is it the hardware of their servers, or is their AD database messed up???
</div>


<div>
AD Icons are missing, Event logs are missing, group policy object are missing, SmartStart not installed, etc. It's just a small network, not very complicated.
</div>


<div>
<div class="content wysiwyg-content">
We have a new, small client whose AD and servers are in bad shape. Our plan is to reload the servers and start over fresh with AD. If I recreate AD with the same domain name and same user names, can I rejoin the workstations to the new domain and the users recieve the same workstation profile they had before. I know I can copy the profile, but I'm trying to do this as economically as possible.<br />

</div>
</div>


We have a new, small client whose AD and servers are in bad shape. Our plan is to reload the servers and start over fresh with AD. If I recreate AD with the same domain name and same user names, can I rejoin the workstations to the new domain and the users recieve the same workstation profile they had before. I know I can copy the profile, but I'm trying to do this as economically as possible.


Joining workstations to a domain

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).