Re: Windows/Exchange server migration
From: Jaclynn Hiranaka [MSFT] (jaclynnh_at_online.microsoft.com)
Date: 04/05/04
- Previous message: anonymous_at_discussions.microsoft.com: "Exchange 2k3 to SBS 2k3"
- In reply to: Bodo: "Windows/Exchange server migration"
- Next in thread: Bodo: "Re: Windows/Exchange server migration"
- Reply: Bodo: "Re: Windows/Exchange server migration"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 5 Apr 2004 13:25:46 -0400
I would suggest against doing it this way.
First off all of your permissions will be lost. Secondly by exporting and
importing you are also losing single instance storage.
The best method is to install into the same org/site and then move
mailboxes, public and system folders, connectors, etc. to the new E2K3
server.
You can move to a new domain using ADMT in order to retain the GUIDs for
permissions.
-- Hope that helps. ------------------------- Jaclynn Hiranaka Enterprise Messaging Support This posting is provided "AS IS" with no warranties, and confers no rights. © 2003 Microsoft Corporation. All rights reserved. "Bodo" <anonymous@discussions.microsoft.com> wrote in message news:13a9d01c41757$11f3a3f0$a601280a@phx.gbl... > I will be migrating a small network of about 12 users from > Windows NT/Exchange 5.5 server to Windows 2003/Exchange > server 2003. I am thinking about setting up a new network > that is separate from the Windows NT network with a new > Exchange organization, then create the user accounts in > the new domain and then export and import the users > mailboxes into the new exchange organization. Is this the > best method and do you think there will be any problems? > > Thanks in advance
- Previous message: anonymous_at_discussions.microsoft.com: "Exchange 2k3 to SBS 2k3"
- In reply to: Bodo: "Windows/Exchange server migration"
- Next in thread: Bodo: "Re: Windows/Exchange server migration"
- Reply: Bodo: "Re: Windows/Exchange server migration"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
