Skip to main content

LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

PRB: MailMarshal for Exchange Engine takes a long time to start.

Expand / Collapse


This article applies to:

  • MailMarshal Exchange 5.X

Symptoms:

  • MailMarshal Exchange Engine takes a long time to start.
  • MailMarshal Exchange Engine is slow to start.
  • MailMarshal Exchange Engine is taking too long to start.
  • MailMarshal Exchange is not starting or restarting in an acceptable amount of time.

  • MailMarshal Exchange takes in excess of 5 to 10 minutes to start.
  • Error: 'Unable to get groups from domain <cn=users,cn=builtin,dc=server,dc=domain,dc=com> - <Not enough storage is available to complete this operation.>'

Causes:

On startup, MailMarshal Exchange attempts to download the entire tree from the Global Catalog.  If the entire tree for the organization is substantially large, or if there are Global Catalog server issues, MailMarshal may not be able to complete the download in an acceptable amount of time.

Reply:

In MailMarshal Exchange 5.0.3.30, a change was made to the Engine service to allow domains to be excluded from the Global Catalog lookup.

This change requires the following registry modifications:

Warning: Using the Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system.  LevelBlue cannot guarantee that problems resulting from the incorrect use of Registry Editor can be resolved. Make sure that you backup your Registry prior to making any changes.

  1. Launch the Microsoft Registry Editor.
  2. Go to the following key:  HKEY_LOCAL_MACHINE | SOFTWARE | Marshal Software | MailMarshal Exchange | Default | Engine.
  3. Add the key ADDomainExclusions as a multi-string value. The key works on Distinguished Names which are similar to the following:
  • cn=users,cn=builtin,dc=server,dc=domain,dc=com

Following this example, the values of the key could be:

  • cn=users,cn=builtin,dc=server,dc=domain,dc=com
  • cn=*,cn=users,cn=builtin,dc=server,dc=domain,dc=com
  • *dc=server,dc=domain,dc=com  [This will match everything from the domain]
  • *dc=* [This will match everything and prevent any AD lookups - use only if absolutely required]

Notes:

  • Each string in the multistring registry key is placed on a separate line.
  • Wildcards such as "*" and "?" can be used.

Related Article:

  • Q10618 - MailMarshal Exchange is processing messages slowly.

This article was previously published as:
NETIQKB36504

To contact LevelBlue about this article or to request support:


Rate this Article:
     
Tags:

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.