cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Mailboxes that have entries in the EV DB which are not in any provisioning group:

Hi Just starting this thread again as the thread below was never actually resolved.

 

https://www-secure.symantec.com/connect/forums/mailboxes-have-entries-ev-db-which-are-not-any-provis...

I have seen a similar issue where the AD\exchange user is not being changed, the only difference is moving the user between one PG and another.

A provisioning group run end in a Prov report successfully picking up the Account in the moved PG but then at the end logging the error.

"Mailboxes that have entries in the EV DB which are not in any provisioning group:"

This is occuring for at present 6 users from different AD groups and from different exch servers. They have been moved from Exch 2003 to Exch 2010 servers which is the only significant change.

These users are working fine after the move from Exch2003 until they are moved between prov groups, then they lose all EV behaviour or ability to be recognized by EV

I have a Dtrace of the evexchangesynchtask but it only seems to show success, found user, updating DB, found SMTP addresses.

Users are provisioned by AD group not ldap or individual windows users, although the individual windows user has been tried, but no difference.

EVPM zap has been tried, delete on exchangemailboxentry table has been tried, there are no duplicates for this user in the exchangembxentry table.

Thanks

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Actually if you read the

Actually if you read the Events it tells you what to do:


28371 10:40:35.498  [6392] (EvExchangePolicySyncTask) <4660> EV~W 
Event ID: 41107 The Exchange mailbox provisioning task found a new mailbox with an existing entry in the Enterprise Vault database. The mailbox GUID does not match the entry in the database.
Task: Exchange Provisioning Task for corp.testdomain.net
Mailbox: /o=testdomain/ou=First Administrative Group/cn=Recipients/cn=croucs
Set the SynchInMigrationMode registry value in order to process this mailbox.
See the documentation for further details.
 

You need to use SynchInMigrationMode and set it to 1

HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\Agents  
DWORD: SynchInMigrationMode

0 — (Default.) Enterprise Vault does not assign new mailboxes to archives that are associated with the same legacyMbxDN values.

1 — Makes Enterprise Vault assign new mailboxes to archives that are associated with the same legacyMbxDN values.

2 — Creates new entries for the new mailboxes and renames the old entries by adding timestamps to the legacyMbxDN fields.


Also check this article as its exactly what you have
http://www.symantec.com/business/support/index?page=content&id=TECH54529

https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post

3 Replies
Highlighted

from that dtrace, could you

from that dtrace, could you give us the addresses which is flagged in the reports/event viewer?

https://www.linkedin.com/in/alex-allen-turl-07370146
Highlighted
Accepted Solution!

Actually if you read the

Actually if you read the Events it tells you what to do:


28371 10:40:35.498  [6392] (EvExchangePolicySyncTask) <4660> EV~W 
Event ID: 41107 The Exchange mailbox provisioning task found a new mailbox with an existing entry in the Enterprise Vault database. The mailbox GUID does not match the entry in the database.
Task: Exchange Provisioning Task for corp.testdomain.net
Mailbox: /o=testdomain/ou=First Administrative Group/cn=Recipients/cn=croucs
Set the SynchInMigrationMode registry value in order to process this mailbox.
See the documentation for further details.
 

You need to use SynchInMigrationMode and set it to 1

HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\Agents  
DWORD: SynchInMigrationMode

0 — (Default.) Enterprise Vault does not assign new mailboxes to archives that are associated with the same legacyMbxDN values.

1 — Makes Enterprise Vault assign new mailboxes to archives that are associated with the same legacyMbxDN values.

2 — Creates new entries for the new mailboxes and renames the old entries by adding timestamps to the legacyMbxDN fields.


Also check this article as its exactly what you have
http://www.symantec.com/business/support/index?page=content&id=TECH54529

https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post

Highlighted

Thanks JW2, I guess I left

Thanks JW2, I guess I left out the vital part.

Here are the users entries from the prov task report

10:40:30 5 Default group VC enabled CORP\IVZ- EV EU Default VC Enabled - London Exchange Mailbox Default Policy Default Exchange PST Migration Policy CN=Clark\, Frazer,OU=LON,OU=EU,OU=test,OU=AVZ Clients,DC=corp,DC=domain,DC=net Updated mailbox
10:40:32 6 Default group VC disabled Whole Exchange Organization Exchange Mailbox Default Policy Default Exchange PST Migration Policy CN=Clark\, Frazer,OU=LON,OU=EU,OU=test,OU=AVZ Clients,DC=corp,DC=domain,DC=net Mailbox already updated by provisioning group member 'Default group VC enabled'/'CORP\IVZ- EV EU Default VC Enabled - London'
 

Mailboxes on Exchange Server [GMBX10] that have entries in the Enterprise Vault database but which are not in any provisioning group:
/o=domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Clark, Frazer (state = enabled)
 

I believe the 41107 error refers to a users

ou=First Administrative Group/cn=Recipients/cn=ASGHARR
ou=First Administrative Group/cn=Recipients/cn=croucs|
 

Neither of which are reported in the statement at the bottom of the prov report

"Mailboxes on Exchange Server [GMBX10] that have entries in the Enterprise Vault database but which are not in any provisioning group:"

As you can see from the report excert I have pasted in. user Frazer clark is picked up but two PG's, first by an AD group and secondly by the Whole org umbrella, the first PG confirms the mailbox has been updated, the second PG confirms that the user has already been updated by another PG and then at the very bottom the error occurs saying this user has no PG. I have confirmed that there is only one row for this user in the exchangemailboxentry table.

Thanks again.