Link to home
Create AccountLog in
Avatar of Hieristie
HieristieFlag for Netherlands

asked on

Migration multiple Exchange 2003 servers to one 2010 server

Hi Experts,

We are migrating from Exchange 2003 tot 2010. Al is working great but now we want to remove the old 2003 servers.

I know the best way is to remove the mailbox- and public folders stores and then deinstall exchange of the boxes.

We do have 4  exchange 2003 servers, 3 production and one test. The test server has been off for some time and one of the colleages has removed the server from AD :-(. How to go from there. Can I just choose remove server from System Manager or should I rejoin the server. I think rejoining probabely won't be the right way to go..? I try to avoid using ADSI, because I'm not to familiar with that and I've heard one can screw up big time when doing it wrong.

Then we have to get rid of the public folders on the 2003 servers, before we can uninstall the serveral exchange servers. We now have moved the public folders of one of the servers to the new 2010 server with System manager | First Storage Group | Public Folders | Move all replicas. Should I do the same with the other servers or am I going to get conflicts or overwriting old data and is there another way to get rid of the replications on the several servers.

Is there a way I can check to see if all public folder(item)s are present on the new 2010 server?

Thanks in advance,

Erik
ASKER CERTIFIED SOLUTION
Avatar of Simon Butler (Sembee)
Simon Butler (Sembee)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of Hieristie

ASKER

Having major problems getting rid of the old PF. Moving seems ok for most of the servers, but the front-end, which had the store dismounted gives en error when trying to move all replicas that some folders no longer exits, which is quite logically to me, since they have turned off the public folder store due to security reasons if I’m correct.

On 2 other servers the moving seems to be working although the Public Folder Instance doesn't get fully empty. With just one server the Public Folder Instance has become empty. I need to say that it should have more than enough time to replicate. For over 3-4 days.

How to get the others empty?

Also if this finally should be completed do I have to remove the Mail stores before the Public Folder stores, because I believe the Mail store holds some mailboxes (system boxes) that rely on the Public Folder Store?

I already have moved the Public Folder Hierarchy as mentioned in one of the many articles I've read. In another though I read that this is an action to be taken after the old PF's have been removed. Should I place the Folder Hierarchy back to the Exchange 2003 environment until all PF's have been decommissioned?

Thanks again,

Erik
Getting the error message "Could not locate root folder" on front-end server.

With two of the other (back-end) servers I renamed the pub.edb and pub.stm folder and created new files. Then the replication took some time and the Instances were gone after a while when moving the replicas to the 2010 server.

This is a trick I read / heard somewhere and seems to have worked. On the front-end it looks tricky to me since the occurring message mentioned before (see attached file). When I renew the db files will they be able to get updated and moved since the public root folder can't be located.

There was the IIS Urlscan Tool 2.0 installed on the front-end, which I de-installed and iislockdown is present on the system, but that is probably not installed, because that is for a previous version, so it seems. I think the front-end is an upgraded server since the %WINDIR% is C:\WINNT and urlscan was situated in C:\WINNT\system32\inetsrv\urlscan.

Therefore I believe iislockdown might have been installed on the previous version of IIS when it still was a WIN2K server, I assume.

Any ideas on how to get to the root public folder..?

Thanks in advance.
Error-message-trying-to-connect-.PNG
I've removed the public folder and mailbox store from one of the 4 servers. So replication between that server and the new 2010 server was completed (Instances on 2K3 box were empty). Should I remove all PF's and MS's and than deinstall exchange or probably de-install the server from which the stores have been removed..?
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Hi Simon, thanks for your input. Much appreciated!

Still some questions.

On that server, where the stores have been removed, McAfee Groupshield is installed. Do you know if it's desireable to uninstall Groupshield before uninstalling Exchange?


I'm having trouble getting the Public Folder Instances empty of the front-end, which was sitting in the DMZ. I moved it over to the inside, because we don't have the need for the OWA functionality anymore, because this is now handled by the new 2010 box.

The front-end is hardened it seems. I recreated a mailbox store and recreated the public folder databases. Now there are only four folders left in the Public Folder. These are Global events, internal, OwaScratchpad{....} and StoreEvents{.....}. But when I try to Move the replica's, which went fine finally with the back-end servers, I'm getting the message "The operation failed due to an invalid format in the HTTP request. Verify that the host header is correct for the virtual server". This is probably due to the act that I moved the server over from the DMZ to the Internal network. That I did because I've been trying to get rid of the hardening in the hope that the public folders would move over and therefore not creating a security risk. I'm getting the same message when selecting or asking for properties of these folders.

How do I get rid of those Public Folder Instances?


Is there a special order in which the servers should be decommissioned? I've read about removing the first installed exchange server as last one, because this one should be holding some special roles / services? If so, how can I find out which server this might be? I assume it will be the front-end, because I believe this server has been upgraded from Win2K to Win2K3 and all the others are Win2k3.

I’ve also read about removing the last legacy exchange server from an exchange 2010 organization, and that the Interop Routing Group Connector must be removed. But the server that holds that connector is also the only server that is a member of the ExchangeLegacyInterop group. Is that the last server to be removed?
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Help.....

All went well until I just removed the serverwith ESM which computeraccount was deleted by one of the colleagues . Now I'm getting an error on the new 2010 Exchange server and the Shedule+Free / Busy System Folders are missing.

The action
If the server has been removed from AD then your only option is to use the right click remove method from ESM. The menu will take some time to appear, so be patient.
didn't turn out to be as I hoped for...

Getting the error:
User generated image

I only see these folders, which where a lot more before"
User generated image
Any idea on what to do with this situation and what will be the consequenses. Something with the calendring objects I assume?
On the Exchange 2K3 server (last back-end) I still can see all the folders..?? See attached picture..
Public-Folder---System-Folders-o.PNG
Now I'm really confused. Al folders are back and things seem to have corrected itself. Or could this be due to the fact that I added a registry key as mentiond in the Eventlog and the msdn blog (http://blogs.msdn.com/b/dgoldman/archive/2007/08/10/installing-exchange-2007-in-to-a-mixed-organization-will-create-a-valid-pdn-entry-and-break-oab-generation.aspx)

Is there any thing I have to do still before / after decommisioning the last exchange 2003 server concerning the Public Folder System Foldres.? I already was under the impression that the OAB, Schedule+ free/busy were already (re-)homed on the new exchange 2010 box before removing the old test mailserver which had been removed from AD instead of using the most preffered de-installation procedure.

I now have two leagacy servers left. The front-end and the last back-end. The back-end holds the Recipient Update Service as can be seen under Recipients | Recipients Update Services in ESM. Do I have to rehome this to the new 2k10 exchange server or does this become decomissioned as I read in the "remove the Last Legacy Exchange Server from an Exchange 2010 Organization (http://technet.microsoft.com/en-us/library/gg576862)?

I absolutely try to avoid things like what happend as mentioned above, because that's really bad for my health. Did cost me a nights rest..and a lot of extra heartbeats.
Public-Folder---System-Folders-o.PNG
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
How do I replicate the PF and SF off'? I've seen an option in ESM, with the right mouse button on the domain, there is an option "Stop Public Folder Content Replication" . Is that what you mean by

The public and system folders will have to be replicated off

or does this happen automatically when removing the last server (back-end)?

The front-end still does contain some instances, which won't go: User generated image
When trying to "Move All Replicas" I'm getting the error: User generated image
The instances of the back-end are empty as supposed.

How do I get rid of the instances on the front-end? You mentioned earlier that this has to be done with ADSI if I'm correct. Do you know where exactly what to remove?
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Hi Simion,

I've disabled the exchange related services on the front-end and last back-end exchange 2003 boxes for some weeks now and it seems all is working fine for as far as I've been able to see. I've had no complaints on missing public folders or so. I'm planning on re-enable the services on the exchange 2003 servers and try to decommission them. As I mentioned before, I'm not experienced with ADSI so if you could tell me where I should remove the remaining instances on the front-end, as shown above in the "PF instances" picture, I would be most grateful.

Thanks again,

Erik
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Hi Simon,

Yesterday I re-enabled the services and have tried several thing again. Also tried "Move Replica's" again, but still the error. I did leave it overnight, but no changes to be seen. The instances , as seen @ ID 38613809 just rihgt above, are also still there. So I'm at the point of removing the DB with ADSI. Do I have to stop some services on the FrontEnd server before removing the DB with ADSI or should I leave them running. Like the Information Store servive for instance.??

I did find an article on how removing the DB, but it only shows me where the DB is situated in AD but doesn't say anything about whether or not I should stop anything like services for instance. Perhaps I shouldn't even start it again after removing it with ADSI in which case I should remove the mailbox store on forehand?

Could you give me some clarification on these things.

Thanks again,

Erik
Hi Simon,

I've removed the PF DB with ADSI and have been able to uninstall Exchange from the front-end. I do have one more question about the FREE/Bust Schedule, but comitted a new question for this so I can close this question.

I want to thank you for your inpute and the time you've taken to assist me.

Kind regards,

Erik