How to determine when Symantec Email Submission Client (SESC) has performed a system update and how do I find out more information about a system update in progress?

book

Article ID: 180988

calendar_today

Updated On:

Products

Mail Security for Microsoft Exchange Messaging Gateway

Issue/Introduction

 

Resolution

SESC performs a "system update" either on a scheduled basis or manually at the request of an administrator.  The administrator uses the SESC console to start a system update (see below for more information). The system update process can take a long time.  As an example a system update for thirty thousand (30,000) mailboxes can take anywhere from one to four hours.

This article provides information on how to determine when system updates start and stop and how to find out more information about a system update that is in progress.

SESC logs the following event in the Windows Application Event log when a system update has started:

Log Name:      Application
Source:        Symantec Email Submission Client
Date:          3/1/2012 7:57:14 AM
Event ID:      10
Task Category: Subscription
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      sesc-3.2k8domain.test
Description:
Provisioning started.

SESC logs the following event in the Windows Application Event log when a system update has finished:

Log Name:      Application
Source:        Symantec Email Submission Client
Date:          3/1/2012 7:57:18 AM
Event ID:      11
Task Category: Subscription
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      sesc-3.2k8domain.test
Description:
Provisioning finished.
Total time taken: 3.6659765 seconds.

If a system update has started but not finished the SESC debug log C:\Program Files\Symantec\SESC\1.0\Logs\log.txt (see article How to Obtain Debug logs for Symantec Email Submission Client (SESC)
for more information about debug logs) contains information about the provisioning. 

When a provisioning starts the following appears in the debug logs:

[::]2012-03-01 07:57:14,885, [21], INFO , Symantec.Submission.Service.MailboxManager, Entering into updation thread[::]
[::]2012-03-01 07:57:14,900, [21], INFO , Symantec.Submission.Service.MailboxManager, Total number of existing mailboxes: 0[::]
[::]2012-03-01 07:57:14,947, [21], DEBUG, Symantec.Submission.Service.MailboxManager, Total number of mailbox databases in the scope: 2[::]
[::]2012-03-01 07:57:14,963, [21], DEBUG, Symantec.Submission.Shared.ActiveDirectoryInterface, Ldap Filter: (&(objectClass=user)(|(homeMDB=CN=Mailbox Database 1108598897,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=2k8domain,DC=test)(homeMDB=CN=Mailbox Database 0944899278,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=2k8domain,DC=test))(mail=*))[::]
[::]2012-03-01 07:57:14,963, [21], DEBUG, Symantec.Submission.Service.MailboxManager, Number of mailboxes in domain "2k8domain.test": 7[::]
[::]2012-03-01 07:57:14,994, [21], INFO , Symantec.Submission.Service.MailboxManager, Total number of mailboxes: 7[::]

As the service iterates through the mailboxes and creates mailboxes the following is written to the debug log for each mailbox where a folder is created:

[::]2012-03-01 07:57:17,100, [43], DEBUG, Symantec.Submission.Service.FolderJobManager, Subscription id: FwBleDIwMTBkYy4yazhkb21haW4udGVzdBAAAABFqYve9po9SIH4rpX+NxFK6thqHNvFzgg=
User: DiscoverySearchMailbox{D919BA05-46A6-415f-80AD-7E09334BB852}@2k8domain.test[::]
[::]2012-03-01 07:57:17,115, [43], DEBUG, Symantec.Submission.Service.FolderJobManager, Folder Name: Submit Spam to Symantec
Folder id: AAMkAGU2YWFiNzczLTQwMTYtNGVmYS1hOTQxLTc3ZDQ0MTM4YWIwYgAuAAAAAABmykiLYnNGSYQqDe5WeXBOAQCIcEhDFYtpS5ZSTNOhLJS9AAAAwEGsAAA=
*********[::]

Using this information you can determine how far along the system update process is.

Technical Information

Performing a manual system update

 

1. Open the SESC console.
2. Open the System Update pane.
3. Select the appropriate Exchange servers from the Select Servers tree.  Or select all Exchange servers.

NOTE:  Selecting all Exchange servers is fine as SESC only updates those that are new or were not able to be updated previously.


4. Click the Update button.

Environment

  • SESC 1.X