Basics

Terminology

• Workstation: a computer on which a software is used (but on which it is not necessarily installed).
• Application server: the computer on which the software is installed in order to be used on other workstations.
• Client: a workstation on which a software, that is installed on another computer, i.e. the application server, is used.
• Stand-alone installation: the software is installed on the workstation on which it is used.
• Application server installation: the software is installed on a file server, in a network shared folder, to be used on other workstations.
• Main Cubus folder: the top folder of a Cubus installation.
• UpdateHost: the workstation from which the software is updated; for a stand-alone installation, UpdateHost and workstation are identical; for an application server installation, it is by default the server, but it can be set to any client in the network.
• Hardlock: electronic key (e.g. USB key) required to be plugged in when a Cubus application is running.
• License server: the computer on which the license management utility is running and to which the electronic key is attached, allowing remote license access from other workstations.
• Hardlock keys server: the license server with an attached Hardlock key, running the “HL-Server” management utility.
• Hardlock keys client: a workstation with remote access to a Hardlock key.
• Driver: (also device driver or software driver) a low-level computer program running in the background with direct access to a specific hardware, allowing applications to interact with the hardware.

Requirements

Please check the following requirements before proceeding with installation or update:

Elevated Priviledges

• The Setup utility requires elevated priviledges.
• The CubusNetworkManager utility requires elevated priviledges.
• The installation of drivers and services requires elevated priviledges.

Be sure you have the right to access to the administrator level.

Application Server

• On the application server, network sharing of the main Cubus folder has to be configured with read access permission for all users on the clients.
• The specified path of the main Cubus folder seen from the clients can either be a connected drive (e.g. P:\PROGRAMS\CUBUS\) or an UNC path (e.g. \\SERVER\PROGRAMS\CUBUS\), but it has to be the same for all users.
• For the first installation, full write permission has to be granted recursively onto this main Cubus folder for the user executing the Setup utility.
• For updates, full write permission has to be granted recursively onto this main Cubus folder (located on the application server) for the user executing the CubusManager or Setup utility on the UpdateHost.

Hardlock Keys Server & Hardlock Keys Clients

• Remote access to the Hardlock keys server requires an Ethernet network configured with the TCP/IP protocol.
• The Hardlock keys server should have a fix IP address.
• Each Hardlock keys client may have its own fix IP address or request for a dynamic IP address (DHCP), as long as all Hardlock keys clients are in the same subnet (segment) as the Hardlock keys server. Indeed, by default, the information requested by the key don't pass through the gateways, routers, bridges and others repeaters.
• The UDP port 3047 should be opened on the Hardlock keys server as well as on each Hardlock keys client.
• We expressly recommend to work with only one protocol: TCP/IP. Each computer on the network should have only one Ethernet card. Any other configuration exponentially increases the number of difficulties one may have to solve in order to master license sharing in the network.

Launching a Cubus Application

Cubus applications are launched from the CubusExplorer. To start the CubusExplorer, press the ‹Windows logo› key and type “CubusExplorer”.