mbxarchivingstate

I understand that the following are the different values this column can have... 0 = Not Enabled 1 = Enabled 2 = Disabled 3 = Re-Link However, I am confused exactly what 0 and 3 mean. I have some users with a 3, and some with a 0. However, I would expect that 0 means it's a new mailbox? When I use the enable mailboxes wizard the current two that show up have different values for the status; one is 0 the other is 3. Could someone enlighten me? How does one "re-link" the account?
1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

You can use this technote to


You can use this technote to enable hidden mailboxes:

http://seer.entsupport.symantec.com/docs/282737.htm

There is also a link to the technote for disabled accounts;
http://support.veritas.com/docs/336978

Cheers,

For the best O365 Reporting Solution click here Radar-Reporting

View solution in original post

4 Replies
Highlighted

Hi Meg G, As you mentioned

Hi Meg G,

As you mentioned MbxArchivingState = 0 means the mailbox is either new or it has been Zapped (The Enterprise Vault hidde message has been deleted and the mailbox would appear as a new mailbox).
http://seer.entsupport.symantec.com/docs/273154.htm


If the mailbox has Mbxarchiving status = 0 ideally it should be a new mailbox and has never been associated with an archive. If that is the case then you need to archive enable the mailbox by following the wizard to completion.

If the mailbox was archive enabled before and has been zapped, then the MbxArchivingState would be reset = 0, when archive enabling the mailbox again you would need to link(re-associate) the mailbox to the user's existing archive.



If the MbxArchivingState = 3, it means mailbox has been moved and would need to be re-linked with the user's archive, when archive enabling the user click on "Select Archive" ->Expand the Vault Store the archive is in select it and proceed. The mailbox will be archive enabled and re-associated with its archive instead of creating a duplicate archive.



Highlighted

Thanks for that information

Thanks for that information evchaps.

Issue ended up being because I missed that some of the mailboxes were hiding from the GAL, and some of the AD accounts were disabled.  Disable accounts showed up as 3, and users who were hiding from the GAL but were new mailboxes were a 0.  When they were hiding from the GAL they didn't show up as a new mailbox by running the enable mailboxes wizard.  If only EV was smart enough to ignore the GAL, and just use LDAP, but apparently not (or I'm not smart enough).

Highlighted
Accepted Solution!

You can use this technote to


You can use this technote to enable hidden mailboxes:

http://seer.entsupport.symantec.com/docs/282737.htm

There is also a link to the technote for disabled accounts;
http://support.veritas.com/docs/336978

Cheers,

For the best O365 Reporting Solution click here Radar-Reporting

View solution in original post

Highlighted

Hi Meg G, Enterprise vault by

Hi Meg G,

Enterprise vault by default will not archive enable or process mailboxes which are hidden from the GAL(http://seer.entsupport.symantec.com/docs/282737.htm), run the following SQL query against the ExchangeMailboxEntry table:

Use EnterprisevaultDirectory
Select MbxDisplayName, MbxArchivingState, MbxExchangeState
from ExchangeMailboxEntry
where MbxExchangeState = '2'

mbxExchangeState = 0 is Normal mailbox, 1 = Deleted, 2 = Hidden.


Once you have unhide the hidden mailboxes run the provisioning task, archive enable the mailboxes and you can go back to hide them and implement the following registry key for processing hidden mailboxes :

HKLM\Software\KVS\Enterprise Vault\Agents
ProcessHiddenMailboxes = 1


http://seer.entsupport.symantec.com/docs/350432.htm


There is also a registry key to process mailboxes with disabled AD accounts:
HKLM\Software\KVS\Enterprise Vault\Agents\
ExcludeDisabledADAccounts=0

http://seer.entsupport.symantec.com/docs/336978.htm