Re: Migrating from 5.5 to 2003 - Connectors and DirRep

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Nick Ford (nicktf_at_hotmail.com)
Date: 08/26/04


Date: 26 Aug 2004 01:09:11 -0700

Thank you very much for this response, Steven, this was just the sort
of information I was after. I had to smile at your suggestion of
getting the whole company to collaborate together - after numerous
mergers, takeovers and joint ventures, I'm almost unsure of who I work
for on a day-to-day basis - we have a "company" that consists of
clumps of administrators zealously guarding their own personal
kingdoms - getting a text file transferred can be a major headache
these days! :-)

Cheers

Nick

"Steven Halsey [MSFT]" <Stevhal@Online.Microsoft.com> wrote in message news:<uwjFzkhiEHA.3548@TK2MSFTNGP09.phx.gbl>...
> What you have is a very complex problem ahead of you. There are several
> paths that you can take, but I would not recommend the one you indicated.
>
> The path I would not recommend is If you use the join method when installing
> your Windows 2003 server. This is a path that will cause problems for your
> dispersed management. You can't have 2 Exchange 2003 servers in the same
> 5.5 organizations existing in separate windows forests, it is an unsupported
> situation. If you go down the path you propose you are likely to end up in
> this situation. You will install a Windows Domain and Exchange 2003 and
> work with the existing Exchange 5.5 organization. Later someone else will
> do the same and suddently you have an unsupported situation.
>
>
> Here are some plans that might work better for you:
>
> The best situation would be to get a plan for the whole company to move
> forward on. For now that could be as simple as installing an Empty Windows
> Root domain that the other parts of your company could join. This would
> keep you as a single organization. As each island moved forward they would
> join the root domain as a new child domain. And install Exchange 2003 to
> join the existing infrastructure, keeping your Exchange 5.5 Organization and
> your Exchange 2003 organization as one entity in the new forest.
>
> If you wanted to keep the Windows permissions seperate (not joined domains)
> then you could do a similar process as the empty root domain, but actually
> create an Exchange Resource Forest. This forest would be dedicated to the
> Exchange organization across all the companies. You would create trusts to
> the various other domains, and you would create the mailboxes as resource
> mailboxes in the Exchange forest.
>
> The other way I would recommend is no to have your Exchange 2003 server join
> the 5.5 server. Rather install a new organization in your forest and
> Migrate the mailboxes to the new Organization. Use Exchange Active
> Directory Connector in Inter-Org mode to keep your new organization and the
> old 5.5 server in Sync. This way you still get the information about the
> whole 5.5 Organization without being in an unsupported situation. The
> biggest problem is later on you may have to migrate again to a consolidated
> organization or deploy a cross forest solution to synchronize the different
> organizations after the 5.5 servers are removed.
>
> --
> 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.
>
>
>



Relevant Pages

  • Re: Two diffeent Forest sharing 1 Exchange Server
    ... I would look into the Galy Sync and inter org connector option. ... The other option you have is to host ABC.com on the current Exchange server ... As far as setting up a separate forest I how can I setup current users ...
    (microsoft.public.exchange.design)
  • Merging two Forest and Exchange server
    ... Our branch officeis Windows NT 4.0 domain with exchange server 5.5 ... We want to remove the Forest at our HO and mergre it with BO Forest,as ...
    (microsoft.public.exchange.misc)
  • Update: Re: Exchange 5.5 to 2003, Multiple Forests, Other Questions
    ... The "Exchange Server 2003 Recipient Object Check ... (RecipientDSInteg)" came back and mentioned "RecipientDSInteg detected a ... > I see that I might need to first migrate the 2000 AD forest into the 2003 ...
    (microsoft.public.exchange.design)
  • Re: search for a guid
    ... have you removed the trust relationship to the old forest. ... > This has been an issue ever sincethe domain and exchagne server were ... > Exchange 2003 manually. ... >>> all attributes of the manuall uninstall were correctly removed. ...
    (microsoft.public.win2000.active_directory)
  • Re: Moving From Windows NT 4.0 to Windows 2003 Domain
    ... domain as well as forest are windows 2003) then you can create cross forest ... Install the new 2003 server into the network as a domain member server. ... Can anyone lead us in the right direction for moving from a Windows NT ... We also want to go from Exchange 5.5 to Exchange 2007 on a new server as ...
    (microsoft.public.windows.server.active_directory)