Re: Exchange 2003 upgrade...
- From: Rick Boza <rickb@xxxxxxxxxxx>
- To: Exchange List <exchangelist@xxxxxxxxxxxxx>
- Date: Mon, 29 Nov 2004 14:42:36 -0500
Well, I¹m not sure exactly what you hope to buy by putting in the front end
server so far out to your migration it shouldn¹t hurt anything, but
there¹s no good reason for it that I can see from what you¹ve mentioned,
unless you just want a chance to poke around with it.
Having said that, you seem to have the order a bit off it sounds like you
want to put in the server before an ADC.
Actually you want the ADC in place before you install your first Exchange
2003 box.
How many DC¹s do you have, that you¹re worried about the schema extension?
If you just want to be sure replication will happen, I¹d go collect a bunch
of DCDIAGS and FRSDiags to make sure things are running smoothly before
running the PREPs. If everything is healthy then there shouldn¹t be any
issue; if not, you definitely want to be sure you get that fixed first.
Same thing for your 5.5 environment¹s Directory Service be sure that is
clean before you put in the ADC.
>>Is this a step that you would do a month in advance of migrating Public
Folders and Mailboxes?
Well, you can really do it anytime I suppose, but there¹s no real reason to
do so way out in advance.
>>Will having this FE server interrupt any current 5.5 operations?
It should have no effect whatsoever, assuming the 5.5 environment is in good
health
>>Will I have to create an ADC from the FE server to my Exchange 5.5 servers?
Assuming you want to migrate and not replace (meaning, carry forward the 5.5
Org rather than simply build a brand new thing from scratch) then you will
need an ADC. The ADC should be the second thing you put in (following the
PREPs) and will run on a Win2K3 server does not need to be an Exchange
server necessarily. You¹ll then probably want to have Connection Agreements
between your DC and one Ex5.5 server in each of your Exchange sites. This
is so you can switch your management of the Exchange mailboxes over to AD
and pass changes to each site as necessary.
>>Basically, I would not publish the MX record until we are ready to begin
migrating Mailboxes to Back End servers to ensure the new FE server is not used.
Just to clarify the MX record will be used for mail delivery, not Front
End Back End purposes. Or do you mean a bridgehead server when you say
Front End server? If it¹s your external facing mail relay host, that still
shouldn¹t matter to your Ex5.5 org, but you might (and probably should)
consider simply using a Windows server with SMTP running rather than a full
blown Exchange box.
Anyhow, my brief thoughts on the matter hope that helps a little!
Rick
On 11/29/04 2:27 PM, "Chris Wall" <Chris.Wall@xxxxxxxxxxxxxxxxxxx> wrote:
> http://www.MSExchange.org/
> Hello all,
>
> We have recently upgraded our NT 4 domain to 2003 AD and now it is time to
> upgrade Exchange 5.5...
>
> I am reading many deployment guides, white papers, etc. As such, I would
> like to install an Exchange 2003 Front End server as an initial step. This
> would accomplish two things for me.
>
> 1. It would extend the schema prior to sending out other DC's to remote
> locations. This will ease the burden of initial replication of the new DC's
> 2. Have this server in place along with our existing 5.5 organization for when
> we do begin migrating mailboxes in about a month.
>
> Is this a step that you would do a month in advance of migrating Public
> Folders and Mailboxes?
> Will having this FE server interrupt any current 5.5 operations?
> Will I have to create an ADC from the FE server to my Exchange 5.5 servers?
>
> Basically, I would not publish the MX record until we are ready to begin
> migrating Mailboxes to Back End servers to ensure the new FE server is not
> used.
>
>
> Thanks for your replies.
>
> Regards,
>
>
> Chris Wall
> Sr. Exchange Administrator
> MCSE, MCSA
>
> Global Knowledge Network
> 9000 Regency Parkway
> Cary, NC 27511
> w - 919.460.3236
>
Other related posts:
