Rejoin PC's after DC rebuild - how to not hose the profiles?

[Doug]

Only DC in the domain and it puked, so I had to rebuild it. Gave it
the same domain name, IP, etc... Now the next part is my bad, but I
admit it!

Took 2 of the client PC's (all Win2k Pro) back to workgroups, then
rejoined the domain, which hoses the user profiles. Yes, the old
profile (user)is still there and can be manually copied to the new
(user.domain) profile, but what a pain in the ass!! Then I got the
bright idea that if I recreate the computer accounts in AD, the other
PC's might just come back up without rejoining the domain, and it
worked... kind of...

The non-rejoined PC's cannot access shared resources on the rejoined
PC's, and vise-versa. The non-rejoined PC's do not register in DNS.
On one of the non-rejoined PC's the Domain Users can log onto the
domain without issue, but the Domain Admin account cannot, tells me it
cannot find the domain.

So, is there a better way to rejoin PC's to a rebuilt domain that
doesn't hose the profiles????

 

[Richard]

I have experienced this same problem. I never did find a
way around the main issue.
What I did do is copy the profile from the domain profile
to a local profile. demoted the PC back to a workgroup.
Promoted the PC back to the domain and then copied the
local profile back to the domain profile on the local
machine. (you can do this through the user profiles
option {right click on "my computer" then go to
properties. Advanced tabe.}

About the only thing you can do is to restore the system
state on the PC once you have Windows 2000 back online.
This would give you the old AD so you wouldn't have to re-
enter the accounts again. The only problem I have had
with this install is when the hardware changed. Some of
my features didn't want to play well.
I hope this helps.

Richard

 

[Doug]

hehe.... Yeah, I had to rebuild it twice thanks to doing an AD restore....