Zenith63
asked on
Exchange 2000 -> Exchange 2007 problems with Windows 2000
Hi,
I'm trying to transition from Exchange 2000 server running on a Windows 2000 SP4 Domain Controller (also a Global Catalog) to Exchange 2007 running on a Windows 2003 x64 SP2 member server. Exchange 2000 is in native mode, AD Domain is in 2000 native mode. There are two other Windows 2003 SP2 servers in the domain acting as Domain Controllers and GCs.
When I was installing Exchange 2007 I got errors about the Win2000 DC not being the right version (2003 SP1 required), but using the -DomainController switch with Setup got around this and Exchange 2007 is now installed and functional.
However when I try to move mailboxes from Exch2000 to the Exch2007 server I again get the error -
Domain Controller 'exch2000.mydomain.local' Operating System version is 5.0 (2195) Service Pack 4. The minimum version required is 5.2 (3790) Service Pack 1.
Using the -DomainController switch with the Move-Mailbox command does not solve it. I've set the StaticDomainControllers, StaticConfigDomainControll
So what are my options? I can't move my mailboxes to the 2007 box because this doesn't work. I can't stop the Win2000 box being a GC or DC because this breaks Exchange 2000. Telling Exch2007 to use specific DCs doesn't appear to work correctly.
The only things I can think of are -
- Remove Exchange 2007, make this server a DC and GC, then reinstall Exchange 2007. Exchange 2007 should then use the server it is on as the DC/GC, though nothing is guaranteed I suspect.
- Build a member server, stick Exchange 2000/2003 on this, move everything off the old Exch2000 server to this one, remove the old Exchange 2000 server, then move the mailboxes from this new 2000/2003 server to the 2007 server. Fairly labour intensive!
- Give up on email and go back to Post-It notes.
Any ideas appreciated.
I'm trying to transition from Exchange 2000 server running on a Windows 2000 SP4 Domain Controller (also a Global Catalog) to Exchange 2007 running on a Windows 2003 x64 SP2 member server. Exchange 2000 is in native mode, AD Domain is in 2000 native mode. There are two other Windows 2003 SP2 servers in the domain acting as Domain Controllers and GCs.
When I was installing Exchange 2007 I got errors about the Win2000 DC not being the right version (2003 SP1 required), but using the -DomainController switch with Setup got around this and Exchange 2007 is now installed and functional.
However when I try to move mailboxes from Exch2000 to the Exch2007 server I again get the error -
Domain Controller 'exch2000.mydomain.local' Operating System version is 5.0 (2195) Service Pack 4. The minimum version required is 5.2 (3790) Service Pack 1.
Using the -DomainController switch with the Move-Mailbox command does not solve it. I've set the StaticDomainControllers, StaticConfigDomainControll
So what are my options? I can't move my mailboxes to the 2007 box because this doesn't work. I can't stop the Win2000 box being a GC or DC because this breaks Exchange 2000. Telling Exch2007 to use specific DCs doesn't appear to work correctly.
The only things I can think of are -
- Remove Exchange 2007, make this server a DC and GC, then reinstall Exchange 2007. Exchange 2007 should then use the server it is on as the DC/GC, though nothing is guaranteed I suspect.
- Build a member server, stick Exchange 2000/2003 on this, move everything off the old Exch2000 server to this one, remove the old Exchange 2000 server, then move the mailboxes from this new 2000/2003 server to the 2007 server. Fairly labour intensive!
- Give up on email and go back to Post-It notes.
Any ideas appreciated.
ASKER
I've done standard transitions to 2007, it's this specific problem with a 2000 DC/GC that I'm having issue with. Reckon I'm going to have to build a member server and go to Exch2003 on that first...
I guess u r right. This should be a problem with 2000 DC/GC
Are you getting errors on your Hub Transport service in the event log? On some of my upgrades I have noticed that the Hub Transport service starts with Windows 2k creds instead of something with Exchange admin rights (like the local admin or something)
Also - you have to have a 2003 DC for Exchange 2k7. You can promote the server while still leaving the 2K box a DC/GC. You dont have to promote the domain level to 2003 native yet.
ASKER
I'll check for the logs tomorrow, but other then not being able to move mailboxes it seems like Exchange 2007 is working perfectly.
I have two other Windows 2003 R2 SP2 server that are DCs and GCs in the domain. The x64 server that I have put Exch2007 on is only a member server. Is this what you are asking?
I think the problem is the Exch2007 server contacts the Exch2000 box to do the mailbox move and then continues to contact it for DC/GC stuff during the move. There is a -DomainController switch to the Move-Mailbox command but it clearly doesn't do what I'd expect.
I have a virtual server or Windows 2003, think I'll run that from a server there tomorrow, install Exch2003 and move the mailboxes to it, then from there to the Exch2007 server. Stupid that I should have to do this, but I guess it's one more reason NOT to put Exchange on a Domain Controller!
I have two other Windows 2003 R2 SP2 server that are DCs and GCs in the domain. The x64 server that I have put Exch2007 on is only a member server. Is this what you are asking?
I think the problem is the Exch2007 server contacts the Exch2000 box to do the mailbox move and then continues to contact it for DC/GC stuff during the move. There is a -DomainController switch to the Move-Mailbox command but it clearly doesn't do what I'd expect.
I have a virtual server or Windows 2003, think I'll run that from a server there tomorrow, install Exch2003 and move the mailboxes to it, then from there to the Exch2007 server. Stupid that I should have to do this, but I guess it's one more reason NOT to put Exchange on a Domain Controller!
i dont see how moving to ex2k3 will help. Do you have routing group connectors created? You will need that for moving mailboxes as well.
You are right about the DC setup - i didnt see where you did have existing 2003 DCs. Who holds the FSMO roles?
You are right about the DC setup - i didnt see where you did have existing 2003 DCs. Who holds the FSMO roles?
ASKER
One of the 2003 servers holds the FSMO roles.
If I build a server, install Win2003 and Exch2003 on it, move mailboxes etc to it., remove Exch2000 then demote the Win2000 box I'll no longer have the problem of Exch2007 not liking 2000 DC/GCs, it's just one extra step that I was hoping to avoid. It's not Exch2003 that is going to sort the problem, it's getting rid of that Win2000 DC.
Yeah the routing group connectors are setup, but the problem is nothing like that really. The Move-Mailbox cmdlet checks the DC it is using to make sure it's the right version so fails straightaway when it notices Win2000. If I could force the Move-Mailbox tool to use the DC I want I'd be sorted.
If I build a server, install Win2003 and Exch2003 on it, move mailboxes etc to it., remove Exch2000 then demote the Win2000 box I'll no longer have the problem of Exch2007 not liking 2000 DC/GCs, it's just one extra step that I was hoping to avoid. It's not Exch2003 that is going to sort the problem, it's getting rid of that Win2000 DC.
Yeah the routing group connectors are setup, but the problem is nothing like that really. The Move-Mailbox cmdlet checks the DC it is using to make sure it's the right version so fails straightaway when it notices Win2000. If I could force the Move-Mailbox tool to use the DC I want I'd be sorted.
I have done 4 migrations for clients from ex2k to ex2k7 with no DC issues. All were using Win2k only DCs.
Here is the only thing different I have done - you said you are in 2000 native? Why? You should be in 2003 mixed-mode. If you have FSMO roles on a 2k3 box - upgrade the funtionality to 2003 mixed mode. Your ex2k org will still function just fine.
Here is the only thing different I have done - you said you are in 2000 native? Why? You should be in 2003 mixed-mode. If you have FSMO roles on a 2k3 box - upgrade the funtionality to 2003 mixed mode. Your ex2k org will still function just fine.
to clarify - i did have to introduce a 2k3 DC before building - but just saying that they were a 2k shop before migrating to ex2k7.
ASKER
I had some hope there, but alas there is no such thing as Windows 2003 Mixed mode. There's Windows 2003 Native and Windows 2003 Interim. Interim only supports W2k3 and NT DCs, 2000 DCs are not supported.
I've put Exchange 2003 on a virtual server and am moving to that now, then I'll dump the 2000 box and go to 2007...
Thanks for the suggestions anyway.
I've put Exchange 2003 on a virtual server and am moving to that now, then I'll dump the 2000 box and go to 2007...
Thanks for the suggestions anyway.
sorry about that - i think i was thinking about exchange but talking about domains. apologies. let me know how the swing goes. it is interesting that the 2000 box is causing that much trouble.
ASKER
I'm still in the process of doing that move, but I started another one on Friday. It was from Exch5.5 on a Win2000 DC to Exch 2007. I moved from Exch5.5 to Exch2003 on a Win2003 DC (just running as a virtual server) and then installed Exch2007. The Exch2007 GUI install wouldn't run because there was still a Win2000 DC in the domain, but using the -DomainContoller switch with setup.com got it installed. In this case the Move-Mailbox cmdlet of Exch2007 works fine even though there is a Win2000 DC in the domain! The difference here I guess is that there is no Win2000 DC with Exchange on it. Bit hit-and-miss for my liking, but at least I know for future reference...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No there were no errors from dcdiag. Everything "seemed" to be perfect, I suspect this is just a quirk in Exchange 2007 that will hopefully be resolved for SP1. Both moves are done now though that's all the matters!
ASKER
Thanks for talking it through with me and helping me to the final solution...
Actually, I ran across this exact problem a couple of days ago. You do have to remove the GC role from the Exchange 2000 server. The problem that Exchange 2000 has with this, is that it only builds the domain paths upon install, so you have to go manually in to the server properties in ESM and point it to the new 2003 DC/GC roles.
That would have fixed the problem with install and with the Exchange 2000 breaking.
Thanks for the points!
That would have fixed the problem with install and with the Exchange 2000 breaking.
Thanks for the points!
ASKER
Ah OK. I knew there was a problem removing the GC role from an Exchange 2000 server so I didn't try that. Hopefully there won't be a next time, but if there is I'll keep it in mind. Thanks.
Following docs helped in successfully migration.
http://technet.microsoft.com/en-us/library/bb124008.aspx
http://www.msexchange.org/tutorials/Transitioning-Exchange-2000-2003-Exchange-Server-2007-Part3.html