This guide will explain how to install an nShift On-premises server. Everything in nShift On-premises is controlled from one server that clients connect to and communicate with. If the server is down or turned off, the clients will not run.
The first step is to install Microsoft SQL Server. If you choose to use your own SQL Server, you can skip this step. You can download an installation package from Microsoft here. The express version can be downloaded for free.
You may also download Microsoft SQL Server Express 2019 from nShift here. Note that this version is prepared for nShift On-premises and assumes that you install a database named nShift and have the SQL database and nShift On-premises on the same machine.
We recommend using Microsoft SQL Server 2019 or newer. Please note that .NET Framework version 4 or newer is required to benefit from all features in nShift On-premises.
Download and install nShift On-premises on the server: SetupSRVC.exe. It is not necessary to do any changes during the installation unless you skipped Step 1. In this case you must change the SQL Server information to your own server when GenerateDB.exe starts up.
When you launch nShift On-premises for the first time, it will ask for a Product key. This is the installation code that you received from nShift. Enter it and click OK.
- nShift On-premises is now installed but should be updated before use. (See the article Update nShift On-premises server)
Install your printer. The first time you make a shipment you will be asked to add a printer. (See articles: Installing a Zebra printer and drivers and Printer setup in nShift On-premises).
Download and install nShift On-premises on client machines: SetupCLIC.exe. During the installation of this file, you have to type in the server name. The name can be found by opening On-premises on the server and choosing Edit > Server Connection in the top menu.
The TCP/IP protocol must be enabled in the TCP/IP in SQL Server Configuration Manager for a remote nShift On-premises Client to be able to connect to the SQL server. If you are running Windows firewall on the server, be sure that port 52346 and 52345 are open. Read more in this article: Opening Windows Firewall for client connections to server.
Note: .NET framework is not turned on in Windows by default. Go to Control Panel >All Control Panel Items > Programs and features > Turn Windows features on or off and turn on '.NET framework'.