The Provisioning Task's report will show something similar to the following:
8:23:10 1 Customer Standard Users Group customer\appevstandardusers customer Standard Users Mailbox Policy customer PST Migration Policy CN=name\, firstname,OU=mgmt,DC=customer,DC=local Skipped journal mailbox.
The mailbox is being detected as a journal mailbox, which cannot be enabled for archiving in the same way as a user mailbox.
First, check that the mailbox is indeed not being used in any journaling rules in the Exchange Organization; if it is, then the offending journaling rule will need to be removed or assigned to use a different mailbox as the journal recipient.
Without further action, it may take a few hours for the changes to synchronize back to EV on the automatic schedule; however, the following steps will speed this up.
1. Ensure that the mailbox is properly targeted by an appropriate Provisioning Group.
2. Run the following SQL statement to update the mailbox's entry in the EV Directory database.
USE EnterpriseVaultDirectory
UPDATE ExchangeMailboxEntry
SET ExchangeMbxType = '1'
WHERE MbxAlias = 'MailboxAlias'
Replace the italicized value with the appropriate value for the mailbox in question.
3. Run the Provisioning Task again and then check to see if the mailbox is listed as new in the Enable Mailboxes wizard. If so, proceed as normal.
4. If the mailbox is still not detected as new, or if the ExchangeMbxType value that was updated has reverted to 2, remove the mailbox's entry from the Directory database by running the following SQL statement.
USE EnterpriseVaultDirectory
DELETE FROM ExchangeMailboxEntry
WHERE MbxAlias = 'MailboxAlias'
Replace the italicized value with the appropriate value for the mailbox in question.
Then run the Provisioning Task again and check that the report shows that the mailbox has been added as new.