Server Installation

Overview

This installation method is no longer recommended and may be deprecated in the future.

For the majority of users we recommend the Standard Local Install option where the application is located directly on the client machine. For mass-deployment in enterprise environments we recommend the Silent Install commands or custom packages/scripts used by company software centers. The Server Install (Advanced) option is a legacy setup that was originally created to help reduce the amount of time spent by IT Admins performing updates. For large workgroups in the past it was burdensome to re-run installers on everyone's machine every time there was a maintenance release or patch. Server installations allowed the base application and files to be stored on a network server, while client machines had a shortcut and pointer to the server. The client machines would effectively clone the executable and required files from the server and run it in local memory. This way, every time there was a maintenance release the IT Admin would simply re-run the server installation to update the source files on the server, and the client machines were already set up to point to the source location.

In modern times, the use of company software center packages, silent install commands, and RMM automations have made it easier to disperse the same version of a software package to many users. Therefore, the server install method has become redundant and outdated. The additional complexity and setup of the server is actually more difficult than preparing packages and scripts for software centers.

Full installation setup consists of the following steps:

  1. Ensure the requirements listed below are met

  2. Server Setup

  3. Client Machine Setup

  4. Set Up the Copy Protection

 

Requirements

  • License Number - This is a 9 or 10-digit number provided on the receipt of purchase in the format of XXXXX-XXXXX (the hyphen is part of the license number). Note: The License Numbers are product-specific and version-specific. For example, a Fathom 14 installer will reject a Fathom 13 License Number. Make sure you have the correct License Number from the software purchase receipt that applies to the product and version that is being installed.

  • Registration.txt File - This is a text file containing the required 32-digit eLicense Activation Code, and it is provided with the receipt of purchase.

  • Internet Connection - The PC must have access to https://my.nalpeiron.com (IP address 20.237.110.18, on port 443). Ensure it is not blocked by company firewalls.

  • Administrator Privileges - The application installation will require admin rights on the PC.

 

Server Setup

On the server, follow the standard instructions but with modifications at the following steps:

  1. Customer Information: Put the same company name in both the Name and Company fields. This information will be visible on all client machines in the Help > About menu of the software interface.

  2. Setup Type: Select Server Install (Advanced).

Once the installer finishes, share the C:\Program Files (x86)\Datacor folder from the server with the network of client machines. Client machines need both read and write permissions.

 

Client Machine Setup

On each client machine:

  1. Navigate to the shared server folder: \\server\Program Files (x86)\Datacor\Application\Network Client Setup.

  2. Run the AppClientSetup.exe to set up the proper links and install the necessary files on the client machine.

Note: Trying to launch the application executable on the server will not work unless you also run the client machine setup on the server itself. This is not needed, and we recommend performing testing from the client machines themselves.

 

Set Up the Copy Protection

Set up the appropriate licensing based on which copy protection method you are using below:

  • eLicense: You can proactively place the Registration.txt file on the server (ProgramData\Datacor\Licensing) or let the end-user enter the 32-digit code themselves on the first activation.

  • Legacy USB Key: Drivers need to be installed on the server hosting the USB Key.