<div>
 &nbsp; Been there done that :) I increased the skip count to 500. Failed half the mailboxes right off the bat. Do you think 500 is too low? I am going to have to revert to the original question. How do you detect and fix corrupt messages on the 2003 side before migration?
</div>


  Been there done that :) I increased the skip count to 500. Failed half the mailboxes right off the bat. Do you think 500 is too low? I am going to have to revert to the original question. How do you detect and fix corrupt messages on the 2003 side before migration?

<div>
well, that's kind of difficult because if they are corrupt Outlook won't display them.<br />
Repairing the database MIGHT fix it but there is no guarantee and that's a lot of downtime eating in to your migration.<br />
<br />
I would increase the corrupt count on one mailbox to say 1000 and see if it gets past it.
</div>


well, that's kind of difficult because if they are corrupt Outlook won't display them.
Repairing the database MIGHT fix it but there is no guarantee and that's a lot of downtime eating in to your migration.

I would increase the corrupt count on one mailbox to say 1000 and see if it gets past it.

<div>
 &nbsp; You are correct. This is just a &quot;test&quot; migration and so far 90% of it has been spent on migrating these problem mailboxes. I'll keep playing :)
</div>


  You are correct. This is just a "test" migration and so far 90% of it has been spent on migrating these problem mailboxes. I'll keep playing :)

<div>
<div class="content wysiwyg-content">
 &nbsp; I have been playing with Windows 2003 to SBS 2011 migration. All goes pretty well except when I try to migrate the Exchange Server 2003 mailboxes. About half of them fail with the error message that there are too many corrupt messages.<br />
<br />
&nbsp; &nbsp;I suppose one more addition step before the migration might be a good idea. Maybe checking the Exchange Server 2003 database for corrupt messages and repairing them. Which eseutil option would do that? Repair?<br />

</div>
</div>


   I have been playing with Windows 2003 to SBS 2011 migration. All goes pretty well except when I try to migrate the Exchange Server 2003 mailboxes. About half of them fail with the error message that there are too many corrupt messages.

   I suppose one more addition step before the migration might be a good idea. Maybe checking the Exchange Server 2003 database for corrupt messages and repairing them. Which eseutil option would do that? Repair?


Exchange Server 2003 Problems

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.