Re: Exch 5.5 Migration to Exch 2003 (1 domain)

From: Steven Halsey [MSFT] (Stevhal_at_Online.Microsoft.com)
Date: 05/26/04


Date: Wed, 26 May 2004 14:45:43 -0700

Question 1:
Both Scenarios should be supported.
So long as your domain is Native Windows, then follow the Deployment tools.
Looks like you have the Windows Domain working, so adding the new Exchange
2003 server, and start moving your data over.
Whether you move forward with the Windows DC to W2k3 now or leave it W2k, I
don't think will make that big a difference on your migration.

Question 2:
Run the Deployment tools on the server 2. Just remember that DCDiag, will
give some errors when run on the member server rather than the DC, I believe
the Deployment Tools gives instructions on which errors/tests to worry
about.

Question 3:
So long as the Exchange 5.5 Server is up and running when the outlook logs
on once the profiles should get redirected to the new server automagically.
But the outlook client does need to contact the old 5.5 server to get
redirected to the new server.

Question 4:
Not exactly sure, but I suspect it will continue to work. The advantage of
doing an intra-org migration is most of the data stays the same. So the
Public Folders even though they exist on another server, maintain the same
address information. This means most Outlook rules continue to fire as
before, so I think it will work.

-- 
Steven Halsey
Stevhal@online.microsoft.com
Microsoft Exchange
Please do not send email directly to this alias.  This alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Patrick" <pdunphy@neo.rr.com> wrote in message 
news:zP2tc.8667$dn1.358@fe2.columbus.rr.com...
> Greetings:
>
> I have been looking through many threads to find the answers to all my
> questions but have not found answers to all of them.  Therefore, I will 
> post
> this new thread in hopes that my specific setup can be addressed.
>
> I currently have the following servers in my organization with one domain:
>
> Server 1 - Win 2K (SP4) AD (Domain controller)
> Server 2 - Win NT 4.0 (SP6a) (MS Exchange 5.5)
> Server 3 - Win NT 4.0 (SP6a) (Faxing Service software)
>
>
> After my upgrade my organization will look like one of these two 
> Scenarios:
>
> Scenario 1
> Server 1 - Win 2K (SP4) AD (Domain controller)
> Server 2 - Win 2003 (SP1) AD (MS Exchange 2003) (New Hardware)
> Server 3 - Win NT 4.0 (SP6a) (Faxing Service software)
>
> Scenario 2
> Server 1 - Win 2003 (SP1) AD (Domain controller)
> Server 2 - Win 2003 (SP1) AD (MS Exchange 2003) (New Hardware)
> Server 3 - Win NT 4.0 (SP6a) (Faxing Service software)
>
>
> Question 1
> Is one of these two scenarios (not) do-able?
> Recommendations?
>
> Question 2:
> When I run the ExDeploy tools, do I run them on Server 1 or Server 2?
> Of course if I run them on server 2 it would be after I install Win Server
> 2003.
>
> Question 3:
> Once I have Exchange 2003 installed and have moved my mailboxes and public
> folders to the new server, will I have to create new profiles in Outlook 
> on
> my users PC's?  I have read in places that I will not but, does that mean
> that Outlook will automatically change the exchange server name from the 
> old
> name to the new server name in the Outlook profile configuration when the
> users open Outlook for the first time?
>
> Question 4:
> I have, in users' outlook profiles, copies of Public folder Contacts in
> their Public folder Favorites.  This means when the main Public folders
> Contacts are updated the copies (Favorites) are automatically updated.
> These favorites are listed in each users profile address search list and 
> are
> available when the user is off-line.  Will these contacts become
> disconnected when the Public folders are moved from 5.5 to 2003?  In other
> words, will I have to re-select the address lists in each users profile to
> point to the favorites again? I hope I have described this clearly.
>
> Thanks very much,
>
> Pat
>
> 


Relevant Pages

  • Re: RPC over HTTP...
    ... RPC over HTTPs can only be used for Outlook 2003 or 2007. ... Exchange MVP 2007 ... scenarios seem to be for front end/back end servers. ... I have one exchange server. ...
    (microsoft.public.exchange.admin)
  • Re: Single user issue; best troubleshooting
    ... COULD be cause by that intermediate 'network access' server ... you do know there is significant logging in Outlook ... form of Integrated Authentication and so all of the OUTLOOK ...
    (microsoft.public.windows.server.active_directory)
  • Re: How to allow POP3 SSL connections w ISA 2004
    ... the Outlook group as well. ... Firewall Client configuration for ISA Server 2004. ...
    (microsoft.public.windows.server.sbs)
  • RE: login and email problems
    ... To the Outlook issue, ... Run "ipconfig /registerdns" command to register the DNS server. ... Ensure that you have an Outlook profile configured for the server ... profile is not associated with a Microsoft Exchange Server e-mail account. ...
    (microsoft.public.windows.server.sbs)
  • Re: Single user issue; best troubleshooting
    ... The user in this case is logging in to Outlook 2003 ... You still haven't indicated which EMAIL SERVER is used. ... Most email servers other than Exchange will not be using any ... Remote Desktops don't typically use INTEGRATED authentication ...
    (microsoft.public.windows.server.active_directory)