how to reassociate archive with recreated mailbox

[James_Drake]

Hi,

I have a scenario where a user who was in EV had his mailbox attributes stripped and a new mailbox recreated but all the content retained (ingested from an exported Outlook PST) including EV shortcuts. The same AD account was retained. Hence the mailbox GUID is now different.

No archiving or enrollment has taken place against the new mailbox.

What is the best or easiest way to reassociate the old archive against the new mailbox, is there some kind of script I can run to update GUID association in the database?

I have some ideas which involve stripping shortcuts, exporting to PST from EV and importing to the new mailbox with shortcut population. However, I don't really want two references in any way shape or form for this archive.

James

[GertjanA · Accepted solution]

Hello James,

I believe the process is easy.

1 - make sure the user is in a provisioning group. (with his new mailbox...)

2 - run provisioning.

3 - enable the mailbox manually in the VAC

4 - during the enabling, you should be able to select the existing archive.

5 - sync mailbox (including permissions)

6 - Done.

You can then do a report run on the archiving task, and see what that gives.

[James_Drake]

That worked thanks. Not sure why I didn't see that option in the first place. Weekend involving an Exchange 2013 nightmare just draining me I think.

[GertjanA]

yw.

I assume you are running EV10 (seeing you use Exchange2013)?

Have you applied the necessary hotfixes to archive from Exchange2013? Just asking.

Please mark answer as solution if applicable.

[James_Drake]

10.0.4 with all additional fixes that are required for 2013.

The core project was a migration to Exchange 2013 from 2010. In summary, my opinion is that Exchange 2013 CU 2 is not ready for production, or at least in the capacity of this particular installation it isn't.

It is not just EV integration, there were too many other issues with it natively and integration with other products which are used here, so we had to roll the users back to Exchange 2010.

I thought after a year that Microsoft would have got it up to scratch, but I'll be continuing with Exchange 2010 for now.