Table of Contents
This knowledge base article will provide a guide on moving an installation of TaskCentre to another server. Migration of the TaskCentre Internal and SQL store will be covered.
For the SQL store, the recommended configuration is to have the TaskCentre Server installed on the same machine as SQL Server, this ensures a more reliable connection between the two should the network suffer any connection failures.
- Ensure that the new server has access to the same network resources as the old: File shares, database, mail server, FTP server,Printer drivers and HTTP server connections.
- Install TaskCentre on the new server and apply the latest hotfix.
- Using the Configurator:
- On any machines where TaskCentre event agents are installed, re-register them with the TC Server in its new location
- Make sure any tool specific connectors such as Crystal Reports have all the runtimes installed.
- Using the ODBC Data Source Administrator (32 bit) recreate any system DSN that the existing installation uses. Remember to include any systems DSN’s used by automated Crystal Reports.
The TaskCentre store which contains all created task and configuration data is now ready to be moved. See below for an outline on how to transfer an Internal or SQL store.
INTERNAL STORE (click here for SQL store)
By default this store is located locally with c:\. If TaskCentre is being installed on a new machine then the locally stored data will need to be migrated across.
- On the new machine use the TaskCentre Configurator to create an Internal Store.
- Stop the TaskCentre services on both the new and existing servers. This can be done by opening command prompt as administrator and typing the following:net stop tcserver
- On the old machine locate the TaskCentre store of the original TaskCentre installation, the default path is C:\ but to be certain the location can be checked by locating the ‘StorePath’ key of the registry.Open the registry and browse to the following path:On x86 32bit systemsHKEY_LOCAL_MACHINE\SOFTWARE\Orbis Software\TaskCentre
On x64 64bit systemsHKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Orbis Software\TaskCentre
Note: The path is displayed in the ‘Data’ column.
- Browse to the specified path and first create a backup of the folder and store in a safe place. Copy the contents to where the Internal Store is saved on the new machine. Overwrite the existing files.
- Restart the TaskCentre service on the new server by typing the following in command prompt:net start tcserver
- The TaskCentre store has now been transferred to the new machine. Load the TaskCentre client and check all tasks are present. Under the global configurations make sure that any database and mail server connections are still pointing to the correct locations.
This store is located within SQL Server either on the same machine as TaskCentre or on a separate one. There are two methods of migration:
A) If TaskCentre and SQL Server are being installed on a new machine together, the SQL store will need to be migrated along with the SQL Server databases.
B) Alternatively, if only TaskCentre is being installed on a new machine then the SQL store does not need to be migrated. Instead TaskCentre is pointed at the location on the network where SQL Server is installed by using the configurator.
Configuration A – TaskCentre Server and SQL Server on the same machine
- Within SQL Server on the old machine, Backup the TaskCentre store along with all databases in use noting where the backups are being saved to. The default save location may be similar to the following:
C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\BackupNote: TCDatabase’ is the default name given to the store when TaskCentre was installed.
- Copy the backups to the new machine.
- Within SQL Server on the new machine, Restore the TaskCentre store along with the databases using the backup files.The TaskCentre configurator is now used for the final step which is to point TaskCentre to the restored SQL store.
Configuring the SQL Store
- Load the TaskCentre Configurator. Expand the Server tree in the navigation pane, select the Store folder then select Configuration.
- Tick the box Change store configuration and select Connect to / Create an alternative Microsoft SQL Server Store.
- Select Next.
- Specify the location of the SQL Server. A server name or IP address can be provided each with or without an instance name. Alternatively, select Localhost if SQL Server is installed on your local machine.
- Provide the name of the store in SQL Server, for example TCDatabaseNote: The name must match the TaskCentre store in SQL Server so that TaskCentre will utilise the restored data. If there is a name mismatch a blank SQL store will be created.
- Choose a method of authentication and select Next.
- Select Save and close the configurator.
The TaskCentre store has now been transferred to the new machine along with all databases in use.
Load the TaskCentre client and check all tasks are present. Under the global configurations make sure that any database and mail server connections are still pointing to the correct locations. Use the TaskCentre configurator to re-register the SQL Server event to the new location of the TaskCenter server.
Configuration B – TaskCentre Server and SQL Server on separate machines
All that is required for this configuration is to point TaskCentre at the existing SQL Store on a networked SQL Server.
Two items of information are required, the location of where the SQL Server is on the network and the name of the TaskCentre Store saved within SQL Server. The default name of the store given during setup is ‘TCDatabase’.
As with the procedure outlined above, “Configuring the SQL Store”, during the setup provide the details of the SQL Server location on the network and the TaskCentre Store name.
Once complete, load the TaskCentre client and check all tasks are present. Under the global configurations make sure that any database and mail server connections are still pointing to the correct locations. Use the TaskCentre configurator to re-register the SQL Server event to the new location of the TaskCenter server.