Network License

From SysCAD Documentation
Jump to navigation Jump to search

Navigation: User Guide ➔ Licensing ➔ Network License

Licensing USB License Software License
Licensing Summary License Options CrypKey Licensing Software Permanent Standalone License Temporary Standalone License Setting up Network License Issuing Network License Licensing Utility Licensing Transfer

Latest SysCAD Version: 21 September 2021 - SysCAD 9.3 Build 139.29552


Network Licensing Options

There are two types of Network licenses that can be used:

  1. Enterprise License Manager (ELM) - recommended
  2. Drive Share

Using Crypkey True Enterprise License Manager (ELM) is recommended over Drive Share method and has a number of advantages:

  • Do not need to create a drive share folder with full permissions for all SysCAD users.
  • More robust and responsive on a variety of LAN and WAN configurations. Faster network license checking.
  • Easier for IT for SysCAD license management and troubleshooting.

General Notes on Network Licenses:

  1. The USB License Key is not used for Network Licenses.
  2. Network licenses are issued for no longer than 12 months duration (usually to next 10 October).
  3. Network licenses cannot be used for old expired versions of SysCAD (SysCAD version must be updated regularly). Refer to Software Licenses Expiry Dates for expiry dates for specific versions of SysCAD.
  4. Network licenses are issued on a first come first served basis.
  5. Licenses are released to the system when a user exits SysCAD.
  6. If you open the SysCAD License Utility located in the license folder, this counts as one of the network user licenses.
  7. If a network connection is lost, or there is an abnormal SysCAD exit then the license is released to the network after a timeout period (a maximum of approximately 10 minutes).
  8. When you try start SysCAD and no network licenses are available, the SysCAD message window displays the computer and user names of the license users. The menu option "Network Users..." also gives a list of current license users. If you believe a license has become available, exit SysCAD and restart to try again.
  9. If multiple copies of SysCAD are started on the same PC, each will use one of the available network user licenses. This does mean that users may only open as many instances of SysCAD as they have licenses. (With a Stand-alone license, there is no restriction to the number of instances of SysCAD that a user may open).

Using Enterprise License Manager (ELM) for Network Licensing

ELM requirements:

  • This requires some configuration on client and server sides.
  • Only one network license type (set of options) can be used per server. So if you have two different network licenses (for example separate ProBal and Dynamic network licenses), then two separate license servers need to be configured.
  • New to SysCAD 9.3 with Crypkey 8 you can now select to use NetBios or TCPIP methods for ELM. TCPIP method is recomended.
  • TCPIP method has some advantages over NetBios method, especially in larger networks with multiple Domains and/or subnets. The method is generally more robust and faster.
  • IMPORTANT: Must not block communications with a client Firewall. Communications are sent via Ports UDP 137 and 138. If Windows Firewall is running, the File and Print Sharing exception must be checked (ie "File and Printer Sharing" MUST be enabled under windows firewall on the client and the server).

Once the Server is configured, no further changes are required for new clients, and when new clients are installing and configuring SysCAD everything is done on the client PC.

For a detailed guide to setting up ELM, please refer to the following guide: DC012 SysCAD Network ELM License Quick Start Guide Rev 1.0

Server side Instructions

