Exchange 2003-07 migration gone wrong

Hi, hope someone can help me out here.

I have:

Old server running Windows 2003 and Exchange 2003 (all latest service packs etc)
New server running Windows 2008 and Exchange 2007

I was following this ( http://www.msexchange.org/tutorials/Transitioning-Exchange-2000-2003-Exchange-Server-2007-Part1.html )guide on transitioning the exchange from the old server to the new one.

All was going well until I got to part 3, repilcating public folders.  To let you understand we have about 40gigs of data in public folders.  I know this is not good but its out with my control.

I kicked off the replication of these folders from the old server to the new server.  
I also started moving a few of the mailboxes over.  All at this point seemed OK.

The next day I had the client phone me saying that email was running dead slow, and could I fix it.  I did the typical reboot the 2 mail server and while this kicked out some of the messages that were in the queues it didn't improve much.
I decided to undo the replication so that all replicas would be on the old server again.  Oddly when I checked the size of the public folder store on the new server it hadn't grown at all and users on the new server couldn't see any data in these folders.
I also had the problem that those on the new server could only email each other and likewise with the old server, there seemed to be no routing between the server working at all.  I thought this might be due to overload from replication.
Eventually I've ended up moving the mailboxes back to the old server.  This solves them being able to send and receive email but the speed issue is still there.  Its like the old server is just constantly trying to do something that's slowing everything on it down.

If I look on the ESM 2003 manager at the queues you can see that there are thousands of messages.  The number just keeps on going up until I reboot, then its just starts again.

I'm now trying to get to the stage where I want to uninstall the Exchange 2007 server for now without causing issues on the old one.

The uninstaller fails on 2 points.

1.  Public folder contains replica's.  I have tried everything and I cannot see any replicas of the public folders.  There is only 5 or 6 system folders in there.

2.  Routing group connectors.  I can see using get-routinggroupconnector that there are indeed 2 connectors, one going to the other server the other coming back.

What I need to know is, can I safely (ie without loosing any data from the old server) use ADSIedit to remove the public folder store from the new server and, can I delete the 2 connectors?

Basically, will this fix this problem for me and my client?

I am desperate to get this sorted out for 9am on Monday so any help would be very, very much appreciated.

Thanks in advance.

Steve
stevencUKAsked:
Who is Participating?
 
endital1097Connect With a Mentor Commented:
1. User the MoveAllReplicas.ps1 script under the C:\Program Files\Microsoft\Exchange Server\bin directory
2. Once the mailboxes and public folders are removed from the 2007 server you can remove the routing group connectors by running
Get-RoutingGroupConnector | Remove-RoutingGroupConnector -Confirm:$false
0
 
stevencUKAuthor Commented:
Hi,

I have just tried the command:

moveallreplicas.ps1 -server serverb - newserver servera

Server a is older 2003 one, serverb is the new 2007 one.

I got the following error back:

WARNING: Object servera\First Storage Group\Public Folder Store (servera) has
been corrupted and it is in an inconsistent state. The following validation
errors have occurred:
WARNING: ReplicationMessageSize(99999999KB) is out of range: [1KB,2097151KB].
WARNING: Object servera\First Storage Group\Public Folder Store (servera) has
been corrupted and it is in an inconsistent state. The following validation
errors have occurred:
WARNING: ReplicationMessageSize(99999999KB) is out of range: [1KB,2097151KB].
[PS] C:\Program Files\Microsoft\Exchange Server\Scripts>

I have checked, and so far as I can see the public folders on servera are visible and working...

Any thoughts?
0
 
stevencUKAuthor Commented:
Scratch that, I realised what that was and fixed it.

I set the message limit for replication to 999999999 and it let me, however I have changed it to 2097151 and the above command now appears to work, although I'll have to wait until it replicates again.

I'm sure I have already tried the moveallreplicas command but it didn't appear to do anything for the situation.

Any further ideas?
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
endital1097Connect With a Mentor Commented:
run the following to determine what folders still reside on the 2007 server
Get-PublicFolder -server Ex2007 \ -recurse
Get-PublicFolder -server Ex2007 \non_ipm_subtree -recurse

Then use the 2003 server to move the remaining folders
Expand Administrative Groups, expand your Administrative Group, expand Servers, and then expand the Exchange Server 2007 object.
Expand the Storage Group, right-click the appropriate public folder store, and then click Move All Replicas.
In the Move All Replicas dialog box, click the Exchange 2003 server to which you want to move the replicas, and then click OK.
0
 
stevencUKAuthor Commented:
First command showed only

IPM_SUBTREE

Second command listed the 6 system folders that I mentioned earlier.

I have now tried the move all replicas from the ESM 2k3 which again it seemed to be happy with.

When I look in folder instances there is only the 6 system folders, no other data folders seem to have ever made it onto this server.
0
 
endital1097Connect With a Mentor Commented:
if those folder exist on 2003 (which they most likely do since they were the source) you can dismount the public folder database on the 2007 server and use ADSIEdit to remove it

since it only contains system folder I would feel safe doing it this way
your offline address book is most likely generating to the 2003 server
2007 doesn't use free busy public folder
0
 
stevencUKAuthor Commented:
Thanks for that.

I'm in the now slow process of backing up public folders just in case it all goes horribly wrong before I delve into the ADSIedit bit.

Fairly sure the OAB is coming from 2003 server.  Any way to be sure?
0
 
endital1097Connect With a Mentor Commented:
Check the settings in system manager for your oab
it should show the 2003 server as the generating server
0
 
stevencUKAuthor Commented:
OK thanks.

One other thing, in the mailbox store on the 2007 server there are a number of disconnected mailboxes.  These were the last of the ones that I moved back to the 2003 server.

If I try to purge them it says they have already been reconnected, which techincally they have been on the 2003 server but I can't seem to get rid of them.

Odd thing is, the other mailboxes that were moved back went fine its just these few that are left.  The only thing I can think of is that these are users who would have logged into their mailboxes while they were on the new server.
0
 
endital1097Connect With a Mentor Commented:
use the clean-mailboxdatabase cmdlet against the database
0
 
stevencUKAuthor Commented:
OK, thanks for all your help so far.

The situation now is that the new 2007 exchange server is now uninstalled cleanly after removing the public folder store and routing connectors between the 2 servers.

It appears that the old server is still generating thousands of messages from servera-IS@domain.co.uk to PublicFolderDatabase@domain.co.uk

At the moment these eventually end up in the SMTP queue for sending outbound causing it to completely clog.

I am combating this by scheduling the queue not to run until 11pm and in the mean time I am periodically clearing the queues of all messages.

What I need to know is, will these messages eventually stop being generated or will the public folders keep trying to replicate with nothing?

Any advise would be very much appreciated.
0
 
endital1097Connect With a Mentor Commented:
you need to go to the 2003 server and make sure the replicas have been removed
i'm guessing the servera-is@domain.co.uk is the 2003 server and publicfolderdatabase@domain.co.uk is the 2007 you removed

what servers currently exist in the environment now?
0
 
stevencUKAuthor Commented:
According to the 2003 ESM there are no replicas now.  both of these address' are 2003 I believe.

the @domain.co.uk is the same for both servers.  These used to grow in the queue between the 2 servers but now its going to the SMTP queue, I think because its the only outbound one there is.

I'm hoping that once each item (of which there are many thousands) has sent this message, the message storm will die away and I can then re-enable the SMTP queue as normal.

What I don't know is what I do if this is not going to happen and the public folders just keep on trying to replicate forever.

0
 
endital1097Connect With a Mentor Commented:
2003 used the format server-is@domain.com for the email address of a public folder database
2007 and later use the databasename@domain.com

so it is trying to send to the 2007 server
if you still have the management shell available to you i would run

Get-PublicFolder \ -recurse
Get-PublicFolder \non_ipm_subtree -recurse

verify that the 2007 server that was removed does not appear in any replica instance
0
 
stevencUKAuthor Commented:
both those commands run on the old server indicte no public folder database present
0
 
endital1097Connect With a Mentor Commented:
add -server 2003srv
0
 
stevencUKAuthor Commented:
Just gives an error saying that server is 2003
0
 
endital1097Connect With a Mentor Commented:
how recent are the messages in the queue?
i would double-check those original six folders for replicas
make sure just the 2003 server is listed
0
 
stevencUKAuthor Commented:
Looking in the queue they date back to 2nd September.  I'll clear the queue and see if the date/time stamps are moving on.  If they are I guess its just a waiting game until they are all processed through.

In the 2003 EMS under Public Folder Store/Replication Status it shows no replicas.  I think this is normal as I have looked on another 2003 server I have access to in a different client and it looks the same.
0
 
endital1097Connect With a Mentor Commented:
ok, yes, they may have just been replication messages that were queued as you deleted the pf database

i would monitor for new messages, if none appear you should be ok
also keep an eye on the application log on the 2003 server for errors
0
 
stevencUKAuthor Commented:
Finally its fixed.

The messages eventually stopped appearing and on deleting them and sorting the SMTP connector back to normal its all fixed.

Thanks to endital1097 for your assistance through all this.  Although no one post gave the final answer they were all helpful and I'll try and find a way of showing that.

Cheers

Steve
0
 
stevencUKAuthor Commented:
Many, many thanks for helping me keep my sanity over what has been a very stressful few days.
0
All Courses

From novice to tech pro — start learning today.