Exchange 2007? Get those domain controllers upgraded!
Do you have to be running all W2K3 SP1 domain controllers in your organization before moving to Exchange 2007? No, only the DCs/GCs that will be used by E2K7 have to be W2K3 SP1 (though SP2 works just as well).
However, if the setup process finds a W2K DC/GC it will fail. And other processes (once you are in operation) such as Move-Mailbox will also fail. Here is another example:
Failed
Error: Domain Controller 'example.example.org' Operating System version is 5.0 (2195) Service Pack 4. The minimum version required is 5.2 (3790) Service Pack 1.
Exchange Management Shell command attempted:'28600b07-6d7c-4e94-9559-7861c88faa48' move-mailbox -TargetDatabase 'CN=Mailbox Database,CN=First Storage Group,CN=InformationStore,CN=EXAMPLE,CN=Servers,
CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=EXAMPLE,
CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=EXAMPLE,
DC=ORG'
Elapsed Time: 00:00:00
I am recommended as a prerequisite that people get their domain controllers upgraded to a minimum of W2K3 SP1 prior to starting their E2K7 migrations.
Labels: Exchange 2007
posted by Jim McBee @ 4:47 AM
2 comments
2 Comments:
Does the setup also checks for DC/GC's in other sites?
I'm working on a transition where there will be one Exchange 2007 server in the main site.
In the main site there won't be any W2000 DC/GC's anymore, but our in 5 of our remote sites there are still W2000 DC/GC's and will be at the time of installation.
We planned to migrate those after the Exchange transition, but if this also is true for sites we probably have to rethink that...
Hurray! I figured this out all by myself :-)
Well, with some help of MS website offcourse.
But to answer my question: yes, E12 checks for DC's in other sites, but for things like mailbox moves etc. it only needs a 2003sp1GC in his site. Best to phase out that 2000 GC, because it stil was used for mailbox moves.
When all was working fine (in the testlab), I still got MS Exchange ADAccess eventid 2116 every 15 minutes. It warns for domain controllers which do not match the requirements. Everything works, but it is annoying!
Using the Set-ExchangeServer cmdlet , i could pin the E2007 server to the DC's and GC's i want him to use. Now he doesn't even see the W2000 servers!
It is still best to upgrade, but it is not necessary and makes your upgrade plan more flexible.
Post a Comment
<< Home