SMSMSE is installed on an Exchange 2010 mailbox server. A scheduled or manual scan is created or edited. However the list of mailboxes to select is empty.
Perform the following steps to verify that the public folders are empty:
1. Log into the Symantec Mail Security for Exchange (SMSMSE) adminstration console.
2. Click on the Scans tab.
3. Perform the following steps to configure a manual scan:
a. Click on Views|Manual Scan.
b. Click on Tasks|Edit manual Scan...
c. Click the Next button.
d. Validate that there are no mailboxes listed in the Mailboxes section of the dialog box.
4. Perform the following steps to configure a scheduled scan:
a. Click on Views|Scheduled Scans.
b. Click on either Tasks|New scan... or Tasks|Edit Scan....
c. Enter a name for the scan if appropriate then click the Next button.
d. Validate that there are no mailboxes listed in the Mailboxes section of the dialog box.
SMSMSE service account does not have the rights to build a list of mailboxes on the Exchange 2010 Mailbox role server or the appropriate assemblies are not registered correctly
The SMSMSE Service account should already be a member of the "SMSMSE Admins" active directory group. You will need to ensure that "Organization management" or "View-only Organization Management" rights are assigned to this account also:
To verify the account the SMSMSE service is using
To assign the appropriate permissions to the service account
To apply the changes made to permissions to the SMSMSE service
After completing these steps, check to determine if you can now see your mailboxes listed in the "Scan location" tree.
If you see this issue even with the appropriate permissions assigned to the SMSMSE user account, verify that a list of mailboxes is stored in:
C:\Program Files(x86)\Symantec\SMSMSE\6.5\Server\Config\master.mb (open with notepad).
There should be entries for each mailbox, one per line, that look similar to the following:
[email protected];S-1-5-21-1449310211-615098520-2967644832-500
If there are still no entries in this file, there may be a corruption problem with the existing service account. This can be verified in the security event log. In this instance, you will need to create a new Service Account and assign the appropriate permissions and group memberships.
If the issue persists, you may need to verify .NET registration of SMSMSE components as follows: