Moving exchange 2007 to a new server
Dear Experts,
As part of a large project, I am tasked with moving exchange services to a new server in a VMware environment. It currently resides on an ageing physical box, but its in a healthy condition. To give you an idea of what's currently in place (all physical servers):
DC - windows 2008 server (File shares, print server, DNS, AD, DHCP)
Exchange server 2007 (also a DC) - windows 2008 server (DNS, AD, DHCP)
SQL server - windows server 2008
Remote desktop server - Windows 2008
All will be migrated over (not P2V'd) to newly built VMs on a VMWare physical host. All VM servers will be windows server 2008R2 where the old servers are 2008.
It is my intention for the new exchange 2007 server to be a member server this time - no AD. I've performed a few exchange migrations in the past - most of them from SBS to SBS or SBS to separate servers. I'm OK with the migration of exchange to another box.
However in this case, given the overall project tasks required, I'm conscious that I will be updating the schema of AD to 2008 R2 and as the existing exchange server is a DC, there may be some compatibility issues. I know that exchange 2007 SP3 is compatible and fully supported in 2008R2 AD - its the order of things i want to get right.
To get around the potential issues, I was planning on doing the following:
- create a new 2008R2 VM and join it to the existing domain as a member server (no AD this time)
- install exchange server 2007 on to it
- migrate all exchange services and mailboxes
- uninstall the old exchange server and demote it
- create another new 2008R2 VM and dcpromo that, thus updating the AD schema.
- carry on with migrating the other servers and services.
Would this approach be sensible or do you have any other suggestions?
Many thanks in advance.
As part of a large project, I am tasked with moving exchange services to a new server in a VMware environment. It currently resides on an ageing physical box, but its in a healthy condition. To give you an idea of what's currently in place (all physical servers):
DC - windows 2008 server (File shares, print server, DNS, AD, DHCP)
Exchange server 2007 (also a DC) - windows 2008 server (DNS, AD, DHCP)
SQL server - windows server 2008
Remote desktop server - Windows 2008
All will be migrated over (not P2V'd) to newly built VMs on a VMWare physical host. All VM servers will be windows server 2008R2 where the old servers are 2008.
It is my intention for the new exchange 2007 server to be a member server this time - no AD. I've performed a few exchange migrations in the past - most of them from SBS to SBS or SBS to separate servers. I'm OK with the migration of exchange to another box.
However in this case, given the overall project tasks required, I'm conscious that I will be updating the schema of AD to 2008 R2 and as the existing exchange server is a DC, there may be some compatibility issues. I know that exchange 2007 SP3 is compatible and fully supported in 2008R2 AD - its the order of things i want to get right.
To get around the potential issues, I was planning on doing the following:
- create a new 2008R2 VM and join it to the existing domain as a member server (no AD this time)
- install exchange server 2007 on to it
- migrate all exchange services and mailboxes
- uninstall the old exchange server and demote it
- create another new 2008R2 VM and dcpromo that, thus updating the AD schema.
- carry on with migrating the other servers and services.
Would this approach be sensible or do you have any other suggestions?
Many thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Split points awarded. Sembee answered my original question and Will made some great suggestions on the order of tasks.