Ok I need some help here the sooner the better. I have a test lab setup up with a copy of my live server. In my test lab I have Windows 2000 Server with SP4 with Exchange 2000 SP 3 this server has a copy of my live system. It is a Domain Controller the FQDN for example is mail.fesi.com. I have a new server which has 2003 Server 64Bit installed with SP1 nothing else has been installed on it. I have it plug into a hub along with my old server as well so I want to move the mailbox's off the exchange 2000 server to my new server. I have the Exchange server set to Native Mode but when I run the Exchange 2007 install I never get prompt browse to my old server to set a routing group. So what steps do I need to do to get the my mailbox's off the old server to my new server??? I would appreciate any help here due to our live server is needing to be replaced so the sooner I can get this to work in my test lad the sooner I can do this on the live server to get on the new server with the new Exchange 2007.
You will need at least one Windows Server 2003 SP1 (or higher) domain controller in the domain.
You will not need to select a routing group when you install Exchange 2007 since it creates its own AG and RG as 2007 phases out use of both the AG and RG. If you have more than one server you should also disable link state routing.
Once you get Exchange 2007 install you need to use the move-mailbox wizard to move the mailboxes, you will also need to create replicas of all the public folders on a Exchange 2007 computer.
How far have you gotten in the process?
- Joel
1st thanks for the response! Well right now I have 2003 Server installed on my new server it is not a domain controller. The copy of my live system is Windows 2000 SP4 with Exchange 2000 SP3 it is a Domain Controller.My new server is just called E-mail with 2003 Server SP1 installed so your saying I need to make it a Domain Controller?? My 2000 Server with Exchange 2000 is called for example mail.fesi.com and I want to make sure if I set my new 2003 server up as a domain controller. That when I do get my mailbox's moved from my old server that I do not half to change my users email address. So right now just have 2003 server loaded on my new server which is hooked up to a hub along with a copy of my live system withe Exchange 2000. I have not made my 2003 server a domain controller yet.
In order to install Exchange Server 2007 you do need at least one Windows Server 2003 SP1 DC. Once making it a DC I would make it a GC and move at least the schema master over to the 2003 DC.
Then you should be able to start the Exchange Server installation which will extend the schema and apply the new permissions.
After that you can then test mail routing with a test mailbox, and then once satisfied move the users and public folders over.
Ok so sounds like I will half to make my new 2003 server a domain controller. Ok if I make my new 2003 server a domain controller and lets say I call it fesi1 and my 2000 Server with Exchange 2000 is a Domain Controller and it is fesi. Will I be able to change the Domain Name which will be the Domain Controller name back to fesi. Due to I want to make sure that my users do not half to change their E-mail address. Also once I make my new 2003 server a DC you said make it a GC which is a Global Catalog is there a way to make sure it's is a GC?? Now once my new 2003 server is a DC and I make it a GC you said move the Schema Master over to the 2003 DC. What are the steps to move the Schema Master over to the new 2003 DC? Once this is done you said start with the Exchange 2007 install now during the install at some point it should prompt for a routing group or routing mail and at this point it should see my old exchange 2000 server.
You won't be able to change the name of the server once you make it a domain controller, when you run dcpromo you will just add the new server to the same domain you have now. Before you can run dcpromo on the new server to make it a domain controller for your domain you will need to run "adprep /forestprep" and "adprep /domainprep" from your Windows Server 2003 installation disk. This will extend the schema of the domain to allow Windows Server 2003 servers to be added to the domain.
Here is a step-by-step on making a server a GC: http://www.msresource.net/content/view/25/47/
Here are a couple articles on moving the schema master (and other FSMO roles) http://support.microsoft.com/kb/324801 and http://www.petri.co.il/transferring_fsmo_roles.htm
Since Exchange 2007 will be installed in the same domain there will be no need to change the users' email addresses, or reconfigure their clients when you move their mailboxes between the Exchange 2000 and Exchange 2007 servers, as Exchange takes care of both of those. In order to have the clients reconfigure however the old Exchange server will still need to be operational until all of the clients have been redirected to the new server.
What is the steps to run the adprep /forestprep" and "adprep /domainprep"?? When I run the adprep/forestprep from the 2003 Server CD on the 2003 server it says adprep can not run on this platform because it is not a domain contorller. So sounds like I half to make my new 2003 Server a Domain Controller before it will let me run this on my 2003 server?? Do I need to run adprep/domainprep on my old 2000 server which is a Domain Controller with Exhcange instead of doing this on my new 2003 server which is not yet a domain controller??
You need to put the Server 2003 CD in the 2000 server and run ADPREP from it. (or copy the adprep files to the 2000 server)
Also before running adprep from the server you should look at this article to make sure you have the correct hotfixes installed. http://support.microsoft.com/?kbid=331161
Hmm ok well when I run the ADPREP from the 2003 Server 64bit CD on the Windows 2000 Server it says this is not a valid Win32 Application.
Do you have a copy of Windows Server 2003 32-bit version you can use?
Yeah think so I will try that.
Ok ran that but not it is saying that there is a Schema Conflict with Exchange 2000.
In order to get past that problem, you'd want to follow scenario 2 in this article:
http://support.microsoft.com/kb/314649
I will give that a try today let you know what happens.
Ok on Scenario 2 I'm at this part.
a. I created a folder called systemrootiop.
b. I went to the command Prompt typed cd systemrootiop then enter
c. I extracted the Intorgpersonfix.ldf from the 2003 Server CD from the Support.cab file.
d. Is where I'm lost it says from the Console of the schema operations master load the Inetorgpersonfix.ldf file by using the Ldifde.exe to correct the LdapDishplayName.
Where do I go frome here??
So from the command prompt on your 2000 domain controller you would want to run:
ldifde -i -f inetorgpersonfix.ldf -v -c DC=X "dn path for forest root domain"
The dn path for my internal domain would be dc=exchangeexchange,dc=local
ldifde should be installed by default.
Ok back at it again I have a test lab set up with a copy of my live system with Exchange 2000 Sp3 with Windows 2000 Server Sp4.. The Windows 2000 server is a Domain Controller example name is mail.bud.com. The Windows 2000 Server is plug into a switch along with the New Server running Windows 2003 Server 64 Bit Sp1. The New server will be the new Exchange 2007 server right now the new server just has 2003 Server loaded on it nothing else and it is also plugged into the switch along with my old server.. 1st what us the best way to get my mailbox's moved over from my old server to the new server??
You first need a Windows Server 2003 SP1 or higher DC (with Schema master). You can use your new Exchange server for this. First, upgrade the new to Windows Server 2003 SP2 before starting anything. Then promote this new server to a DC and then a GC. Then move the schema master (and other FSMO roles) over to it. Once that is complete, demote the 2000 DC.
Next then you can start the install of Exchange Server 2007 SP1 (you can go straight to SP1 instead of installing RTM and then applying SP1)
After Exchange has been installed on the new server and you have tested everything to make sure it is working, you can use the move-mailbox task or cmdlet to move mailboxes from the Exchange 2000 server. When the users connect with Outlook the Exchange 2000 server will redirect the Outlook to the new server automatically, no manual changes are needed.
Ok so my new 2003 64bit Server I need to make it a Domain Controller? Now naming the 2003 Domain Controller I need to keep it close to my old 2000 server Domain controller name. Due to it is used as your e-mail address and I do not want to half to change users email address. After I make the 2003 Server a Domain Controller what is the best way to make it a GC? Then you said to move the Schema Master and other FSMO Roles over to it so what is the best way to do that?? Also before you can do that the old 2000 server must see the 2003 server correctly.. Again thanks for all of your input on this..
The name of the server doesn't matter at all as the domain name will be the same. The email address is set by the recipient policy which will not change because of the upgrade. No other special configuration is needed to make the servers "see" each other.