Migrating TEKLYNX CENTRAL – Instructions

Target Audience: Advanced User IT Manager
Article #: 13710

Summary

This article explains the process for migrating TEKLYNX CENTRAL from one production server to another. It also covers the process for migration to an Azure Active Directory (AAD) virtual machine (VM).

Preparation

Before beginning the migration process, you will need to request a temporary license key for TEKLYNX CENTRAL from Efficient Business Integrators at support@efficientbi.com.

Instructions

PART 1 – CREATE A NEW SERVER OR AZURE VM

Create a new server or Azure VM for the SQL database. If you plan to also install TEKLYNX CENTRAL onto this server or VM as well, make sure it complies with the system requirements laid out in Section 1-2 of the TEKLYNX CENTRAL INSTALLATION GUIDE appropriate to your software version:
TEKLYNX CENTRAL v6.0 – TEKLYNX CENTRAL 6.0 INSTALLATION GUIDE.
TEKLYNX CENTRAL v5.1 – TEKLYNX CENTRAL 5.1 INSTALLATION GUIDE.
Copy the production TEKLYNX CENTRAL databases which include LABELENET, LABELARCHIVE, MSGS, and UMSS. Restore them to the new server or VM.
Copy your company’s production label database and restore it to the new database server or VM.

PART 2 – INSTALLING TEKLYNX CENTRAL

TEKLYNX CENTRAL can be installed on the same server or VM used for the database set up in Step 1, above.

If you will be installing TEKLYNX CENTRAL onto a DIFFERENT new server or VM, ensure that it complies with the system requirements laid out in Section 1-2 of the TEKLYNX CENTRAL INSTALLATION GUIDE appropriate to your software version:
TEKLYNX CENTRAL v6.0 – TEKLYNX CENTRAL 6.0 INSTALLATION GUIDE.
TEKLYNX CENTRAL v5.1 – TEKLYNX CENTRAL 5.1 INSTALLATION GUIDE.

Install Microsoft Windows Internet Information Service (IIS). If installing IIS 8.0 or later, install the web server.

Also make sure that the following features are installed as well:

Directory Browsing
HTTP Errors
HTTP Redirection
ASP.NET
.NET Extensibility
ISAPI Extensions
ISAPI Filters
HTTP Logging
Logging Tools
Request Monitor
Tracing
Customer Logging
Windows Authentication
URL Authorization
Request Filtering
Static Content Compression
IIS Management Console

Install TEKLYNX CENTRAL onto the new server or VM.
• Enter the server name for the migrated SQL database.
• Enter the SQL credentials for database access from TEKLYNX CENTRAL.

Using the temporary key, activate the new TEKLYNX CENTRAL installation. Instructions for activating TEKLYNX CENTRAL can be found here.

PART 3 – MIGRATE PRINTERS

Begin migrating the printers by copying the active printers list from the production server. This list will be located between the <Printers> tag on C:\Users\Public\Documents\Teklynx\SENTINEL\tkxcs.xml. Paste the copied names into the same file on the new server or VM.

Next, copy C:\ProgramData\Teklynx\CODESOFT\User.ini from the production server and paste it over the same file on the new server or VM.
Search Windows for Print Management. Run this program as Administrator.
At the top of the folder list, right-click Print Management and select Migrate.
On the next screen, choose Export printer queues and printer drivers to a file.
On the following screen, select This print server (your server name).
Click Next and create a filename and destination.
Copy this new file and paste it to the desktop of the new server or VM
Locate Print Management on the new server or VM, again running as Administrator.
Select Import printer queues from a file, choosing the file you just created as the target and complete the import.

PART 4 – MIGRATE SENTINEL CONFIGURATIONS

Launch the Services app in Windows and stop the Label Printer Manager service.
Copy the following files from C:\Users\Public\Documents\Teklynx\SENTINEL from the production server and paste them onto the new server or VM:
a. Mapper.ini
b. Sentinel.xml
c. Tkxoutput.xml
d. Tkxinput.xml
e. Users.xml
Copy all of the files from the C:\Users\Public\Documents\Teklynx\SENTINEL\Maps directory on the production server and paste the to the same path on the new server or VM.
Restart the Label Print Manager service.

PART 5 – MIGRATE CODESOFT CONFIGURATIONS

You will need to move any supporting graphics, documents, UDLs and etc. to the new server.

One the original server, edit the file C:\ProgramData\Teklynx\CODESOFT\User.ini
Copy the [PATH] section and replace the same section in the new server or VM’s User.ini

[PATH]
Document=C:\Program Files (x86)\Teklynx\CODESOFT 2019
Image=C:\Program Files (x86)\Teklynx\CODESOFT 2019
Odbc=C:\Program Files (x86)\Teklynx\CODESOFT 2019
Describer=C:\Program Files (x86)\Teklynx\CODESOFT 2019
Global=C:\Program Files (x86)\Teklynx\CODESOFT 2019
FilePrint=C:\Program Files (x86)\Teklynx\CODESOFT 2019
Data=C:\Program Files (x86)\Teklynx\CODESOFT 2019
SpecificFormulas=C:\Program Files (x86)\Teklynx\CODESOFT 2019
OLEDBCnx=C:\programdata\Teklynx\codesoft\datalink
Galleries=C:\Users\Public\Documents\Teklynx\CODESOFT\Galleries\
Patterns=C:\Users\Public\Documents\Teklynx\CODESOFT\Patterns\
Shapes=C:\Users\Public\Documents\Teklynx\CODESOFT\Shapes\
Templates=C:\Users\Public\Documents\Teklynx\CODESOFT\Samples\Compliance\

If any of these folders do not exits on the new server, create the missing folders on the new server or VM.
Copy all of the files from each of the corresponding folders on the old server into these new folders.

NOTE: the most important files to copy over are in the:

Image Path: these are the images used on the label templates
OLEDBCnx path: this path will have database connections that label templates use.

Restart the Label Print Manager service.

PART 6 – MODIFY UDL SETTINGS

Open CODESOFT and Select Tools -> Administrator OLE DB.
Select a connection and click Edit.
Make sure each connection’s settings are correct. If needed, change the server name, database, and credentials.
Click Test Connection to verify.