Knowledge Base

NiceLabel installation checklists

Before you begin the installation of NiceLabel software, make sure to follow the guidance in the installation guides about the system requirements. NiceLabel software has some dependencies on other components that have to be satisfied before the installation.

Please see the requirements published on NiceLabel web site first, they precede information from this KB article.

This topic provides pre-installation and post-installation checklists for NiceLabel software.

Pre-installation checklist

For NiceLabel Control Center

Available access to the Windows accounts with administrative privileges and SQL system administrator

WARNING. When installing the software to multiple servers, all servers must be managed through the same Windows domain.

To install NiceLabel software, you must have access to the user with administrative privileges:

  1. On the Windows server with Internet Information Services role where you will install Control Center web site.
  2. On the Windows server with Microsoft SQL Server role where you will install the Control Center database, so the users EPM_DBADMIN and EPM_USER can be added as local Windows users. The provided Windows account must be a domain user (not local Windows user), and must be member of local user group Administrators.
  3. On the SQL Server, so the Control Center database can be added to the SQL Server. The entered user must have the sysadmin server role defined on the SQL server. This must be as SQL user name, usually "sa".

NOTE. If the Windows user account you use to install Control Center has administrative privileges also on the Windows machine with SQL Server and the SQL Server itself, then you need just this one user name/password (and you do not need information from steps 2 and 3).

Internet access for the activation process

You will need the Internet access to activate NiceLabel Control Center. You do not need to allow Internet connection to the Windows Server where you have installed Control Center.

Meeting prerequisites for the Microsoft SQL Server
  • The Control Center database requires that SQL Server is installed with case-insensitive collation.
  • Make sure to enable the SQL Server Browser service, if you use instance names. This will make the instances visible to external clients.
  • Make sure to enable the TCP/IP protocol for your SQL Server, if the SQL Server will be installed on a different machine than Control Center Web page. Start SQL Server Configuration Manager, expand SQL Server Network Configuration and enable the TCP/IP for the your server/instance.
  • Make sure the inbound connection towards the SQL Server is enabled. Start Windows Firewall with Advanced Security and add a new Inbound Rule to allow the program sqlservr.exe accept incoming connections. You will find the program in the folder C:\Program Files\Microsoft SQL Server\MSSQL<version_number>.SQLEXPRESS\MSSQL\Binn.
  • If the RPC port on the server that hosts your SQL database is blocked, the installation of Control Center fails. Please check that the RPC port on your SQL server is open. The RPC port number is usually 135 or 445, depending on your system configuration.
Installing Control Center on a Windows Server with enabled Remote Desktop
Services (Terminal Services) role

To ensure that an application is installed correctly to work in a multiple user environment, the Remote Desktop Server must be switched into Install mode before the applications are installed on server.

Do the following:

On Windows Server 2012 or Windows Server 2012 R2

  1. Open Control Panel.
  2. Select Programs.
  3. Select Install Application on Remote Desktop Server.
  4. Browse for the installation executable, click OK and follow on-screen instructions.

On Windows Server 2008 or Windows Server 2008 R2

  1. Open Control Panel.
  2. Select Install Application on Terminal Server.
  3. Browse for the installation executable, click OK and follow on-screen instructions

NOTE. This tool is available only when installing the terminal server. It will automatically put terminal server into execute mode when application installation is complete.

Making sure the port 8080 TCP is available on the computer where you intend to install the Control Center

Verify that the port 8080 TCP is not in use by some other application running on the same machine. NiceLabel Control Center will occupy port 8080 to allow WebDAV access to the Document Storage. If port is already in use, you will have to choose some other port for Document Storage Server WebDAV communication. The entered user must have the sysadmin server role defined on the SQL server.

You can run Windows command-line utility netstat.exe to see list of open ports on the computer.

Do the following:

  1. Open Command Prompt window.
  2. Type in the following command:

    netstat -ano

  3. The following is a screen shot from the machine, where Control Center has already been installed. You can see that port 8080 is in use (it is in state LISTENING). The process with PID 4 has the port in use.
    You can open a Task Manager to see which application has the process with ID opened.
  4. If you see that the port 8080 is already in use, you will have to choose another port for Control Center, so you do not disrupt the existing application.

Post-installation checklist

For NiceLabel Control Center

Open ports in the firewall

Make sure the following inbound communication is allowed:

  • 80 TCP: Inbound connections to the Control Center. The browsers on the workstations open Control Center page. The service LabelServices from the workstation sends information for printing process/statuses to the Control Center.
  • 8080 TCP: Inbound connection to the Document Storage (WebDAV usage). If you have chosen a different port during the installation, make sure that one is open.
  • 6773 TCP: NiceLabelProxyService2019. Connection for application management streams and licensing.
If you use HTTPS trafic (SSL/TLS), enable it for all sites

To encrypt the traffic between NiceLabel clients and NiceLabel Control Center, make sure to enable HTTPS protocol for both sites, where NiceLabel Control Center runs:

  • Default Web Site: Exposes the connection to the main Control Center UI.
  • EPMWebDav: Enables seamless integration of document storage in NiceLabel clients through WebDAV protocol.

If you enabled HTTPS support, make sure to disable HTTP traffic. The clients cannot use both protocols at the same time. Its either one or the other. In IIS, remove binding to HTTP protocol for both sites.

For NiceLabel clients (Desiger, Automation, Print)

Enable access to authentication servers (if you use Label Cloud products)

The following sites added into the Trusted sites zone (Internet options>Security settings).

If you use Microsoft authentication:

  • https://*

If you use Google authentication:

  • https://*
Enable full access permissions to NiceLabel’s System folder

NiceLabel client requires full access (read, write, delete) to the System folder.

The system folder is at this location:

%PROGRAMDATA%\NiceLabel\NiceLabel 2019\

This is usually not an issue, because folder %PROGRAMDATA% is writable for users by default.

Open ports in the firewall

If you use Windows Firewall and it is running, the exceptions are added to the list of allowed incoming connections. If Windows Firewall is off, the exceptions are not added automatically. If you use another firewall, configure it manually.

  • 56416 TCP: Incoming connection from the Control Center to NiceLabel Automation service that allows remote management of Automation service.
  • 6772 TCP: NiceLabelProxyService2019. Connection for application management streams and licensing.
Support for WebDAV to use files in the Document Storage

Each machine that need to access data inside a Document Storage repository, must have the WebDAV support installed. Windows desktop OS have the WebDAV support already installed, for Windows server OS you have to add the support before you can access the data.

NOTE. The "client" is not only the one of the NiceLabel Designer applications, but any software accessing the Document Storage, including NiceLabel Automation or even Windows Explorer.

If you use proxy server, exclude local traffic from proxy

Bypass proxy server for local addresses, or the client might not get the license from the NiceLabel Control Center, and files in Document Storage will not be available. For more information see Knowledge Base article KB163.

Add Control Center to the Trusted sites

Add NiceLabel Control Center to the list of Trusted Sites in your browser. This will allow Document Storage plugin to run in your browser.

Client prerequisites for running NiceLabel clients as RemoteApp programs

To access RemoteApp programs that are deployed as .RDP files, the client computer must be running Remote Desktop Connection (RDC) 6.0 or RDC 6.1. 

A supported version of the RDC client is included with Windows Server 2008 and Windows Vista and newer.

To access RemoteApp programs on Mac OS or Android OS, make sure to install the Microsoft Remote Desktop client.

Print document   Email document


Did this article help you? *