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

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:

After that, please check that file and folder paths in the archive and the ruleset are still valid.

The steps required to migrate the archive as efficiently and smoothly as possible differ depending on the type of archiving and the database used. This tutorial assumes that you have already installed the Exchange Server Toolbox on the new server. 

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.

  • In this case you only have to configure the database connection on the new server under Main Archive  | Archive Type 

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 under Main Archive  | Archive Type (also for the old server if it is operated in parallel for a certain period of time).

Integrated file-based database (Firebird)

You can find the location of the database file on the old server under Main Archive | Archive Type.

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

  • After the installation on the new server go to Main Archive | Archive Type and set the archive type to "Database". A new, temporary database file will be created
  • 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
    • Select the old database file on the new server under Main Archive | Archive Type | Configure integrated database
    • Import the temporary database file from the new server. Select the file under Main Archive | Import | Select source integradted database archive store. The entries from this temporary database will now be included into the working database

If parallel operation is not desired proceed as follows:c

  • Stop the Exchange Transport service on both servers
  • Copy the old database file from the old server to the new server
  • Select the old database file on the new server under Main Archive | Archive Type | Configure integrated database

File system archiving

With file system archiving, only the paths to the archived emails are stored in the database instead of the complete email. The archived  emails are being stored in an archive folder.

You can find the location of the archive folder under Main Archive | Archive Type | File system archiving options | Archive root folder.

MS SQL & MySQL

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

  • Configure the database connection on the new server under | Main Archive | Archiv Type
  • 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 archive folder from the old server to the new server
    • Copy the files of the old archive folder into the archive folder of the new server. Thanks to the parallel mode the index database already has the entries of the old archive folder

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

  • Configure the database connection on the new server under | Main Archive | Archiv Type
  • Continue with these steps only when you are about to shut down the old server
    • Stop the Exchange Transport service on both servers
    • Migrate the database to the new (or a third) server
    • Configure the new index database connection under Main Archive | Archiv Type
    • Copy the old archive folder from the old server to the new server
    • Copy the files of the old archive folder into the archive folder of the new server. Thanks to the parallel mode the index database already has the entries of the old archive folder

Integrated file-based database (Firebird)

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

  • After the installation on the new server go to Main Archive | Archive Type and set the archive type to "File system". A new, temporary archive folder and a temporary index database file will be created
  • 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 archive folder and the  old database file from the old server to the new server
    • Select the old archive folder under Main Archive | Archive Type | File system archiving options | Archive root folder
    • Select the old database file under Main Archive | Archive Type | Configure integrated database | Database file:
    • Import the temporary archive folder (as in the archive folder temporarily created on the new server) by selecting it under Main Archive | Import | Choose your type if import: File System | Select file type for import: Old filesystem archive. Since this creates the index entries in the new index database the temporary index database file is not needed.

If parallel operation is not desired proceed as follows:

  • Stop the Exchange Transport service on both servers
  • Copy the old archive folder and the  old database file from the old server to the new server
  • Select the old archive folder under Main Archive | Archive Type | File system archiving options | Archive root folder
  • Select the old database file under Main Archive | Archive Type | Configure integrated database | Database file:

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.

Refuse mail is only available for incoming (recieve) emails. This means that the Exchange Server is currently recieving the email but has yet to accept it. The rule action allows to refuse to accept the email and return an error message to the sender.

Do not deliver mail does not depend on the current status of the email. The rule action will have the Exchange Server quietly discard the email without delivering it.

Incoming (recieve) means that the email is currently incoming and has not yet been processed. It can still be rejected at this point allowing for the rule action "Refuse Mail". This means that your Exchange Server will refuse to accept the email.
Since the emails have not yet been accepted by the Exchange Server they can not be modified by rules. Any rule to modify the email in any way has to be created in the Incoming (accepted) rules.

Incoming (accepted) means that the email has already been accepted by your Exchange Server. It can no longer be rejected and thus the rule action "Refuse Mail" is no longer available.