CoLOS Installation and Migration Guide
CoLOS Installation and Migration Guide
Table of Contents
Overview ........................................................................................................................................... 4
Prerequisites ........................................................................................................................................... 4
Installation – New Install of CoLOS Product Suite (Base, Line, Factory & OEM) ................................... 4
On a Different Computer...................................................................................................................11
References ......................................................................................................................................... 14
Revision History
Overview
This guide provides information on installing CoLOS® and helps you migrate from older versions of CoLOS.
Target Audience
The primary target audience for this document is Field Service Engineers, Help Desk, Presales, and CAT
implementers. It can be used by anyone who performs installation of CoLOS or migrating from older
versions of CoLOS.
System Requirements
The latest updated system requirements are available as part of the "Release Notes" of the targeted
release version.
Prerequisites
• The CoLOS Product Suite Installer or Freeware Installer, or Terminal Installer.
• Other optional dependent installers like OPC DA Installer, Third-party Driver installer, MS SQL Installer.
• The logged-on user needs Windows Administrator rights to install CoLOS as a windows service.
• Prerequisites for LDAP/SAP Connectors/Third-party drivers.
Installation – New Install of CoLOS Product Suite (Base, Line, Factory & OEM)
CoLOS provides a windows installer and follows on-screen instructions. It can be installed as a server or
client. The following are the steps for installation.
2. Copy the NGW folders from the source computer (e.g., Where V5 is installed) to the new target
computer (e.g., Where V6 is to be installed) under "C:\Program Data\Markem-
Imaje\NGW\<oldversion>" (Create the folder structure if it does not exist in the target computer).
The service names are "Markem-Imaje Connectivity vs." and "MI Settings ServiceVX.X." Stopping the
CoLOS Services on the source computer will avoid port conflicts and prevent printer
communication from both CoLOS instances.
4. If the user wants to continue production and move only specific lines/devices onto the new CoLOS,
Disable the devices to close the communication ports (using CoLOS) that are getting migrated.
5. Pre-Installation Steps
If CoLOS is configured to use ODBC in Job sources, Remote Data sources, OEE SKUs (from
v6.1), the DSNs used must be created on the target machine with the same name,
credentials, architecture (32bit or 64bit), and in System DSN. If the ODBC drivers are missing
on the target, Install the drivers having the same version as the source computer.
The DSN names can be located from the Properties of the created Job Sources, Remote
Data Sources, etc., from the Administrator.
To create/view ODBC DSNs on the computer, Launch Start > Windows Administrative Tools
> ODBC Data Sources(32bit) or ODBC Data Sources(64bit).
b. Create MS-SQL connection used for Promotional coding, OEE, Printer performance, CAPI
(Data Management), and Mark & Read. (Except for Promotional coding, all others are for
v6.1 onwards)
i. If MS-SQL is in the local computer, create the database instance with the same name and
credentials. Import the data from the old to the new computer.
ii. If MS-SQL is in a separate computer, ensure the new computer has access to it.
c. Create a folder structure and copy files onto the target computer for
• Scheduled Backup task (Looks up for MIB file)
• Scheduled Import task (looks for CSV and text files)
• Stream data source (For unique codes used in Promotional Coding)
• Input Nodes – Directory watcher (looks up for job id files, executables, and batch
files)
• Additional Repositories (Created for ITFs, Settings, Calendars, Custom codes, and
Device logbooks)
d. If any of the folders/files in point C use a UNC/Network path, ensure the connectivity service
account has access to those. If not accessible, contact the Customer - IT team.
e. If CoLOS uses any Windows drivers, the target computer should have drivers with the same
version (recommended) and same name/configuration.
f. If Sap RFCs are used, Install SAP .NET Connectors for the target computer (32 or 64 bit based
on the OS)
g. Ensure that new CoLOS clients and servers are present in the same network domain.
h. If the credentials of CoLOS services on the source computer have been modified, ensure
the same credentials are used on the target computer (post-installation)
6. Launch the installer on the target computer and select the migrate settings option
ii. If there are no certificate changes, the new installation will create new OPC UA Server
and Client certificates. The new certificate must be exported and copied to the
Clients connecting to this CoLOS OPC UA Server and to the Servers where CoLOS
reads the OPC UA tags.
b. All other endpoints (For source CoLOS versions from CoLOS 6.2.5)
If the default certificates are changed for any setting (refer to the screenshot below),
export the certificates from the source computer, copy them to the target computer, and
import them using the CoLOS Administrator.
9. If only certain devices/lines are migrated, disable all other devices on the target computer.
10. Launch MIConfig.exe from the installation folder and ensure the options are checked as in the old
version.
From CoLOS Administrator > System > Properties > License, verify all the features used in the older
version of the software are installed. Green checkmark indicates installed feature and
indicates feature not installed/available.
The ODBC connection status for Job sources/Remote Data sources and repository can be checked
by ensuring a green tick mark on the icons like the one below.
c) Verify Scheduler tasks – Backup and Import are functioning by running manually.
d) Verify the CoLOS Database is configured correctly (For migrations from v6.1 and above)
If MS-SQL is used, then from CoLOS Administrator > System > Database Connection > Configure
Database and verify ‘Test connection’ is successful.
Connect to the server from CLI, OPC UA, and Web Production panel and if there are any issues,
see the Troubleshooting section for the most common issues.
1. On the existing CoLOS, disable the printers which are being migrated
2. Ensure that the user has the 'Administrator' privileges.
3. Follow instructions on-screen and choose the "Migrate Settings" option and complete the
installation
4. On the new installation, enable only the migrated printers.
5. Change the port configuration
a. Run CoLOS Administrator
b. Got System > Properties > Ports
a. Assign a new port number to the ones which are marked as editable (It is
recommended to add 1 to the existing port)
b. Reconfigure the clients connecting to this instance using the new port.
6. Verify the installation by following the steps in the "Migration to a Different computer" section.
7. If the default certificates for OPC UA are changed, copy the certificates from the old NGW folder
as mentioned in the 'Secure End Points' step of the 'Migration to Different computer' section.
NOTE
CoLOS MSSQL Database will be backed up and restored only if the SQL instance is on the same
machine as CoLOS and by specifying /DBRestore:True option.
On a Different Computer
If the data is to be restored on a new computer,
1. Verify the target version of CoLOS belongs to the same Minor release as the backed-up CoLOS
version.
2. Verify the Migration Checklist in the Migration to a different computer.
3. Back up the data using the steps outlined on the CoLOS Administrator Help.
4. Copy the backed-up file to the target computer
5. Restore the data using the steps outlined on the CoLOS Administrator Help.
6. Verify the installation using the steps in Migration to a different computer.
Maintenance Upgrades
Upgrade to a higher maintenance release
1. To install maintenance releases above CoLOS 6.2SP, launch the installer and follow on-screen
instructions.
2. For versions below 6.2SP
a. Take a backup of the existing installation by copying the C:\ProgramData\Markem-
Imaje\vX.X folder.
b. Uninstall the existing version
c. Install the new maintenance release
2. CoLOS v6 fails to open Images created in v5.4 for SLC 350 containing Circular fields.
• Open the ITF using notepad
• Change the order of tags from
<IsHidden>false</IsHidden>
<Logged>false</Logged>
To
<Logged>false</Logged>
<IsHidden>false</IsHidden>
6. Note that the Device Logbooks on the Default repository, Generated System Logbooks, and
Promotional coding production data (codes sent, etc.) are NOT migrated. If required, users are
advised to take a backup from the old installation manually.
7. For migrations from v6.0, if SAPRFC and Email Alerts are used, reconfigure the Credentials for both
from the Administrator.
CAT Migration
CAT projects must be opened in the newer Toolkit version, and the Migration is automatically done.
The Certificates used for HTTPS and OPCUA must be copied and configured. The certificates can be found
in "C:\ProgramData\Markem-Imaje\CA\v6.X\Certificates".
See the "Certificate Management in CoLOS" document for more details on configuring certificates.
If any of the Integration service ports are hardcoded in the workflow, update to the new port numbers
applicable for the target version.
Solution #1:
1. If the Migration is on the same computer, ensure the old CoLOS service is not running.
2. If the services are intended to run side by side, verify that "Web Server Production Panel Port 1" and
other ports are given a new available port number.
Issue: The Web Production panel throws the error 'The client
machine has no configured groups'
This error can happen when the Web production panel is configured for restricted access for groups. The
restrictions are historically added using the 'Host Names' of the client computer. Modern browsers are
beginning to use IP addresses to identify the origins of the request instead of hostnames. It is recommended
to configure both IP and Hostnames in the Group restrictions for the Web production panel.
Solution #1:
1. Add the client IP address and the hostname to the Allowed hosts.
2. If step 1 does not solve the problem, proceed with the following
3. CoLOS supports only IPv4 versions; if the client has enabled IPv6, disable IPv6 on the client and try
connecting again
To Disable IPv6:
Solution #1:
• Make sure the ports are migrated correctly for CAT services. See section Migrating CAT projects.
Solution #2:
• Clear the browser cache and retry.
Issue:
• CoLOS service fails to start or connects only for a few
minutes.
• CoLOS Administrator/Designer cannot connect even though
the service is running.
Solution #1:
Refer to the CoLOS Connection Troubleshooting guide for detailed information. CoLOS uses several
network ports for its communication with clients. Ensure the local IT or firewall does not block the ports. The
detailed list of ports used by CoLOS can be found in the "CoLOS System Requirements and port list"
document.
References
1. CoLOS Connection Troubleshooting
2. Installing and configuring Internet Information Services
3. CoLOS System requirements and Port list
4. Certificate Management in CoLOS