Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Tue, 3 Jan 2006 10:32:05 -0800,    group: microsoft.public.exchange.design        back       


Join exisitng site or create new one?   
Hi,
We have a small subsidery company that is part of our larger company that 
just purchased their own exchange server. We would like to see all recepients 
in GAL from both company's. Should we have this new exchange 2K3 server join 
the exising site or create a new one? (There are approximately 200 users in 
parent co. and 25 in subsidery co. They are both MSX 2K3 - Parent is 
Enterprise and subsidery is Standard edition)

Another consideration is these two company's are connected via T-1.

Thanks,
Scott
date: Tue, 3 Jan 2006 10:32:05 -0800   author:   ScottMaine

Re: Join exisitng site or create new one?   
Exchange 5.5 used "Sites" as administrative & routing boundary. Exchange 
200x separates these into Routing Groups and Administrative Groups. The 
former is a message routing boundary, and the latter - as the name 
suggests - is administrative grouping.

If you want admins from subsidiary company to only be able to manage their 
own Exchange server, you can create a new Administrative Group (*before* you 
install Exchange on the new server) and install the server in the new AG.

As far as message routing is concerned, if you have more than one Exchange 
servers in your primary site and only want one (or more) bridgeheads to 
route messages to the subsidiary's Exchange server, you can place it in its 
own Routing Group and create Routing Group Connectors (both ways).

Regardless of which way you go, recipients on all servers in the Exchange 
Organization should be visible in GAL by default.
-- 
Bharat Suneja
MCSE, MCT
www.zenprise.com
blog: www.suneja.com/blog
-----------------------------------------


"ScottMaine"  wrote in message 
news:8EB4E2A5-F31C-4821-B9D7-6E022E117E78@microsoft.com...
> Hi,
> We have a small subsidery company that is part of our larger company that
> just purchased their own exchange server. We would like to see all 
> recepients
> in GAL from both company's. Should we have this new exchange 2K3 server 
> join
> the exising site or create a new one? (There are approximately 200 users 
> in
> parent co. and 25 in subsidery co. They are both MSX 2K3 - Parent is
> Enterprise and subsidery is Standard edition)
>
> Another consideration is these two company's are connected via T-1.
>
> Thanks,
> Scott
date: Tue, 3 Jan 2006 11:34:41 -0800   author:   Bharat Suneja

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us