Re: AD Configuration

From: Al Mulnick (amulnick_No_SPAM_at_ncDOTrr.com)
Date: 01/17/05 

Date: Mon, 17 Jan 2005 10:33:55 -0500

Goals as stated: Central administration

Some things to check:
Have you already read the branch office deployment guide? It's full of
information that would be useful to you. Depending on your requirements, you
may not need multiple domains, but rather mulitple sites. Depending on your
network topology (now or future) you may not need as many DC's. The reason
to keep those numbers low? Simplicity. With simplicity, comes reliability
and lower costs (often) than otherwise would be had. Forgetting expenses,
reliability is often worth it.

VPN's often have enough bandwidth, but keep an eye on available bandwidth
for those links and the amount of changes you intend to have. A retail
environment may have a high turnover if I had to guess, meaning that you may
have constant administration going on resulting in replication traffic.
Other traffic on the wire will take some bandwidth as well, so it's
important to watch that available bandwidth vs. the amount of bandwidth when
planning this out.

FWIW, I think you can and should do what you're saying. Trusts being
'screwed up' has me concerned since it would take a bit to do that.
Replication? What happened? Those kinds of things make it worth it to
streamline the architecture IMHO.

I'm assuming 2003 is the AD infrastructure here. It's a good idea to get to
2003 if not already there. Better replication and behaves better in a
branch office scenario like you describe.

Al

"msteinhoff" <msteinhoff@naturalretail.com> wrote in message
news:%23OnCE1J$EHA.2032@tk2msftngp13.phx.gbl...
>I work for a retail company that has 12 locations spread throughout the
>U.S. Each of these locations connects back to the Main Office via a
>hardware VPN solution. Each of these locations is also it's own domain. so
>in essence I have:
>
> corp.com
> store1.com
> store2.com
> store3.com
> etc....
>
> The previous network admin had no clue and has let all kinds of bad things
> happen. Servers are not replicating, trusts are all screwed up, I could
> go on and on. I have worked these problems for hoursa with no solution.
>
> I am would like to centrally admin all of these locations from the main
> office, and I am considering turning each into a child domain. The new
> network would be:
>
> server1.corp.com
> store1.corp.com
> store2.corp.com
> store3.corp.com
>
> Does anyone have input as to whether this is a good or bad idea? Reasons
> to keep it the same?
>

Relevant Pages

  • Re: AD Configuration
    ... I downloaded and read the Branch Office Deployment ... big to support the number of servers they are suggesting..9 total. ... > VPN's often have enough bandwidth, but keep an eye on available bandwidth ... > may have constant administration going on resulting in replication ...
    (microsoft.public.windows.server.active_directory)
  • Re: Active Directory Design
    ... and control replication. ... Replication isn't really an issue with so few users - intersite replication ... The branch offices are each connected to the main office through a 56k Frame Relay. ... users in the branch office must be able to work locally even if the Frame goes down. ...
    (microsoft.public.win2000.active_directory)
  • Re: AD Sites and Services Best Practices
    ... does this mean that you have four separate domains (each corresponding to ... Office" domain in branch offices will actually increase replication. ... Office will have a Domain Controller. ... I will create the subnets for each site (Main Office and Branch Office) ...
    (microsoft.public.windows.server.active_directory)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... branch office DC running Windows 2003 Standard. ... The remote site is using 192.168.1.* and the SBS is running the ... The problem I'm having now is that it doesn't appear that replication ...
    (microsoft.public.windows.server.sbs)
  • Re: Site links and replication
    ... It is NOT necessary to make replication work, ... Sorry what I meant is in the event the link between Central Office - ... Branch Office fails, I still have the secondary link which goes from ... This assumes I have another WAN link between Sub Branch and Central ...
    (microsoft.public.windows.server.active_directory)