NT4 to Win2k3 Considerations
From: Chad Specht (cspechtatnospamohnwarddotnet)
Date: 02/10/04
- Next message: Admin: "Re: After upgrading 2000 server to 2003 server keeps restarting"
- Previous message: Joe Wu [MSFT]: "RE: After upgrading 2000 server to 2003 server keeps restarting"
- Next in thread: Jimmy Andersson [MVP]: "Re: NT4 to Win2k3 Considerations"
- Reply: Jimmy Andersson [MVP]: "Re: NT4 to Win2k3 Considerations"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 10 Feb 2004 06:46:36 -0600
We're debating on an AD structure/design. Currently, we have one NT4
domain, 16 sites via WAN (512k through 1MB connections) - each with their
own BDC/App/File/Print server (1 machine). We're planning on an in-place
upgrade.
Our situation consists of 4 companies under the care of one holding company.
Should we create a single domain, single forest (ie. holdcompany.com)? If
so, can we create child domains without impacting GC decisions - like
replication, GC server placement, etc. (ie. companyA.holdcompany.com,
companyB.holdcompany.com, etc.)? Or should we not do the child domains?
What are the ramifications for going one way or the other?
Thanks for the feedback in advance.
-Chad
- Next message: Admin: "Re: After upgrading 2000 server to 2003 server keeps restarting"
- Previous message: Joe Wu [MSFT]: "RE: After upgrading 2000 server to 2003 server keeps restarting"
- Next in thread: Jimmy Andersson [MVP]: "Re: NT4 to Win2k3 Considerations"
- Reply: Jimmy Andersson [MVP]: "Re: NT4 to Win2k3 Considerations"
- Messages sorted by: [ date ] [ thread ]