Enable mailbox list is wrong

[oguzhan]

The users are not in the provisioning group but these users seems in the enable mailbox list.

Why occurs this issue?

Thank you,

[LCT]

I am not sure what you are asking, I suspect the users have been moving around within the Provisioning Groups? Have you run the provisioning task to update the users?

[FreKac2]

If the users have been provisioned but then you've removed them from the provisioning group/s, then they still have a record in the EV Directory Database.

What are you using as a target for the provisioning group/s (OU,Windwos Security Group, LDAP query, ....) ?

[ManishN]

Enable mailbox list entries from the Exchangemailboxentry table from the SQL server under the EnterprisevaultDirectory database.

The above comments are true if you add in provisioning group and if the provisioning task has run either in scheduled or manual it will updates the entry in the exchangemailboxentry table. Later on if you remove the entry from the group which is in provisioning group, it's not going to clear the table.

So if you want to clean those wrong entries which are listing in Enable mailbox, you can open SQL Server Management Studio and perform the following steps.

a. Click on New Query

Use EnterpriseVaultDirectory

select * from exchangemailboxentry

and Click on Execute or press F5

You can check the result at the bottom. You will find those wrong entries which has been provisioned accidently.

b. Delete those entries manually by running sql query

or

You can flush/clean the exchangemailboxentry table and then confirm that the provisioning group has valid members and not any members which are not to be provisioned and then run the provisioning task.

After running the provisioning task the exchangemailboxentry table will get updated.

Note: Please perform a full backup of your EnterpriseVaultDirectory database backup in order to avoid any causes if you make any mistakes. You need to take advise from your SQL expert in order to run any query in SQL database.

[JesusWept3 · Accepted solution]

If a user *was* provisioned and is no longer provisioned, they will not have any policies or provisioning entries so they should not come up for enablement after the next provisioning run.

So for instance if you add a user to a provisioning group, and then run provisioning, you should be able to run the Enable Archive Wizard and the user will be available to enable.

If you then remove the user from the list and DO NOT run provisioning, the user will still be available to enable (the EME entries will have the policy and groups still populated)

If you then run provisioning, the user not being listed in any provisioning group, the user will no longer be eligible for enablement, the EME entries for Provisioning group and policie will all be set to Null.

So either the user is in another provisioning group, which i think frekac was alluding to, because if you are targeting an OU or a DL, its possible the user is in one of those containers

OR you need to re run provisioning.

Yes, you can run a SQL query to clean it up, but thats over the top and unnecessary