SBS 2003 - server 2008 and exchange 2010

Ok, here is a groovy issue,

The 2003 box is 32 bit.
I need to prepare the schema for exchange 2010.
It mentions I should use the setup.com /pl command
do I use the exchange 2010 cd for this? If so, i have a 32bit/64bit OS issue :(

Did this a couple of weekends ago. Didn't have any problems. Just make sure your DCdiag and Netdiag are clean before you start the migration.
 
I will be facing the same issue a bit later - need to upgrade us from 32-bit server2003 and exchange2003 to 64-bit exchange2010 and server2008 etc

:sick: not looking forward to it.

Also did this a couple of months ago. Just check the white papers is not 100% correct sometimes you have play around a bit.
 
Did this a couple of weekends ago. Didn't have any problems. Just make sure your DCdiag and Netdiag are clean before you start the migration.

I have no idea what that is, but i shall google it and find out.
thanks..

it seems it all gets updated / prepared during the exchange 2010 installation?
Am i right in saying this?
 
I have no idea what that is, but i shall google it and find out.
thanks..

it seems it all gets updated / prepared during the exchange 2010 installation?
Am i right in saying this?

Not really all you need to do is run those 2 commands separately they will run a bunch of tests and tell you if anything fails. Then you just google the error messages if any.

DCDiag = Domain Controller Diagnostics
Netdiag = Network Diagnostics
 
Got three servers in company called server01, server02 and server03.


I take it all you need to do is to set the 2008 server up as normally, then run DCPromo on it to make it the master DC. This machine will be called server04.

Then rename server01 to server05 (with a new IP), and rename server04 to server01 (with server01's IP)

Then install Exchange2010 once the servers have been renamed?

Am I correct in my assumptions?
 
Got three servers in company called server01, server02 and server03.


I take it all you need to do is to set the 2008 server up as normally, then run DCPromo on it to make it the master DC. This machine will be called server04.

Then rename server01 to server05 (with a new IP), and rename server04 to server01 (with server01's IP)

Then install Exchange2010 once the servers have been renamed?

Am I correct in my assumptions?

As far as I know but we don't usually change the server IP back to the old IP we just leave it as the new one, so just check on that.

Also Ms doesn't recommend running a DC on the same server as Exchange.
 
Not really all you need to do is run those 2 commands separately they will run a bunch of tests and tell you if anything fails. Then you just google the error messages if any.

DCDiag = Domain Controller Diagnostics
Netdiag = Network Diagnostics


Oooh, u should never have answered :)

ok, so i got exchange 2010 installed on a new box.
2003 pdc with exchange 2003 on the other.

Where to from here?
I mean, on the 2010 server i can move mailboxes etc from 2003 to 2010.
But how do i actually cut over all the roles the 2003 server is performing to the 2010?
 
Got three servers in company called server01, server02 and server03.


I take it all you need to do is to set the 2008 server up as normally, then run DCPromo on it to make it the master DC. This machine will be called server04.

Then rename server01 to server05 (with a new IP), and rename server04 to server01 (with server01's IP)

Then install Exchange2010 once the servers have been renamed?

Am I correct in my assumptions?

Nope, don't rename anything! This microsoft stuff is actually quite clever, amazingly. Once you install server04 and move the roles etc, it replicates all the changes down to the workstations. So lets say you migrated from 2003 server to 2008 and you moved all the FSMO roles, on any of the workstations, you just log out and log in. Open up Outlook and its amazingly looking for the new Exchange server. You might need to recreate one or two exchange profiles if it didn't replicate 100%, but so it goes. This goes even for mapped shares and roaming profiles, etc. You just need to ensure you have completed all the steps.
 
Oooh, u should never have answered :)

ok, so i got exchange 2010 installed on a new box.
2003 pdc with exchange 2003 on the other.

Where to from here?
I mean, on the 2010 server i can move mailboxes etc from 2003 to 2010.
But how do i actually cut over all the roles the 2003 server is performing to the 2010?

Short breakdown for what needs to happen:

1. Promoting a 2008 or 2003 server to a DC (installing DNS, DHCP, WINS,
etc).
2. Installing a separate server for Exchange into the org.
3. Move mailboxes
4. If using SQL, installing a separate server for SQL and move the databases
5. Move any other apps over
6. Unplug the SBS
7. Move FSMO roles over
8. Manually remove SBS' Exchange instance out of the org
 
Short breakdown for what needs to happen:

1. Promoting a 2008 or 2003 server to a DC (installing DNS, DHCP, WINS,
etc).
2. Installing a separate server for Exchange into the org.
3. Move mailboxes
4. If using SQL, installing a separate server for SQL and move the databases
5. Move any other apps over
6. Unplug the SBS
7. Move FSMO roles over
8. Manually remove SBS' Exchange instance out of the org

Perfect! You know your stuff.
 
Short breakdown for what needs to happen:

1. Promoting a 2008 or 2003 server to a DC (installing DNS, DHCP, WINS,
etc).
2. Installing a separate server for Exchange into the org.
3. Move mailboxes
4. If using SQL, installing a separate server for SQL and move the databases
5. Move any other apps over
6. Unplug the SBS
7. Move FSMO roles over
8. Manually remove SBS' Exchange instance out of the org

Ok sweet, doesnt sound too hard.
I actually had it a little wrong in the OP, its not an SBS 2003.
Its standard server 2003 with exchange on it, and now I have a second server with 2008 and exchange 2010.

What roles do I move over so that exchange 2010 is the guy being used and not 2003?
 
got a server I can diddledaddle on :cool:

Will try a dry run (and some other stuff) before doing the Real Thing™
 
Ok sweet, doesnt sound too hard.
I actually had it a little wrong in the OP, its not an SBS 2003.
Its standard server 2003 with exchange on it, and now I have a second server with 2008 and exchange 2010.

What roles do I move over so that exchange 2010 is the guy being used and not 2003?

Considering my 2008/2010 box will not be a DC, I assume i dont move any roles to it?
So again, my question is, how do I "transfer" exchange from 2003 to 2010? (including OWA and all that stuff?)
 
did a whole bunch of steps, moved mailboxes, uninstalled exchange 2003....
and mail still works!!! YAY!!!

I broke OWA though. fun times
 
Is the 2003 server still in place?

The 2003 server is still there, and still the PDC etc
2008 server is running exchange
I have removed exchange 2003

I get a cert issue when trying to logon to the OWA link, it then asks for credentials.
After that it bumps me straight back to the cert issue page.
If i select continue again, I get a webpage error
 
Last edited:
Nope, don't rename anything! This microsoft stuff is actually quite clever, amazingly. Once you install server04 and move the roles etc, it replicates all the changes down to the workstations. So lets say you migrated from 2003 server to 2008 and you moved all the FSMO roles, on any of the workstations, you just log out and log in. Open up Outlook and its amazingly looking for the new Exchange server. You might need to recreate one or two exchange profiles if it didn't replicate 100%, but so it goes. This goes even for mapped shares and roaming profiles, etc. You just need to ensure you have completed all the steps.

Short breakdown for what needs to happen:

1. Promoting a 2008 or 2003 server to a DC (installing DNS, DHCP, WINS,
etc).
2. Installing a separate server for Exchange into the org.
3. Move mailboxes
4. If using SQL, installing a separate server for SQL and move the databases
5. Move any other apps over
6. Unplug the SBS
7. Move FSMO roles over
8. Manually remove SBS' Exchange instance out of the org

Luckily no SQL stuff or SBS stuff.

So, to recap :

Install Server2008, join to domain as server.
Run DCPROMO, grab FSMO rules. Make sure it's the DC.
Install Exchange2010, migrate mailboxes (on same server)
-while on this subject, can the exchange information store be copied over (*.EDB and *.STM files)
-or do I have to use EXMERGE or other utilities?
Adjust the incoming port rule on the firewall to point to new mailserver IP
Log clients out, log in again
 
Ok, so i think my OWA problem has to do with owa still being pointed to the server 2003, and not the new exchange 2010 server.

How/where do these redirects take place?
 
The 2003 server is still there, and still the PDC etc
2008 server is running exchange
I have removed exchange 2003

I get a cert issue when trying to logon to the OWA link, it then asks for credentials.
After that it bumps me straight back to the cert issue page.
If i select continue again, I get a webpage error

Do you have a digicert? If not you would need to create a self signed cert if I'm correct from Ex 2007 it's required.

Luckily no SQL stuff or SBS stuff.

So, to recap :

Install Server2008, join to domain as server.
Run DCPROMO, grab FSMO rules. Make sure it's the DC.
Install Exchange2010, migrate mailboxes (on same server)
-while on this subject, can the exchange information store be copied over (*.EDB and *.STM files)
-or do I have to use EXMERGE or other utilities?
Adjust the incoming port rule on the firewall to point to new mailserver IP
Log clients out, log in again

There will be a move tab in the new exchange management console that you use to migrate the mailboxes.

How my previous install worked was that while the 2003 and 2010 servers were running at the same time mail was coming in via 2003 then transfered to 2010 via a routing connector. Only when you uninstall 2003 will mail starting coming in straight via the 2010 box.

Ok, so i think my OWA problem has to do with owa still being pointed to the server 2003, and not the new exchange 2010 server.

How/where do these redirects take place?

What happens if you try to access OWA via the internal server name something like https://localhost/owa?
 
Do you have a digicert? If not you would need to create a self signed cert if I'm correct from Ex 2007 it's required

What happens if you try to access OWA via the internal server name something like https://localhost/owa?

It still does the same thing sadly!
Tried re installing cas. No luck
 
Top
Sign up to the MyBroadband newsletter
X