|
|
|
date: Mon, 21 Apr 2008 10:57:01 -0700,
group: microsoft.public.exchange.design
back
Re: Exchange Consolidation/Design Help
You've asked what I call a "consulting engagement question", a question so
complicated or requiring so many follow-up data-collection questions from us
that we can't possibly give you the depth of information the issue deserves.
You really ought to hire a consultant to work this project through with you,
and/or pick up Tony Redmond's and Jim McBee's books and start reading.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
"TI" wrote in message
news:1E5C5F83-3E05-4C77-ACA6-CE4F92D57D11@microsoft.com...
> Hi,
> I'm requesting some input on how best to consolidate 3 separate divisions
> of
> a company into 1 Exchange 2003 Server. All 3 divisions currently have
> their
> own Windows Domain and there is no connection between locations.
>
> The business requirement is for all users to have a common SMTP email
> domain.
>
> Here is the current layout:
> Boston - Exchange 2003 Server, Active Directory 2003, 50 Users
> Providence - Exchange 2000 Server, Active Directory 2000, 20 Users
> Salem - Exchange 2003, Active Directory 2003, 20 Users
>
> We are installing a new Exchange 2003 Server in Boston to replace the
> current server and to add the Providence and Salem users. We are
> installing
> Point to Point T1's between Boston-Providence and Boston-Salem for email
> (future use may include Terminal Server applications).
>
> Our internal debate revolves around whether or not the 3 different domains
> should be consolidated under one domain or not.
>
> Any input regarding possible implementations would be appreciated!
>
> Thanks
date: Mon, 21 Apr 2008 22:41:51 -0400
author: Ed Crowley [MVP]
Re: Exchange Consolidation/Design Help
Thanks Ed...I understand that there are many questions to be answered and we
have done a fair amount of research. From what we've read it appears that
our best option is either "Using a Dedicated Exchange Forest" (from Technet)
or implementing "RPC Over HTTP".
Would you be able to comment on those options or is it just too little
information on which to comment?
In any event, thanks for your help!
"Ed Crowley [MVP]" wrote:
> You've asked what I call a "consulting engagement question", a question so
> complicated or requiring so many follow-up data-collection questions from us
> that we can't possibly give you the depth of information the issue deserves.
> You really ought to hire a consultant to work this project through with you,
> and/or pick up Tony Redmond's and Jim McBee's books and start reading.
> --
> Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
>
> "TI" wrote in message
> news:1E5C5F83-3E05-4C77-ACA6-CE4F92D57D11@microsoft.com...
> > Hi,
> > I'm requesting some input on how best to consolidate 3 separate divisions
> > of
> > a company into 1 Exchange 2003 Server. All 3 divisions currently have
> > their
> > own Windows Domain and there is no connection between locations.
> >
> > The business requirement is for all users to have a common SMTP email
> > domain.
> >
> > Here is the current layout:
> > Boston - Exchange 2003 Server, Active Directory 2003, 50 Users
> > Providence - Exchange 2000 Server, Active Directory 2000, 20 Users
> > Salem - Exchange 2003, Active Directory 2003, 20 Users
> >
> > We are installing a new Exchange 2003 Server in Boston to replace the
> > current server and to add the Providence and Salem users. We are
> > installing
> > Point to Point T1's between Boston-Providence and Boston-Salem for email
> > (future use may include Terminal Server applications).
> >
> > Our internal debate revolves around whether or not the 3 different domains
> > should be consolidated under one domain or not.
> >
> > Any input regarding possible implementations would be appreciated!
> >
> > Thanks
>
>
>
date: Tue, 22 Apr 2008 06:26:00 -0700
author: TI
|
|
