Hi,
The solution to this problem is actually a modified version of #2. What you
want to do is setup at least one more domain controller in the new unit, and
mark it as a global catalog. Open AD Sites & Services, and create a new
site. Put the new DC(s) in this site. You'll also need to define a site-link
for connecting this site to the main office, and a cost value that
determines how often replication will take place.
The users in the second unit will automatically recognize that they're in
this site, and authenticate against their local DCs.
--
--Brian Desmond
Windows Server MVP
(E-Mail Removed)
Http://www.wpcp.org
Beta #469090
"Citimouse" <(E-Mail Removed)> wrote in message
news:3f06617a$(E-Mail Removed)...
> Hi All,
>
> I have a problem and hope anyone can help me.
>
> Our office is going to expand to another unit in the building. The new
> office will be on a different level as the current one.
>
> I will need to setup a network in the new office. However, I am hesitant
on
> the implementation of it. Our preference is to try to keep the whole
office
> in the same domain. However, we also can accept setting up a different
> domain in the new office. We are all using Windows 2000 servers.
>
> Now I have 2 choices.
>
> 1. Setup a new domain and establish a trust between the new domain and the
> current domain. This will involve new hardware cost and there will be
> difficult maintaining 2 domains.
>
> 2. User will log on into current domain. We will need to open up the
> firewall port on this and logging into the current domain in a different
> location may take a long time.
>
> Now I am quite confused on which option to choose. I would prefer option
1.
> If we were to choice option 1, may I know what are the things I will need
to
> take note of? And what about option 2? Is it feasible and what to take
note
> of too?
>
> Thank you.
>
> Wei Yu
> Singapore
>
>
>
>
>
>
>
Similar Threads
