daniel_smith
asked on
Have Exchange 2007 and adding a new Exchange 2007 server
Currently we have Exchange 2007 on Windows 2003. We have had some weird errors and microsoft will not support it because it is not on windows 2008 (we are running it on VMWARE).
So we decided to add a new Windows 2008 VM with Exchange 2007 and move all the mailboxes to the new server and shut the old (current) one off.
I have the new machine up and running, Exchange 2007 is installed and of course its sees all the mailboxes on the current Exchange.
Whats the steps to best move the mailboxes, distrubution list etc and what steps to remove the current Exchange once everythign is moved?
So we decided to add a new Windows 2008 VM with Exchange 2007 and move all the mailboxes to the new server and shut the old (current) one off.
I have the new machine up and running, Exchange 2007 is installed and of course its sees all the mailboxes on the current Exchange.
Whats the steps to best move the mailboxes, distrubution list etc and what steps to remove the current Exchange once everythign is moved?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can easily move mailboxes from EMC or by using PS. DL are stored in AD, i don't think u need to move them. Later remove the old Exchange server from ADD remove program.
Keep one safe backup for your old server. In case, you need it sometime.
Keep one safe backup for your old server. In case, you need it sometime.
ASKER
DL ?
distrubution list
ASKER
The items listed in my Distrubution Group, I dont see those in AD anywhere.
Where would they be?
Where would they be?
Search in AD with email address.
I assume servers are on same domain. If so then you need to check the expansion server of the DG, if it is the server that is to be removed, you need to change it, You do not get the option to move the DG, you can either disable or remove
ASKER
Yes they are on the same domain,
Expansion server is set to ANY server in organization.
Expansion server is set to ANY server in organization.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If it is set to Any, it will be taken care automatically. Follow the article mentioned by muzafar_13 from removing the server.
ASKER
On step 1) item a) about making a public folder database on the 2nd exchange.
I made it, however it fails when attempting to mount
This error is received:
I made it, however it fails when attempting to mount
This error is received:
--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
Failed to mount database 'Public Folder Database'.
Public Folder Database
Failed
Error:
Exchange is unable to mount the database that you specified. Specified database: C4EXCH\First Storage Group\Public Folder Database; Error code: MapiExceptionADNotFound: Unable to mount database. (hr=0x80004005, ec=2417)
.
--------------------------------------------------------
OK
--------------------------------------------------------
Check this
http://www.vware.at/?p=169
http://www.vware.at/?p=169
ASKER
ok you lost me on that at the
"Open ADSI Edit, connect to a Domain Controller, change the context to Configuration."
What is ADSI Edit? I dont have that.
"Open ADSI Edit, connect to a Domain Controller, change the context to Configuration."
What is ADSI Edit? I dont have that.
It is part of support tools in windows. Goto run and type adsiedit.msc
http://support.microsoft.com/kb/892777
It is like registry for AD. You need to be very careful. Whatever changes you are making here. One wrong step can lead to major issue. This tool is basically for very advance admins.
http://support.microsoft.com/kb/892777
It is like registry for AD. You need to be very careful. Whatever changes you are making here. One wrong step can lead to major issue. This tool is basically for very advance admins.
ASKER
so for admins that have never used that, what solution is there to fixing the error on mounting a public database. Did we do somethign wrong on setup?
ASKER
well a reboot resolved it and it started.
Note down, whatever you are changing, each and every value.
ASKER
Nothing was changed, a reboot resolved it.
Now we are about to proceed with the major steps of the article that was posted above
http://technet.microsoft.com/en-us/library/bb310767(EXCHG.80).aspx
One question, is Step 2 needed, if I am reading correctly its only if my other Exchange is 2003 or 2000, Is that correct?
Now we are about to proceed with the major steps of the article that was posted above
http://technet.microsoft.com/en-us/library/bb310767(EXCHG.80).aspx
One question, is Step 2 needed, if I am reading correctly its only if my other Exchange is 2003 or 2000, Is that correct?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I guess I should of been more clear. My question is on this: (Does this step need done if both my Exchange servers are 2007)
2.To modify the routing group connectors between the Exchange 2007 routing group and the Exchange 2003 or Exchange 2000 bridgehead server, run the following commands:
Get-RoutingGroupConnector | where {$_.SourceTransportServers -like "<First Exchange 2007 server>"} | Set-RoutingGroupConnector -SourceTransportServers "<Second Exchange 2007 server>"
Get-RoutingGroupConnector | where {$_.TargetTransportServers -like "<First Exchange 2007 server>"} | Set-RoutingGroupConnector -TargetTransportServers <Second Exchange 2007 server>
2.To modify the routing group connectors between the Exchange 2007 routing group and the Exchange 2003 or Exchange 2000 bridgehead server, run the following commands:
Get-RoutingGroupConnector | where {$_.SourceTransportServers
Get-RoutingGroupConnector | where {$_.TargetTransportServers
Do you have Exchange 2003 also? Is this a co-exist env? I thought you are into pure 2007 env as Exchange 2007 doesn't have any Routing group concept. It used AD Sites for communication.
ASKER
Current is Exchange 2007 Sp3
New is Exchange 2007 Sp3
Same Domain, moving everything from CURRENT to NEW.
New is Exchange 2007 Sp3
Same Domain, moving everything from CURRENT to NEW.
you dont need to perform this task, once you remove first exchange server all will get mapped to the new one
ASKER
KB Article provided was right on track
Exactly what I needed to know
Exactly what I needed to know
ASKER