Migration of NoSpamProxy versions 10.x and 11.x
To move versions 10.x and 11.x to another computer, proceed as follows:
- Copy the Intranet Role.config and the license.xml to the new computer.
- Create the directory “C:\ProgramData\Net at Work Mail Gateway\Configuration” and copy Intranet Role.config and license.xml into it.
- Customize the Intranet Role.config.
- Install the SQL server.
- a) Backup the database files and restore them to the target SQL server OR
b)Move the database files to the new directory and mount them in the SQL server. - Execute the NoSpamProxy Setup.
- Connect the Intranet role to the Gateway role.
- Then check all previously set passwords and certificates and reassign the connectors.
The steps in detail
- Copy the Intranet Role.config and license.xml to the new computer.
- First, stop the NoSpamProxy services on the source computer and then stop the SQL database instance. These can usually be found under the Windows services as “SQL Server (NOSPAMPROXY)”. Then stop all Net at Work Mail Gateway services.
Copy the Intranet Role.config and license.xml from “C:\ProgramData\Net at Work Mail Gateway\Configuration” to the target computer.
Please copy ONLY the mentioned files from the directories, otherwise problems could occur during installation. - Create the directory “C:\ProgramData\Net at Work Mail Gateway\Configuration” and copy Intranet Role.config and license.xml into it.
Customize the Intranet Role.config.
Open the file with an editor, such as Notepad, and search for the following entry:
<connectionStrings configProtectionProvider="DataProtectionConfigurationProvider">
<EncryptedData>
<CipherData>
<CipherValue>AQAAANCMnd...==</CipherValue>
</CipherData>
</EncryptedData>
</connectionStrings>
Modify it to look like this:
<connectionStrings>
</connectionStrings>
Search the file for
encryptedPassword=
and change entries similar to
encryptedPassword="AQAAANCM...W9b17"
in
encryptedPassword=""
Do the same for the entries
tlsCertificatePin="AQAAANCM...W9b17"
and
tlsCertificateThumbprint="AQAAANCM...W9b17"
and
password="AQAAANCM...W9b17"
and
privateKey="AQAAANCM...W9b17"
Save the file.
- Install the SQL Server.
Now install the SQL Server in the version you want starting with SQL Server 2008. Do not forget to install the administration tools, especially SQL Management Studio. - a) Back up the database files and restore them to the target SQL Server.
With the help of SQL Management Studio you first create a backup of the SQL database “NoSpamProxyAddressSynchronization” on the source server.
Right-click on the database and select “Task / Backup”. A dialog opens.
Leave everything there as it is in the standard system and simply add a “disk” and the corresponding path to the backup file in the lower section.
Then start the backup. Copy the resulting backup file to the target server and restore it.
To do this, right-click on “Databases” in the SQL Management Studio of the target server and select “Restore Database”. A dialog opens.
First select “Device” and add a new “File” in the dialog that appears. This file is the backup file that has just been copied. Now start the recovery.
b) Move the database files to the new directory and mount them in the SQL server.
The SQL database files are usually located in the path “C:\Program Files (x86)\Microsoft SQL Server\MSSQL.XXXX\MSSQL\Data” or “C:\Program Files\Microsoft SQL Server\MSSQL.XXXX\MSSQL\Data”. You can recognize them by the name that begins with NoSpamProxy.
Copy both the NoSpamProxyAddressSynchronization.mdf and NoSpamProxyAddressSynchronization.ldf files to the target computer.
Now move the database files to the desired directory. This does not necessarily have to be the default directory of the SQL server. Then open SQL Management Studio.
After logging on to the server, right-click Databases and select Add (or Databases and Attach).
In the following dialog, add the first database file from the desired directory.
The associated log file is automatically recognized. - Execute the NoSpamProxy Setup.
Now start the setup of the NoSpamProxy. Be sure to select Advanced Installation.
When prompted for which SQL Server is used, select that an SQL Server is already installed and set the appropriate connection parameters. The setup then recognizes all further configuration files and adapts them. - Connect the Intranet role to the Gateway role.
As soon as the setup has been completed successfully, reconnect the intranet role under Gateway Components to the gateway role and, if necessary, to the web portal.
To do this, delete the existing connections, then restart the Intranet role and reconnect it. - Then check all previously set passwords and certificates and reassign the connectors.
With the conversion, the device-dependent encrypted passwords were deleted or can no longer be decrypted. This applies in particular to the password for protecting sensitive data, with which the private keys of S/MIME and PGP are protected.
Set the old password again in the interface to restore access. The same applies to SSL certificates configured in the receive connector.
Therefore, check all passwords and SSL certificates that were previously stored and reset them.
In addition, the send and receive connectors must be reassigned to corresponding gateway roles.
Note
The gateway role and the web portal get all information from the intranet role. Therefore, they are simply reinstalled during an upcoming migration.