In
David said:
Hi again.
Yes, you right, Course 2152c.
I thought so.
I'm not a trainer. I've been working making another things
without problem until I used dcpromo to demote the DC
(previous copy). I promote again (I'm have not used my
back up) and it start to go wrong.
That is the WHOLE problem. AD is SID/GUID specific besides references being
held in the forest root for all child domains or references for all computer
accounts and member servers in their specifi domain.
If the student machines (Vancouver, Denver, Acapulco, etc) are either joined
to the domain or are part of a child domain of Nwtraders.msft (London) and
you demoted London and then re-promoted it, even if you used the same
computer and domain name for London, it is NOW a totally NEW and DIFFERENT
domain. Then the computer accounts and/or child domains will have lost their
identity in the forest root or domain they were once joined to.
To fix, and if these are just member servers, you would either have to
dis-join and re-join the machines (if member servers).
If the students (or you) made them child domains (Namerica, Samerica, etc),
then you would have to demote these machines with the dcpromo /forceremoval
switch (need a dcpromo.exe update to make this work) and then re-promote the
child domains. If you don't have the DCPROMO update, then you would have to
literally reinstall the machines from scratch. There is also a manual method
to do this.
So depending on your scenario, they are your choices.
I have no a ghost image or something like that.
In all clients I use london (192.168.0.1) as DNS server.
As most of the classes do.
I'm thinking in reinstall all again, but I would like to
know more about this problem.
Well, anything help will be ok.
I hope my explanation above helps in understanding what happened.
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory