Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
AD Replication w/parent & child domains
- Thread starter emaybee
- Start date
mlichstein
MIS
There are three basic partitions, or naming contexts in Active Directory: the domain naming context, the configuration naming context, and the schema naming context.
The schema and configuration naming contexts are replicated to all domains in the forest. The schema naturally contrains the schema information, and the configuration contains information about the site topology, Exchange, etc.
The domain naming context is unique for each domain in the forest. Each domain's naming context is replicated only between DCs in that domain.
So to answer your question, the information replicated between a parent and child domain would be the configuration information (sites) and the schema.
The schema and configuration naming contexts are replicated to all domains in the forest. The schema naturally contrains the schema information, and the configuration contains information about the site topology, Exchange, etc.
The domain naming context is unique for each domain in the forest. Each domain's naming context is replicated only between DCs in that domain.
So to answer your question, the information replicated between a parent and child domain would be the configuration information (sites) and the schema.
- Thread starter
- #3
Thank you.
With that said here's a couple of questions.
1. Let's say that there is a user whose account is located in the parent domain but needs to use resources in the child. Currently 'parent' user cannot log into the child. How can I make this happen?
2. If the parent domain server goes down, users cannot log into the child domain if I'm correct. What would be good is if I can replicate the parent user accounts to the child domain server. In theory this would lessen network traffic and makes the child domain usable in case of a catastrophe. Can I make this happen?
Michael
With that said here's a couple of questions.
1. Let's say that there is a user whose account is located in the parent domain but needs to use resources in the child. Currently 'parent' user cannot log into the child. How can I make this happen?
2. If the parent domain server goes down, users cannot log into the child domain if I'm correct. What would be good is if I can replicate the parent user accounts to the child domain server. In theory this would lessen network traffic and makes the child domain usable in case of a catastrophe. Can I make this happen?
Michael
mlichstein
MIS
1. There is an automatic trust relationship that is established between parent and child domains. In order to give users from one domain access to resources in the other, you just need to give them permission.
For example, if you look at the file permissions for a folder in the child domain, you can add a new user, browse to the parent domain, select the user or group that you want from that domain and then select the appropriate permissions.
2. If the parent DC goes down, users in the child domain should be unaffected, as long as there is a DNS server in that child domain that they are configured to use, and there is a GC that they can access. The only thing they will be missing is the schema master and the domain naming master. Schema is only needed if you are making changes to the schema, and domain naming is only needed if you are adding or removing domains from the forest.
Also, users will be unable to access any resources in the parent domain that they might have access to, but that is expected. They should be able to function within their own domain with no problems.
For example, if you look at the file permissions for a folder in the child domain, you can add a new user, browse to the parent domain, select the user or group that you want from that domain and then select the appropriate permissions.
2. If the parent DC goes down, users in the child domain should be unaffected, as long as there is a DNS server in that child domain that they are configured to use, and there is a GC that they can access. The only thing they will be missing is the schema master and the domain naming master. Schema is only needed if you are making changes to the schema, and domain naming is only needed if you are adding or removing domains from the forest.
Also, users will be unable to access any resources in the parent domain that they might have access to, but that is expected. They should be able to function within their own domain with no problems.
- Status
Similar threads
- Locked
- Question
