Re: Advice on site topology

I think you need to forget buildings and networks and think about how the
two organisations are related to each other. The only relevance of the high
speed network is that you can locate servers for all users in either
building. The more the organisations have in common, the more they should be
in one domain perhaps in separate OU's. The less they have in common, the
more they should be in a different forest, joined by a Trust.
You need to explore a bit more what the requirements are.
- Will all users be in the same address book for e-mail, or separate address
books?
- Do you require separate security policies for the two organisations? For
example, is one of them pretty relaxed about passwords and the other
obsessive about security? Will you have one logical firewall to the Internet
or two?
- Might the two organisations become separate again in a few years?
- Can you implement the same user policies regarding the use of IT equipment
in both places?
Mostly you should start from the assumption of one domain, and work out what
essential requirements can not be met that way. Bad reasons for separate
domains are:
* the logon box
* IT people wanting to do their own thing
Your forest name was too specific when it was created in the past. It should
be as generic as possible to refer to the entity that is your organisation.
So now, it does not seem right for people in BuildingB to be logging onto a
domain called BuildingA. But lets imagine the domain was actually called
123. Would users in BuildingB still object to logging onto domain 123? If
not, then you need to do a domain rename to get out of a problem that was
created in the past.
If you have specific requirements for the two organisations that are
different, people here will be able to tell you whether they can be
implemented on one domain or forest, or not.
Anthony




"Richard Passey" <r.passey@xxxxxxxxx> wrote in message
news:%23qazBQUtGHA.4968@xxxxxxxxxxxxxxxxxxxxxxx
Sorry there was a typo:

Dear All,

I would appreciate some advice on the best way to expand my domain.

1) We are taking over a new building, it's local and we have fibre links
to
it. We therefore have the option of running the two networks on the same
physical network.

2) The "powers that be" would like services (Exchange, fileshares,
software)
from building A (where we are now,
buildingA.organisation1.mothercompany.co.uk) to be accessable in building
B, ie user A can go to building B and logon.

3) The "powers that be" would like building B to be distinct. Ie users
should see the domain there as being called
buildingB.organisation2.mothercompany.co.uk.

4) Our forest is currently called
buildingA.organisation1.mothercompany.co.uk. The new building will be
housing a separate organisation. When we designed the domain we planned
for
new buildings but not new oranisatons under our control.


The main questions are:

Would two separate Domains with Exchange run properly on the same physical
network?
-Then could I join the sites to share services?

Would it be best to have distinct networks and domains and link them in
some
way?

Is there some other way of organising this??




"Richard Passey" <r.passey@xxxxxxxxx> wrote in message
news:%233XzXMUtGHA.3264@xxxxxxxxxxxxxxxxxxxxxxx
Dear All,

I would appreciate some advice on the best way to expand my domain.

1) We are taking over a new building, it's local and we have fibre links
to it. We therefore have the option of running the two networks on the
same physical network.

2) The "powers that be" would like services (Exchange, fileshares,
software) from building A (where we are now,
buildingA.organisation1.mothercompany.co.uk) to have services in building
B.

3) The "powers that be" would like building B to be distinct. Ie users
should see the domain there as being called
buildingB.organisation2.mothercompany.co.uk.

4) Our forest is currently called
buildingA.organisation1.mothercompany.co.uk. The new building will be
housing a separate organisation. When we designed the domain we planned
for new buildings but not new oranisatons under our control.


The main questions are:

Would two separate Domains with Exchange run properly on the same
physical network?
-Then could I join the sites to share services?

Would it be best to have distinct networks and domains and link them in
some way?

Is there some other way of organising this??







.

Relevant Pages

  • Re: BBC Resources Question
    ... They wanted separate go and return paths so they could hear their country's sound and talk back to them. ... Officially this required bridges etc but lazyengineers would do it by hissing down the line from a telephone and adjusting the networks to get the least back in the earpiece. ... A contact in BBC News tells me that they are even considering doing live reports via Internet telephony. ...
    (uk.tech.broadcast)
  • Re: Wireless + Wired LAN?
    ... In that case, there would be two entries in the laptops routing table for the same subnet, so Windows will load-balance across the two routes, sending some traffic via the wireless and some via the LAN. ... If it's all one big network, ie you have your laptop plugged in to a wireless router, and also setup on the wifi, then you'll likely encounter problems because again both interfaces will be on the same subnet, here at least though it doesn't matter which is used as they both go to the same place. ... So, in short, unless both networks are separate physically and/or at least separate subnets then only have one enabled at a time. ...
    (alt.sys.pc-clone.dell)
  • Re: VoIP VLAN across router-router link?
    ... You can move the fiber connections to the 3750, have the networks ... allowed to pass across the routers between the two networks. ... fact two separate organizations on the data network side of things... ... the data networks must remain strictly separated except for the limited ...
    (comp.dcom.sys.cisco)
  • Multi-subnet networks
    ... I have two separate networks, each with their own separate internet ... connections and gateways. ... Shared resources from either subnet are available on both subnets. ...
    (comp.sys.ibm.pc.hardware.networking)
  • Re: Advice on site topology
    ... Another way to do it would be to create a new forest and migrate ... If you need two separate domains or forests, ... high speed network is that you can locate servers for all users in either ... Would it be best to have distinct networks and domains and link them in ...
    (microsoft.public.windows.server.active_directory)
Loading