Re: How to specify an exchange 2003 as remote bridgehead?

That's great hint.

We are also planning a year to go to Exchange 2007.
I think with an administrative group with only RGs, we
then can implement, design Hub, Edge transport easily without
confusion...etc.

Do you have any advice about Exchange 2007 Hub/Edge
design? Look like each of remote office, we should have
a Exch2007 Hub server and a dedicated Edge ..etc

Regards, thanks again for your advice!
JPTHSD



"Rich Matheisen [MVP]" <richnews@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:l749b35dhhl86jhv8od23f2kkm55oabp51@xxxxxxxxxx
"JPTHSD" <jpthsd@xxxxxxxxxxx> wrote:

You are right! in each of TW, Thailand administrative group, I moved
Exchange server to their own RG. So the server become master server in
there
(TW, Thailand)...this is what I'd like it to be, each of administrative
group has their own RG, and each of RG has a master server, we will
connect
RGs together by RG connector to link these RGs together?

That's the usual course of action. :-)

Now each of office like TW, Thailand has administrative group and an
exchange servers, they will have more exchange servers, but we will link
the 1st exchagne server from each administrative group location together
to
reduce the heavy bandwidth load ..etc..so on. Hmmm where do I create the
RG
connector? in each RG do i need to create SMTP connector or no?

In the Routing Groups container, in the Connectors container. If you
don't see the Routing Groups containers, select the organization
object and right-click it. From the "Properties" page, check the
"Display Routing Groups" check box.

You should start using "Routing Group" instead of "Administrative
Group" when you speak of message flow within your organization.
Although the default is to have a routing group container in each
administrative group, it's also possible to have an administrative
group that contains only routing groups and /NO/ servers. With that
configuration you can delegate control at the AG group for servers and
mailbox greation, but not give away control to local admins over the
way messages move within the organization.

--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.pott@xxxxxxxxxxxxx
Or to these, either: mailto:h.pott@xxxxxxxxxxxxxxx
mailto:melvin.mcphucknuckle@xxxxxxxxxxxxx
mailto:melvin.mcphucknuckle@xxxxxxxxxxxxxxx


.

Relevant Pages

  • Re: removing exchange 2003 objects once exchange 2007 is in place
    ... Was EXCHANGE\0ADEL your Ex 2003 server? ... Also for the first error did you move your public folder hiearchy? ... On your Exchange 2003 or Exchange 2000 server, ... Exchange 2000 administrative group to the Exchange 2007 administrative ...
    (microsoft.public.exchange.admin)
  • Re: Renaming an Administrative Group?
    ... The KB also says shows you how to bring the server back into a supported state, ... Although this change appears to be merely cosmetic there are dependencies on the Administrative Group name. ... Please do not send email directly to this alias. ... Administrative Group names in Exchange Server 2003 or in Exchange 2000 ...
    (microsoft.public.exchange.admin)
  • Re: Exchange 2007 email routing
    ... ExternallySecuredAsPartnerDomain: ... N=Exchange Administrative Group ... I am testing out Exchange 2007 Beta two. ... test AD forest on my LAN and joined the 2007 exchange server to the test ...
    (microsoft.public.exchange.admin)
  • RE: Why remove 5.5 server in mixed 2003/5.5 site prior to mbx migr
    ... > We can convert Exchange Org to Native Mode after decommissioning the old ... > server, then we can only use Mixed Mode for that Org. ... > o Routing groups can include servers from multiple administrative groups. ...
    (microsoft.public.exchange.setup)
  • Re: Unistall exchange 2003 in mixed enviornment
    ... If possible leave the Exchange box up and running. ... I want to uninstall exchange 2003 from the enviornment. ... If there are any mailboxes assigned to a storage group on a server, ... in a mixed administrative group that is running Site Replication Service ...
    (microsoft.public.exchange.admin)