Section 1

Section 2
Configuring for First Use

Section 3
Changing Admin Password

Section 4
Creating Accounts

Section 5
Global Component Settings

Section 6

Section 7
Log Files

Section 8
User Interface Settings

Section 9
Database Connections

Section 10
Non-Standard Ports

Section 11

Section 12

Section 13
Tracking and Recipient Profiles

Section 14
Editing INI Files

Section 15
Distributed Components

15.2 Moving Components

15.2 Moving Components Continued

15.3 Server Aliases and Proxy Setup

15.3 Continued

Section 16
User Interface Branding

Section 17
Evaluation Mode

Section 18
International Character Sets

Appendix A
Standard Default Ports

15.2.3 Moving the Maestro Tracker Component to Another Server

It is critical to remember that moving the Maestro Tracker component to a different server must be well thought out and planned. The problem is that all messages that have been sent while the Maestro Tracker component was still installed on the old server include message tracking code with the old server name. If the Maestro Tracker component is shut down and de-installed on that old server, all tracking events from those messages will be lost. Even worse, click-through tracking links will no longer work. If a recipient clicks on a click-through tracked link that is connected to the old Maestro Tracker component's host name, then the recipient will receive a "Host not found" or "Page not found" error -it will look like a broken link - instead of being routed to the actual link target. Therefore be very careful when moving the Maestro Tracker component to a different server.

Under normal production conditions, this should never be done. But if necessary, move the component only if the last tracked e-mail job has occurred some time in the past and there is no more concern for tracking events that get lost and broken links. Of course changing the DNS registration of the host name can also solve this problem. For example, if the host name for the Maestro Tracker component was previously DNS registered to point to the IP address of the old server, than change the registration and let it point to the address of the new server instead. To users accessing links this will appear like there was no change at all. Keep in mind, however, that the propagation of a DNS change always takes a few days, so in the interim period, the averse effects of moving the component may still happen.

If it really becomes necessary to move the Maestro Tracker component follow these steps:

1. Install the Maestro Tracker component on the new server. Do not start it at this stage.

2. Shut down the LISTSERV Maestro installation where the old Maestro Tracker is running.

3. Copy the following files and folders (including all files and subfolders) to the new server:

\Program Files\L-Soft\Application Server\trk\tracker.ini
\Program Files\L-Soft\Application Server\trk\data

This will overwrite some files and folders on the new server. Depending on the installation, these paths may be slightly different on one or both of the servers.

4. Edit the following file of the Maestro User Interface component, which may be installed on an entirely different server!

\Program Files\L-Soft\Application Server\lui\lui.ini

In the file edit the "TrackerHost" entry so that it contains the host name of the new server where Maestro Tracker will be running. If the DNS registration of the old host name also changed to point to the new server, then this is not a necessary change, since the actual host name is not changed - it only points to a different server.

5. On the old server, use Windows' "Add/Remove Programs" panel to start the maintenance setup of LISTSERV Maestro. In the setup, choose "Modify" and deselect the Maestro Tracker component, so that it is uninstalled. Start the LISTSERV Maestro installation on the new server (thus starting the new Maestro Tracker component).

6. Start the LISTSERV Maestro installation on the new server (thus starting the new Maestro Tracker component).

15.2.4 Moving the Database External Component to Another Server

Install the database software on the new server and start the program. Follow the instructions in Section 9 Database Connection with the exception that instead of moving from one type of database to a different one, move between two databases that are on different servers. These may actually be the same type of database (the database vendor, version, and such).

Back One Page | Forward One Page