Through my experience the best way and cleanest way would be as follows.
1. Rename 20fs3 to something irrelevant like test123.
2. Remove it from the domain and join a workgroup.
This should clear all references in AD pointing to 20fs3.

3. Rename 20fs4 something irrelevant like test564.
4. Remove it from the domain and join a workgroup.
5. Rejoin the domain with the new name 20fs3.

I found that just removing 20fs3 from the domain still leaves references in
AD that can cause issues when trying to join another server with the same
name. So this pretty much assures everything is clean in AD regarding
computer names associated to SIDs.



"Guy" <Guy@discussions.microsoft.com> wrote in message
news:62C16E8A-DB2B-4B2B-BD8A-45E1ED45293D@microsoft.com...

No. these are NTFS permissions. You will see that after you remove it from
thedomain and view the permissions that they will appears as SID formats
only because they cannot replicate the names to the domain but once you
rejoin they will be able to replicate and be back to normal. You can just
rename the server without removing it from the domain but it is not as
clean. Dealers choice I guess.

"Guy" <Guy@discussions.microsoft.com> wrote in message
news:4C0E0F51-F674-43B9-B674-0B7E473C1E9A@microsoft.com...