Knowledgebase

This error is caused by missing access rights to a key file. This is located in the folder C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys. You can either change the permissions on the entire folder or check which file needs the permissions.

To find out which file this is, you can use window's own "Procmon". This shows all file accesses. Open the program and set the filter "Path contains C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys". Then check which file the "Jam.EST.Archive.Writer.Service.exe" process tries to accessand allow access to this file.

We have planned a quarantine function for the future. Until this is implemented, you can, for example, set up a quarantine mailbox and deliver emails that have been detected as spam to it. To do this, you can use the following rule:

"Mail is spam" condition. To do this, you need to set a spam score. By default, the value 5 is recommended here.

Action "Forward copy to SMTP server". Here you specify the e-mail address of the quarantine mailbox and the SMTP server connection.

Action "Do not deliver email". This will delete the original email and deliver only the copy to the quarantine mailbox. It is important that this action is listed last.

Alternatively, you can use this action instead of "Forward copy to SMTP server":

"Modify recipients (SMTP)" action. Delete the existing recipients here and specify the quarantine mailbox as the recipient.

This action is useful if the quarantine mailbox is on the same SMTP server as the original recipient.

To complete the installation process of the Exchange Server Toolbox, the installing user needs administrative rights. This is necessary because services need to be set up and firewall rules need to be created during the installation.

Additionally, the user creating the Active Directory user must be a member of the "Account Operator" group.

These permissions are required to ensure that all necessary configurations and security policies can be correctly applied.

The integrated versions of ClamAV and SpamAssassin are not updated manually, but with our software updates.

The Active Directory user under which the Exchange Server Toolbox service runs must be a member of the following groups:

• Administrators
• Domain Admins
• Domain Users

The user can be created with all necessary permissions during the installation. If you want to create a user manually, you need to add them to the above-mentioned groups.

These group memberships are necessary to ensure that the service has the required permissions to function properly.

To display the content of TNEF emails, the Exchange Server Toolbox requires the following files:

• Microsoft.Exchange.Data.Common.dll
• Microsoft.Exchange.Data.Transport.dll

The Exchange Server Toolbox looks for these files either in the folder [ExchangeInstallationFolder]\Public or in the installation folder of the Exchange Server Toolbox.

If the files are not found, ensure they are correctly installed and located in the specified directories.

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.

Attention: If the old server still has an old Exchange Server Toolbox version installed, please follow the steps described in the following article before migrating the settings / archive:
https://knowledgebase.jam-software.com/7666

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 there is no other email server between the Exchange Server and the Exchange Server Toolbox setting the value.

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

Ensure that no other email servers are affecting the SCL value before the email reaches the Exchange Server.