Re: Server crash Re-created AD resulting problems

I was hoping the answer would be otherwise, but thank you for clearing
it up and confirming. I now at least have a firm list of tasks for my
next visit.

D

On Thu, 28 Jun 2007 12:19:28 -0600, "Danny Sanders"
<DSanders@xxxxxxxxxxxxxxx> wrote:

After having to re-install Windows Server 2003 completely, we managed

If you did not have another DC on the domain when you did this, you created
a new domain. Even if you name it the same as the old DC, the SID is
different. Different SID=Different domain. This is the main reason the MS
best practice is to have more than one DC on a domain.

All the workstations in the office still think they're members of
ABC.LOCAL. However, I have a suspicion that they're really not
authenticating but only using a still-cached copy of the previous
ABC.LOCAL. I hope I'm wrong about this.

No you are not wrong.

Is there a way to simply add them back as Directory objects without
having to leave and then re-join the domain on the workstations? A

No.

I think that if the computers were added to the new, although
samely-named, domain, the issues can clear up.

Please advise. If what I want to do is not possible, also please
advise if you can suggest any "best" approach.


There is only one approach, remove the workstation from the old domain and
add them to the new.

PS I've tried to remove, re-join, then login as administrator and go
to the user profiles tab in system properties to "copy" the profile to
the newly created folder, but windows gave me an error it could not do
it.

You need to work out this error. See if this helps:
http://support.microsoft.com/kb/324734/en-us

hth
DDS


"Atreju" <someone@xxxxxxxxxxxxxxxxxx> wrote in message
news:p2q783lh9s2icea4q5en90bt8v4bcov1r1@xxxxxxxxxx
Dear all,

I am praying someone can help me.

A client has a server with RAID 5, 3 drives. Unfortunately, the
manufacturer neglected to mention that there was a KNOWN firmware bug
in the drives, and the end result was having 2 consecutive crashes of
the array.

After having to re-install Windows Server 2003 completely, we managed
to retain pretty much all the data on the second partition. However,
I'm faced with the following problem:

We created the domain with the same name as it was before... let's
call it ABC.LOCAL

All the workstations in the office still think they're members of
ABC.LOCAL. However, I have a suspicion that they're really not
authenticating but only using a still-cached copy of the previous
ABC.LOCAL. I hope I'm wrong about this. The suspicion arises from a
few little glitches I've encountered; for example, on one computer,
even though it says computername.ABC.LOCAL, if I go into the local
administrators group and try to add objects, it won't see the domain
as a repository, only the local. Some other minor indications as well.

One of the main problems I face now is that although I've re-created
all the users, and they can login, none of the computer names appear
in ActiveDirectory under "COMPUTERS" section.

Is there a way to simply add them back as Directory objects without
having to leave and then re-join the domain on the workstations? A
colleague of mine told me that's the only way he knows of, but I'm
hoping there is a way to do it dynamically without the need for
removal and re-join. The reason is that this method which I used on
two stations has created whole new local profile folders for the
users, and it has been quite a nuisance getting everything
transitioned to their satisfaction. There are some proprietary
applications they use which are also not cooperating very well with a
new local profile.

I think that if the computers were added to the new, although
samely-named, domain, the issues can clear up.

Please advise. If what I want to do is not possible, also please
advise if you can suggest any "best" approach.

PS I've tried to remove, re-join, then login as administrator and go
to the user profiles tab in system properties to "copy" the profile to
the newly created folder, but windows gave me an error it could not do
it.

Thanks so much for any help you can offer


.

Quantcast