Knowledge Base Home

Call Support

Search the Knowledge Base

Skip to end of metadata
Go to start of metadata


NetGovern Archive 6.x


In some cases, NetGovern Support engineers may apply a <fastprelude> tag to the jobs via an LDAP browser.  This can result in performance benefits, but with some caveats.  This article will attempt to explain this parameter in more depth.


Without the <fastprelude> parameter the software will function as follows:

  1. Fetch (via powershell) some meta-data such as Exchange version, profile culture, inbox folder ID, etc.
  2. Load all folders in the mailbox in order to iterate over them with a cursor.
  3. Archive items matching the filter/policy.

By enabling the <fastprelude> option on the job the software will function as follows:

  1. Skip powershell calls and assume en-US culture, Exchange version 2010 SP1+ , and a couple of other defaults.
  2. Create a search folder in the mailbox, apply filter/policy to it, wait several seconds for items to populate.
  3. Archive items found in the search folder.

As you can see from the above, the speed-up is gained from:

  1. Skipping the reading of the meta-data and just assuming some defaults.  This is useful if Powershell is very slow or simply not accessible in the environment.
  2. Not loading all the folders in the mailbox.  This is useful if there are some mailboxes with 1000's of folders and binding to each one is very time consuming.
  3. Using a search folder for filtering the content.  This a consequence of (2) above, and will require the use of a search folder to filter the mailbox since the job has skipped the loading of user folders.  The drawback of using this method is that it's very difficult to determine "completeness".  After creating the search folder & applying filtering criteria, the job will wait ~100sec for Exchange to populate the folder with results before processing them.  In mailboxes with large amounts of data, this time may not be sufficient to load complete set of results.

<fastprelude> may not be wise in every situation.  Let's examine cases where this safe to use and where it's not.

Open to using <fastprelude>NOT recommended for <fastprelude>
Using en-US culture on all your mailboxesMailbox culture is international (not always en-US)
On a recent version of Exchange (2010 SP1+)On version of Exchange 2010 pre-SP1
Archive, LiveMail indexing, and (usually) Remediation jobsMigration jobs
Job has a little data to process (eg. daily incremental archive)Job has a lot of data to process (eg. initial archive of a mailbox)

Assuming your scenario does not meet any condition in the 2nd column (above), then it's probably safe to use the <fastprelude> tag.


Archive access via OWA

If there is end-user access to the archives via OWA in your environment, there must be at least one archive job that runs without the <fastprelude> parameter. This is because OWA access to the archives is done via inbox folder ID, which is fetched via Powershell during the beginning of the archive job. If all archive jobs implement the <fastprelude> parameter then this information is never populated in LDAP, and thus the users will not receive an archive link in OWA.


The <fastprelude> tag is applied by inserting the tag into the maParameters of the relevant job in LDAP.  Values for this tag can either true or false

The tag is implemented at the connector level, so all jobs which leverage EWS to connect to the mailbox are eligible for this tag.

Help us improve!
Is this article helpful?
Is it well written?
Is the content complete?

  • No labels