[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2361
  • Last Modified:

Public folder replication problems (Event id 3093)

I have a new server with Exchange 2003 SP2 loaded and ready to go.  I am decomissioning an SBS 2003 and I am first trying to move all public folders to this new server.  So, I chose "move all replicas".  As this appeared to be the new and improved way of synchronizing public folders.  It has been around 8 hrs and it is still going.  During the day I have received event id 3093 error messages in the app log.  Also, when I click on replication status for the SBS server i get an "an unexpected, unknown error has occured.  MAPI or an unspecified service provider.  ID no: 800401f-00000000 ID no: c105010f Exchange System Manager.  Eventhough I am getting these errors it does loook like some data is still coming across with the diag logging set to maximum for incoming and outgoing public folder messages.  Also, I see the hierarchy on the new server.  Should I let this replication process keep running or should I do something else?  Have I lost my public folders at this point?  Any help is appreciated.
0
cbsykes
Asked:
cbsykes
  • 3
  • 2
1 Solution
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Not sure how you were doing your entire migration from SBS 2003 to Standard Servers, but you can't just "decomission" an SBS.  

Did you not use the Transition Pack?  http://sbsurl.com/transition

Jeff
TechSoEasy
0
 
cbsykesAuthor Commented:
I am applying the transition pack as soon as I migrate exchange to the new box.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
It doesn't work that way.  You need to apply the transition pack FIRST so that you remove the SBS restrictions from that server.

Jeff
TechSoEasy
0
 
cbsykesAuthor Commented:
What does the transition pack have to do with migrating Exchange to a new box?  I have read on many posts to migrate all Exchange data before breaking down SBS.  Is this not correct?  Also, I have performed this method in a test lab with no problems.  Thanks for your help!
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Sorry, I must have missed the last post.

"What does the transition pack have to do with migrating Exchange to a new box?"

Technically, it doesn't, but licensing-wise it does.  So, I'm guessing that you have purchased separate Windows Server CORE CALs (including Exchange CALs)?  In a 60-user environment, that can cost you about $8,000.00 more than if you had used the Transition Pack.  Serious waste of money.

As for migrating the data of Public Folders, you can use pfmigrate.exe, but my preferred method is to use Outlook to export them to .pst files and then use Outlook again to import them back to the new server.

Jeff
TechSoEasy
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now