M
Meinolf Weber
Hello patrick,
see inline.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
The only thing you have to look, is moving NOT seizing the 5 FSMO roles to
another DC. If you have an Exchange server youb have to look that the Recipients
update services are pointing to one of the other DC's.
If you mean this one (http://support.microsoft.com/?kbid=555846&SD=tech),
that's only for orphaned DC's. After the demotion the machine should automatically
move from DC OU to the computers container. If this is the case, then the
machine is only a member server, which can just be deleted like a normal
computer account. Before deleting this object give time for replication between
all DC's that they also update theire databases about the removed DC. And
you should also check with dcdiag and netdiag for errors.
Also replmon to check replication between the DC's can be useful now:
http://technet2.microsoft.com/windo...a6a7-4ced-984e-972aec2cbdd21033.mspx?mfr=true
If all looks good, delete it.
see inline.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
Hi Meinolf,
After demote AD01, I just delte the AD01 container IN "AD Sites and
services"-> "Default-First-Sites-Name"->"Servers"--AD01"
Then no more group policy errors found on any machine that i logon.
Fine.
AD01 is a first install DC, it is something bound to first insatall
DC?
The only thing you have to look, is moving NOT seizing the 5 FSMO roles to
another DC. If you have an Exchange server youb have to look that the Recipients
update services are pointing to one of the other DC's.
I'll try to remove DC completely according to your doc?
If you mean this one (http://support.microsoft.com/?kbid=555846&SD=tech),
that's only for orphaned DC's. After the demotion the machine should automatically
move from DC OU to the computers container. If this is the case, then the
machine is only a member server, which can just be deleted like a normal
computer account. Before deleting this object give time for replication between
all DC's that they also update theire databases about the removed DC. And
you should also check with dcdiag and netdiag for errors.
Also replmon to check replication between the DC's can be useful now:
http://technet2.microsoft.com/windo...a6a7-4ced-984e-972aec2cbdd21033.mspx?mfr=true
If all looks good, delete it.