SBS 2003 to 2008 Public Folder Migration Not Working
I'm testing a migration from our SBS 2003 environment to SBS 2008. We have a lot of stuff stored in our public folders so it's pretty important to us. The mailbox move went fine, but the Public Folders have not. I've followed MS's SBS 2008 migration docs closely, and we have no smarthosts set up.
Here is what is going on:
I know the public folder replication happens through SMTP, and the SMTP queue is backed up with what looks like replication messages for Public Folders. (It is backed up because this is a non-internet-connected testbed) However, from lots of the documentation I've read it seems that it should be going to the new migration connector that the SBS migration utility sets up.
I have a theory on what is going on but I don't know how to fix it. Our domain name is companyA, and we have email addresses for companyA.com, however our primary email addresses are companyB.com. Now what I'm getting at with this is the messages in the queue are addressed to companyB.com, probably because that is our primary email address. It's like Exchange is confused on where to send the replication messages and they are backing up in the regular SMTP queue instead of going to the migration connector. Any ideas?
Here is what is going on:
I know the public folder replication happens through SMTP, and the SMTP queue is backed up with what looks like replication messages for Public Folders. (It is backed up because this is a non-internet-connected testbed) However, from lots of the documentation I've read it seems that it should be going to the new migration connector that the SBS migration utility sets up.
I have a theory on what is going on but I don't know how to fix it. Our domain name is companyA, and we have email addresses for companyA.com, however our primary email addresses are companyB.com. Now what I'm getting at with this is the messages in the queue are addressed to companyB.com, probably because that is our primary email address. It's like Exchange is confused on where to send the replication messages and they are backing up in the regular SMTP queue instead of going to the migration connector. Any ideas?
More specifically, I was able to copy the public folder up to the user's contacts (because it was a contacts folder), export to csv and import to the user's new account on the 2008 installation, then drag to the public folder and share it.
ASKER
Actually almost as soon as I write this I think I figured it out. I added an internal DNS zone and MX record for companyB.com and restarted the SMTP server on the source server and it seems to be flowing. I'm thinking for my next test I will temporarily set the primary email address back to companyA for the migration then change it back to companyB once it's finished. That might be the easiest route to go if it works. I am going to re-test the migration with the experience I gained in the first round of testing and post back the results.
ASKER
That wouldn't be an option for us because we have a heirarchy of folders containing client emails. Thanks for the input though
I believe Microsoft would like to see you move away from public folders and use Sharepoint instead. Just something to think of for the future.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
So, I connected via Outlook to the 2003 public folders and exported. Saved the file to a locaiton accessible to the 2008 server and then as that same user on the 2008 side, connected via Oultlook and imported it.