We have two people left on a old MS 2010 server.

The raid failed on it, and after the rebuild, these two users mail files are corrupt and cannot recover them fully.
1. Get's to 40% the other 22%. (ran all the utils on the database and mailboxes.. no avail)

We need to move these two users to the new 2013 exchange on the cloud, but I need to recreate mailboxes for them.
We intend to import PST pulled from the client OST file and import into the new mail file. But it appears that I cannot
create a "orphaned mail file" and assign it to this user...

Can anyone help?

Very simple,
Create the new mailbox. Setup an outlook account. Import PST to Outlook. Outlook will sync with 0365

Current User = Joe Somebody w/corrupted mailbox on server.

New User = Joe Somebody, setup outlook and import pst...
Ok. sounds good, but doesn't the new "joe somebody" AD SSID / SAM information be different from the current "Joe Somebody"?

Won't that be a problem?

I am sorry, but I am not getting your problem. Initially you said, I thought, that you cannot import the PST (old mail).  Now you are saying something different.

Can you delete old mail? Do you have access to Exchange Admin Tools at all? 

I'm sorry for the confusion.

we have a exchange 2010 box, where we have been migration users to Exchange 2013 on the clould.
Everyone has migrated, except for two accounts. (1 being the CEO of the company).
During the move request these two account would fail. When I try to export the mailboxes to a pst file, It will only get so much before export process runs up against the corruption and stops the export process.

So the idea is to (like IBM Domino) create a blank mailbox on the 2013 server, assign each user to their new mailbox, and import whatever we could from the PST files we could get into them.
But it appears you cannot create a blank ("orphaned" per se) mailbox and reassign to the user.

If I create a new account matching the same old account in the same OU, then were going to have a problem.
A. Because it cant be the exact spelling of the User's Name
B. Because even if I set up a new account with a slightly different name, that is going to create a different SID/SAM in AD for this "new user". Hence all security rights in server shares outside of exchange will break for these users, along with any distribution groups, security groups..etc...

So that brings the main question: Is there a way to create a clean/new mailbox for an existing user to switch to?
I would want to create the clean/new mailbox on 2013 and try to assign these users to it, and hopefully all their settings would switch to the 2013 server..(mail, mobile..etc..)

Hi,

Based on my search, we can use the below command  to create a mailbox for an existing user.

Enable-Mailbox john@contoso.com -Database "MyServer\Mailbox Database"

For more detailed information, please refer to the article:

https://technet.microsoft.com/en-us/library/aa998319%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396

Best Regards,

David 

David,

No one is arguing that we can create an email.  Question was how to use a secondary smtp (same object) to send from. I said that this is not possible and he ought to create a new email instead. 

I'm sorry for the confusion.

we have a exchange 2010 box, where we have been migration users to Exchange 2013 on the clould.
Everyone has migrated, except for two accounts. (1 being the CEO of the company).
During the move request these two account would fail. When I try to export the mailboxes to a pst file, It will only get so much before export process runs up against the corruption and stops the export process.

So the idea is to (like IBM Domino) create a blank mailbox on the 2013 server, assign each user to their new mailbox, and import whatever we could from the PST files we could get into them.
But it appears you cannot create a blank ("orphaned" per se) mailbox and reassign to the user.

If I create a new account matching the same old account in the same OU, then were going to have a problem.
A. Because it cant be the exact spelling of the User's Name
B. Because even if I set up a new account with a slightly different name, that is going to create a different SID/SAM in AD for this "new user". Hence all security rights in server shares outside of exchange will break for these users, along with any distribution groups, security groups..etc...

So that brings the main question: Is there a way to create a clean/new mailbox for an existing user to switch to?
I would want to create the clean/new mailbox on 2013 and try to assign these users to it, and hopefully all their settings would switch to the 2013 server..(mail, mobile..etc..)

Yes, your concern is correct, you can't create a new AD account because the SID will change.  You can't create a new mailbox on Office 365 because the AD account will still think it has a mailbox already, which technically it does, it's just broken.  You could try removing the mailbox while leaving the AD account intact (https://technet.microsoft.com/en-us/library/aa997210(v=exchg.150).aspx) although I'm not sure if it will succeed since the mailbox is corrupted.  If these are the last two mailboxes in the old DB on Exchange 2010, have you thought about trying to repair the database?  Or even better try to repair the individual mailboxes with a repair request cmdlet (https://technet.microsoft.com/en-us/library/ff625226(v=exchg.141).aspx).  I think this is the answer you're looking for.  If you can repair the two mailboxes, or the entire DB, then you should be able to retrieve their mail, plus be able to finally migrate them to Office 365 with hopefully no further issues.