On the Server, as administrator:

  1. Create a folder for the SysCAD Licensing, for example "SysCADLicenseServer". This folder must NOT be under Program Files. This folder does not need to be in a share or have any specific user permissions, etc. This folder should be on a drive on the server.
  2. Obtain a fresh copy of the server files. These can be obtained from two alternate locations:
    • from the SysCAD downloads page (https://www.syscad.net/login/). Under the Utilities section download the LicenseManagementFiles zip file. The NetworkLicense_Server folder is contained in this zip file.
    • from the SysCAD installation folder "\SysCADXXX\Setup\NetworkLicense_Server"
  3. Copy the server files (in the NetworkLicense_Server folder) to the new folder created in step 1. Do NOT copy all the files from a previously used ELM network license folder, as copying some of the created files (eg syscad.cihs) can cause error messages when trying to use the licensing software.
  4. If the Crypkey Service is not already installed on server, install this from the server by running setupex.exe.
  5. The configuration file syscad.ces.ini is pre-configured to use NETBIOS, but can be used for further configuration.
  6. Run Enterprise License Manager (Enterprise License Manager.exe). It should be run locally from on the server. It will show NETBIOS or TCPIP at bottom RHS of window.
  7. To use TCPIP method, select the menu option Edit | Edit Configuration. Then on the "Status" tab change the TCPIP setting to "Enabled". This is the equivalent of setting entry "TCPIP=Enabled" under [GENERAL] in syscad.ces.ini. Optionally change the default IP Address and/or TCPIP Port. Push OK button.
  8. Select the menu option Actions | Start Server. In a minute it should return a dialog indicating it's running.
  9. Then in ELM, select menu option Actions | Manage Server licenses, the Server Machine name (or IP Address if using TCPIP method) should appear on the left hand column. Click the Machine Name. Make a note of the Server Machine Name or IP Address as this name is required when configuring the Client.
  10. ELM will then check for a SysCAD License, it would normally be unlicensed (unless a network license had already been issued for this folder). The license status is given and a site code for issuing licenses.
    ELM Site Code.png
  11. Generally, the next step is to issue the network license for this server folder. The site code should be copied and pasted into the text of an email and sent to license@syscad.net. The site code can be obtained in two ways:
  12. Kenwalt will send back a corresponding site key to authorise the license. The license can be activated by pasting the site key into the site key dialog box.
    • If the site key is entered in ELM, press the 'Validate' button after the site key has been entered.
    • If the site key is entered in the License Utility, press the 'Update' button after the site key has been entered.
  13. The ELM License Server may not be restarted automatically with machine restarts. It is recommended that a call to "StartServer.exe" is included in machine startup script.

Client Side Instructions

  1. On each of the Client PCs create a folder for the client side license management, for example "SysCADNetworkLicense". This folder must NOT be under Program Files.
  2. Obtain a fresh copy of the client files. These can be obtained from two alternate locations:
    • from the SysCAD downloads page (https://www.syscad.net/login/). Under the Utilities section download the LicenseManagementFiles zip file. The NetworkLicense_Client folder is contained in this zip file.
    • from the SysCAD installation folder "\SysCADXXX\Setup\NetworkLicense_Client"
  3. Copy the client files (in the NetworkLicense_Client folder) to the new folder created in step 1.
  4. With a text editor (eg notepad) open the SYSCAD.CEC.ini file. (Note that these steps can also be performed using program ClientLicenseConfig.exe)
    • If using NETBIOS, where it has the server machine name (example SYSCAD-PC) change this to the server name noted when setting up the Server side. Save and exit.
    • If using TCPIP, where it has the server machine name (example SYSCAD-PC) change this to the server name noted when setting up the Server side. Alternatively the server IP address can be used (eg 192.168.1.19) this is useful where in some larger multidomain networks where the server name is not working. Under [GENERAL] ensure there is an entry 'TCPIP=Enabled'. Save and exit.
    • If using TCPIP and not using the default Port 4758 the port number must follow the server name or IP address separated with a ':'. (example SYSCAD-PC:4200 or 192.168.1.19:4200).
  5. To test if it is working correctly, run SysCAD License Utility (syscad.exe) located in this folder. It should start and retrieve a license from the server. Close the SysCAD license utility to release the license.
  6. The correctly configured SYSCAD.CEC.ini can now be copied or rolled out for all client PCs for all users.
  7. Still on the client PC, for the main SysCAD Application, run this. Then select the license location menu command. Now Browse for the client folder created and tested above. NOTE - you are no longer browsing across the LAN/WAN for a shared folder! Exit and restart SysCAD. If all is still well, then the SysCAD application should retrieve the license from the server.

Trouble Shooting ELM Network License Problems

For Server and Client when using NETBIOS:

  1. Is Crypkey Service installed and running correctly?
  2. All systems must belong to the same Windows Domain or Workgroup.
  3. Are File and Printer sharing enabled under windows firewall? If you are using the built-in Windows Firewall, you will want to enable File and Printer Sharing as an allowed exception.
  4. Are UDP 137 and 138 ports open? Note, these are ports that Windows uses for NetBIOS communications.
  5. Make sure the network connection that you are using has the Client for Microsoft Networks installed and enabled.
  6. Client and Server must be installed on the same network subnet. This is because both Client and Server will broadcast messages.
  7. Ensure Name Resolution works between License Server and Client.

For Server and Client when using TCPIP:

  1. Is Crypkey Service installed and running correctly?

Server Side:

  1. Test that ELM runs and that Start Server works. Try Stop and Start the server. ELM is intended to be run locally from the folder that contains the license. If you try to run the ELM from a different context, then certain menu options will become disabled - the bottom right of status bar will show "REM". When run locally on the server the bottom right of status bar will show "LOC".
  2. The ELM License Server may not be restarted automatically with machine restarts. For example, this can occur with server updates and maintenance. Suggested solution: Include a call to "StartServer.exe" in machine startup script.
  3. In ELM select Manage License Servers and select the machine name. It should display a status including a valid license.
  4. In the ELM folder run syscad.exe. It should also be error free and show a valid license.

Client Side:

  1. If using NETBIOS:
    • Is the server name entered correctly in syscad.cec.ini?
  2. If using TCPIP:
    • Is the server name or server IP address entered correctly in syscad.cec.ini?
    • Is the entry under [INCLUDED_DOMAINS] E1=NOT_APPLICABLE in syscad.cec.ini?
    • Is the entry under [GENERAL] TCPIP=Enabled in syscad.cec.ini?
  3. Run syscad.exe in the client side license folder. Does it find the network license?
  4. In SysCAD application, set license location to the client side license folder on the PC.

Error "Initialisation Failure -27":
On the client when SysCAD is initialising the Crypkey software and you receive the -27 error "The requested License Server was not found for xxxx\syscad.exe" then check:

  1. A server is running, with a valid network license and configuration
  2. There is network communication between the machines
  3. The client is configured correctly to look for the server
  4. Windows firewall or another firewall is not running on the client blocking communication
  5. If using NETBIOS and the server is not in the same domain as the client, the clients syscad.cec.ini must have E1=NOT_APPLICABLE under [INCLUDED_DOMAINS] and E1=<the server machine name> under [INCLUDED_MACHINES]

If none of the above resolves the issue, please send an email to license@syscad.net with the following details:

  1. Describe the problems you are experiencing and steps you have tried to resolve them.
  2. If possible, screenshots of the error messages would be helpful.

The SysCAD team will be in contact with you soon to resolve the issue.

Using Drive Share Network License

If a SysCAD network license using DriveShare is going to be used, there needs to be a nominated PC for use as the SysCAD License Server. This can be any PC on the network and does not need to be a Server.

Note that the DriveShare method is only for LAN use where users are directly connected on the network (ie not intended for WAN, VPN, remote access, etc).

Issue a Network License

There are two options for setting up licensing on the selected SysCAD license server:

  1. Install the Crypkey Service and use the SysCAD Licensing Utility for license management. This is the recommended option.
  2. Install the full SysCAD software as described for a normal Stand-Alone PC.

Setting up the network license folder:

The Drive Share network license can be located on any folder on the license server. This folder needs to be shared on the network and FULL access rights need to be granted to all SysCAD users for your site. Typical steps for setting this up are:

  1. Create a folder (eg "..\SysCADLicense") for the shared network license. This folder must NOT be under Program Files.
  2. For this new folder, assign Full permissions for all SysCAD users or groups. Important: Full permissions (read/write/modify/create/etc) for all SysCAD users who need access to this shared folder is required. When adding new users, they need these access permissions to all the existing files in the license folder, especially the .ngn file and all the syscad.* files including the system hidden syscad.* files.
  3. For this new folder, copy the licensing utility files to this folder. Copy the contents of the licensing utility folder (\SysCAD93\Setup\LicensingUtility) to the folder that has been created. The important files are syscad.exe, crp32002.ngn, setupex.exe and cks.exe.
  4. If Crypkey Service is not installed or is old, then on the server install it by running setupex.exe (may require IT to perform this step). The Crypkey service is installed by running the "setupex.exe" program supplied. This requires administrator privileges to install correctly and must be installed from the server PC. Note that this is a silent install so there are no notification messages during or after the installation.
  5. This license folder MUST be shared to allow remote network access by other users. If desired, a meaningful share name may be created so that users can locate this shared folder easily.
  6. Run syscad.exe. This will start the licensing utility. As this file syscad.exe is in the folder for the intended license, the license location is the current folder. Select the license authorisation button to obtain a site code.
  7. Contact Kenwalt and provide the site code so that the network license may be issued. Once the authorisation site key has been provided by Kenwalt, this needs to be entered and the network license is now ready for use.
  8. Select license information to confirm license has been issued and view details of the license options granted.
  9. Once a license is issued the folder (or contents) must not be deleted, renamed or moved, as this will cause the license to be “lost”.
  10. Client users can now run SysCAD and “point” (using the license location option) at the shared network license folder to access the multiuser network licenses as described below in "Using SysCAD on network workstations".

Using SysCAD on network workstations:

  1. On each local PC (or laptop) that may use SysCAD, install a copy of SysCAD.
  2. The first time you start SysCAD it will operate in demonstration mode. Before trying to load any projects, select the license location menu option and use browse to “point” at the network location or share where the SysCAD network license is located. You will need to ensure that IT have given you full access to this shared network location.
  3. Once you have changed and accepted the new network license location, you will have access to one of the shared network licenses.
  4. If at the time you start SysCAD all the network licenses are held by other users, you will receive a message denying access to a license and a list of users currently using SysCAD licenses. Your copy will then revert to demonstration mode.

Trouble shooting Drive Share Network License Problems

Having Problems accessing Network Licenses:

  1. Check that licensing software (crypkey) is working correctly on the license server PC. Test this on the server by running the License Utility syscad.exe and checking the messages and license. Note you must test this ON the server (not by running syscad.exe license utility from a network folder while you are on a client PC). Any crypkey licensing errors on the server need to be resolved before trying to use the network license. See Troubleshooting Crypkey for further information on checking Crypkey version or resolving Crypkey issues.
  2. Check that the user has full permissions (read/write/modify/create/etc) to the license folder AND the existing files in this folder.
  3. If lots of files with extension .an are being created and not removed in the network license folder then it is likely that one (or more) users do not have correct permissions to the license folder and/or existing files.
  4. Check that licensing software (crypkey) is working correctly on the client PC. Test this by changing the license location to a local drive and checking the message window for licensing errors. Any crypkey licensing errors need to be resolved before trying to use the network license.

If none of the above resolves the issue, please send an email to license@syscad.net with the following details:

  1. Describe the problems you are experiencing and steps you have tried to resolve them.
  2. If possible, screenshots of the error messages would be helpful.

The SysCAD team will be in contact with you soon to resolve the issue.