Migration windows 2000 AD to wiàndows 2003 AD
hello,
here situation :
i have 1 root domaine 6 root dc, with 20 child domain, with hundreds sites, , have change windows 2000 windows 2003 dc.
how know wich dc hold data of sites , services ?
where stored informations sites , services ?
during migration windows 20003 dc, is data of sites , services hold old windows 2000 dc move new dc or not ?
thank answer
regards
romain
here situation :
i have 1 root domaine 6 root dc, with 20 child domain, with hundreds sites, , have change windows 2000 windows 2003 dc.
how know wich dc hold data of sites , services ?
where stored informations sites , services ?
during migration windows 20003 dc, is data of sites , services hold old windows 2000 dc move new dc or not ?
thank answer
regards
romain
how know wich dc hold data of sites , services ?
every domain controller holds copy of sites , services configuration... stored in active directory under configuration partition... on every domain controller in active directory forest.
cn=sites,cn=configuration,dc=....etc
where stored informations sites , services ?
question makes no sence me.
during migration windows 20003 dc, is data of sites , services hold old windows 2000 dc move new dc or not ?
that purpose of active directory compared old sam databases... kcc (knowledge consistancy checker) automatically triggers replication of active directory data according algorithm intrasite replication , according site links intersite replication. want install new 2003 domain controllers in each domain "additional domain controllers" during dcpromo process. promoted... automatically added correct site, domain controller determines looking @ subnet, , compares correct subnet objects in active directory sites , services , site linked to.
additional information
think of active directory pie. in pie there number of partitions. there partitions available forest wide, example schema, rootdse , configuration partitions. there partition unique each domain of forest... call them domain partitions people refer them "default naming context". domain partitions use seeing... have pretty interfaces such active directory users , computers displays all. domain partitions contain organisational units, computer accounts, user accounts , groups create.
every domain controller in forest contains copy of forest partitions, not domain controllers can write these partitions. fsmo (flexible single master of operation) roles come in. example domain controller containing schema master role domain controller in forest can write schema partition. other domain controllers have read copy. there 2 forest wide fsmo roles , 3 fsmo roles unique each domain, need ensure move these well.
i hope doing project senior engineer... otherwise in bad day.
kind regards,
clint boessen mcse, mcitp: messaging
l7 solutions, microsoft gold partner
perth, western australia
every domain controller holds copy of sites , services configuration... stored in active directory under configuration partition... on every domain controller in active directory forest.
cn=sites,cn=configuration,dc=....etc
where stored informations sites , services ?
question makes no sence me.
during migration windows 20003 dc, is data of sites , services hold old windows 2000 dc move new dc or not ?
that purpose of active directory compared old sam databases... kcc (knowledge consistancy checker) automatically triggers replication of active directory data according algorithm intrasite replication , according site links intersite replication. want install new 2003 domain controllers in each domain "additional domain controllers" during dcpromo process. promoted... automatically added correct site, domain controller determines looking @ subnet, , compares correct subnet objects in active directory sites , services , site linked to.
additional information
think of active directory pie. in pie there number of partitions. there partitions available forest wide, example schema, rootdse , configuration partitions. there partition unique each domain of forest... call them domain partitions people refer them "default naming context". domain partitions use seeing... have pretty interfaces such active directory users , computers displays all. domain partitions contain organisational units, computer accounts, user accounts , groups create.
every domain controller in forest contains copy of forest partitions, not domain controllers can write these partitions. fsmo (flexible single master of operation) roles come in. example domain controller containing schema master role domain controller in forest can write schema partition. other domain controllers have read copy. there 2 forest wide fsmo roles , 3 fsmo roles unique each domain, need ensure move these well.
i hope doing project senior engineer... otherwise in bad day.
kind regards,
clint boessen mcse, mcitp: messaging
l7 solutions, microsoft gold partner
perth, western australia
Windows Server > Directory Services
Comments
Post a Comment