We don’t use marketing cookies. Functional cookies ensure a smooth performance of our website. If you continue to use our services, you agree to the use of cookies. Data protection at JAM OK

FAQs & Knowledge Base

Welcome to our Knowledge Base. Search or browse through the topics below to find answers to your questions.

Categories: Exchange Server Toolbox | Show all categories

The Exchange Server Toolbox Service User needs to be a member of the following Active Directory groups:

Domain Admins
Domain Users 

In order to exclude specific file types from the "Delete Attachments" action you can add the following Regex expression to the action:

(?!.*\.(pdf|rtf)$).*\..*$ 

With this expression only PDF and RTF files would not be deleted.
You can switch the "pdf" and the "rtf" with any file type you want to exclude.
To add more types (for example docx) simply add a |docx.
To only exclude a single extension you can remove everything from the brackets but one file type.

Please note that you can install the Exchange Server Toolbox with the same license only on one machine at a time.

If you want to perform a step-by-step migration to the new server, processing mailboxes from the new server one by one, you can install the Exchange Server Toolbox demo on the new server for the duration of the migration.

To apply the configuration, export it under the Advanced Options of the Exchange Server Toolbox and import it on the same page on the new server.

The steps required to migrate the archive as efficiently and smoothly as possible differ depending on the type of archiving and the database used:

Database Archiving

MS SQL & MySQL

If the database is located on another server, you can continue to use it on the new server in parallel.

If the database is also located on the old server, proceed as follows:

  • Stop the Exchange Transport service on both servers.
  • Migrate the database to the new (or a third) server
  • Configure the new database server in the archive options of the Exchange Server Toolbox (also for the old server if it is operated in parallel for a certain period of time).

Integrated file-based database (Firebird)

If parallel operation is desired for a period of time proceed as follows:

  • Create a temporary new database file on the new server for archiving.
  • Continue with these steps only when you are about to shut down the old server
  • Stop the Exchange Transport service on both servers
  • Copy the old database file from the old server to the new server
  • Include the old database file on the new server in the archive options
  • Then import the temporary database file of the new server on the new server into the old archive under Main Archive -> Import

If parallel operation is not desired proceed as follows:

  • Stop the Exchange Transport service on both servers
  • Copy the old database file from the old server to the new server
  • Include the old database file on the new server in the archive options

File system archiving

With file system archiving, only the paths to the archived e-mails are stored in the database instead of the complete e-mail. To avoid a time-consuming import, it is also advisable to migrate the index database in this case.MS SQL & MySQL

MS SQL & MySQL

If the index database is located on another server, you can continue to use it on the new server in parallel.

If the database is also on the old server, proceed as follows:

  • Stop the Exchange Transport service on both servers.
  • Migrate the database to the new (or a third) server
  • Configure the new database server of the index database in the archive options of the Exchange Server Toolbox (also for the old server if it is operated in parallel for a period of time).
  • Then copy the folder of the old file system archive from the old server to a suitable location on the new server. You can either copy the contents of the old archive folder to the new one or create a dedicated folder for the alt data.
  • If you have created a dedicated folder for the alt data, configure it in the alternative search paths under Archive Options -> Archive Type.

Integrated file-based database (Firebird)

If parallel operation is desired for a period of time proceed as follows:

  • Create a temporary new index database file on the new server for archiving.
  • Create a new archive folder on the new server for file system archiving.
  • Continue with these steps only when you are about to shut down the old server
  • Stop the Exchange Transport service on both servers
  • Copy the old database file from the old server to the new server
  • Include the old database file on the new server in the archive options
  • Then import the temporary archive folder of the new server into the old archive under Archive Options -> Import on the new server.
  • The index data will be recreated for the emails in the temporary archive folder, the temporary index database file is no longer needed.
  • Then copy the folder of the old file system archive from the old server to a suitable location on the new server. You can either copy the contents of the old archive folder to the new one or create a dedicated folder for the alt data.
  • If you have created a dedicated folder for the alt data, configure it in the alternative search paths under Archive Options -> Archive Type.

If parallel operation is not desired proceed as follows:

  • Stop the Exchange Transport service on both servers
  • Copy the old database file from the old server to the new server
  • Include the old database file on the new server in the archive options

This option is only available if you have a local Microsoft Outlook installation. If Outlook is missing on the system this option is disabled.

The SCL value of an email can only be set if you are using an Exchange Server and even then only if there is no other email server between the Exchange Server and the Exchange Server Toolbox setting the value.

If an Exchange Server recieves an email with Exchange Server specific header content it will automatically ignore and overwrite these values.

All entries (Page 1 / 9)