Network License Installation Instructions Revised: 04/04/2018

Transcription

1 Network License Installation Instructions Revised: 04/04/2018

2 1 Table of Contents Installation & Activation... 3 Troubleshooting... 5 Nalpeiron Windows Service... 5 Abandoned Client Licenses... 5 LAN Diagnostic Tool... 6 Unable to install Windows Service... 6 No connection to LAN... 7 Licensing service file is missing... 8 Get service update from publisher... 8 You did not enter a LAN license number... 8 Error Reporting / All Other Issues... 8 Checking Out a License... 9 Tracking License Usage... 9 License Tracking Sample Log... 10

3 2 Thank you for purchasing Orca3D! The following is meant to guide you through the process of setting up your Orca3D network server and clients. We have tried to write this in a way to guide you around common pitfalls, but due to the outstanding number of unique network configurations, we are not able to cover every single case in this short installation document. Should you have any questions or issues, please feel free to contact us at support@orca3d.com. Please be sure to include a description of your configuration, including the operating system on the server and workstations. Also include a description of the steps that you ve completed, as well as screen captures of any error messages.

4 3 Installation & Activation *** Please note that as of Orca3D v1.3.8, there is no longer a 32-bit network client installation for Orca3D. We have discontinued 32-bit support for Orca3D meaning that it will not be possible to install Orca3D with Rhino 4. The network license server can still be a 32-bit operating system, but the clients must be 64-bit running Rhino 5 64-bit. *** There are 3 basic steps involved in installing Orca3D with a network floating license. These steps are described below. Note that server activation should be done from the server locally and not through a remote connection. Client installation can be done remotely but the Orca3D network license will only be found when running at the local workstation, not through a remote connection. 1. Install Network Server - Select a machine in your network to act as the Orca3D network license server. Although this can be any machine in the network, it is advisable to choose a machine that is always running so that the Orca3D license is always available. In addition, this machine must meet the following requirements: a. It must be running on a Microsoft Network b. The license server must be at the top level of the network (or above all of the workstations using the protected application). c. The service uses standard Microsoft ports; the licensing setup will have to be configured to allow file sharing between the license server and the workstations (the license server must be visible on each workstation under network neighborhood); Leave ports 136, 137, and 138 open for communication on the intranet. d. NetBIOS must be enabled for communication between the license server and the client. Ensure that name resolution is enabled between the machines. e. Prior to version 1.2 of Orca3D, there was a requirement that the network license server must not be running under VMware or any other hardware virtualization software. As of version 1.2, this requirement has been removed (only from the network-licensed version of Orca3D). Be aware though, that there are potential issues that the IT administrator must be aware of if installing the Orca3D network license on a server with virtualization software. Specifically, changing the virtual server s configuration, say by a backup and restore, can cause the licensing system to think the server s hard drive has changed. This may cause the Orca3D license to stop functioning. Before performing any configuration changes the user should deactivate their network license and then reactivate it after changing the configuration. Run the installation file Orca3DNetworkServerInstallation[version].exe (where [version] is version specific information like version number or date). You must have administrative privileges when installing the network server. *** If your server is running Windows Vista/7/8.1, you will need to right-click the install file and choose Run as Administrator, even if you have administrative privileges. Also note that after installing the Orca3D network server you must reboot the server. ***

5 2. Activate Network License on Network Server You will next need to activate the network license on the network server. You should have been provided with a license code for your network license. From the Windows Start menu choose All Programs/Orca3D Network Server/Orca3D Network License Manager. (If this shortcut does not appear in the Start menu use Windows Explorer to browse to the folder where the Orca3D network server software was installed in step 1. By default this is C:\Program Files\Orca3D Network Server on 32-bit operating systems or C:\Program Files (x86)\orca3d Network Server on 64-bit operating systems. Run the network license manager utility, netnls Manager.exe. ) On the Internet Activate tab, enter the provided license code and click Activate. You should receive notification that the license was successfully activated. Offline License Activation If you are unable to use automatic activation due to network restrictions on the network server, you may use the offline activation option. From the Orca3D Network License Manager, click on the Import Certificate tab. You will need your installation ID from this page as well as your original license code. On a computer with an Internet connection, navigate to: Enter the installation ID and network license code and click Generate Unlock Code/Certificate. Paste the generated code into the Activation Certificate box in the license manager and click Import Certificate. Note: The license can be de-activated using the Export Certificate tab of the license manager to generate an Export Certificate. This code should then be pasted into the following webpage to complete the de-activation process: If for any reason you are unable to activate successfully do not proceed to installing Orca3D on the client workstations. Doing so may result in the product being incorrectly installed and not connecting correctly to the license server. 3. Install Orca3D On Workstations Once the network license server has been installed and the network license has been activated, install Orca3D on each workstation where you want to be able to access Orca3D. (If you already have a version of Orca3D installed on the client workstation, you will need to first uninstall it before installing the network version.) Use Windows Explorer to browse to the client installation folder on the Orca3D network server where the server software was installed. This folder is on the machine nominated in step 1 as the Orca3D network server, and is in the same folder described in step 2 above when you activated the license. You should see a client installation folder for the 64-bit client installs. Make sure you have administrative privileges on the workstation and run the installer Install Product.exe. *** If your workstation is running Windows Vista/7/8.1, you will need to right-click the install file and choose Run as Administrator. After installing the Orca3D client you must reboot the client. Perform this step on each workstation where Orca3D is to be installed. *** Your network installation should now be complete. You should be able to run Orca3D on each client workstation as long as you do not exceed the number of concurrent licenses that you have purchased. 4

6 5 Troubleshooting Nalpeiron Windows Service Orca3D uses the Nalpeiron licensing service for both standalone and network licenses. Provided that Orca3D has been properly installed and activated following the steps in the installation section of this guide, the network version of this service should be running on both the server and client computers. In some rare cases, computer/network security settings may have prevented the Nalpeiron service from starting during the Windows boot process. To check this, open the Windows Services dialog: Windows XP: Open the Control Panel, and double-click on Services. Windows Vista/7: Click Start, then in the Search box type Services. Click on "Services" in the search results. Windows 8.1/10: Using the Search charm, type Services. Click on "View Local Services" in the search results. For network licenses, you should see "Nalpeiron Control Service" in the list, and its status should be "Running." If not, right click on it and select Start. Abandoned Client Licenses If Rhino crashes or otherwise closes improperly, the Orca3D client license may not be properly returned to the server. The network licensing system is designed so that the next time that Rhino is started on that same client computer; the same Orca3D network client license will be used in order to avoid losing the use of a client license. If you do seem to lose the use of an Orca3D client license, for example a client license was not properly returned from a computer and the computer is no longer available, you should reset the network license service. To do this, you will need to follow these steps on the computer that is acting as the network license server: 1. Follow the steps in the section Nalpeiron Windows Service to open the Windows Services dialog. 2. Locate the Nalpeiron Control Service in the list, right-click on it, and select Restart. 3. Wait for Windows to restart the service, then verify that its current status is Running. 4. On the Orca3D network license server, launch the network license manager (netnls Manager.exe) from the Orca3D installation directory. (The default location is: "C:\Program Files\Orca3D Network Server) 5. On the Authorize Transfer page of the network license manager, verify that the number of Seats in Use is correct.

7 6 LAN Diagnostic Tool For any issue that cannot be self-diagnosed and rectified, we have included a Nalpeiron diagnostics tool in the Orca3D network client and server installations that will analyze computers and networks for known communication issues. Please follow the following steps to run the diagnostic tool on both the server and client: 1. Locate the Nalpeiron tool ( LAN Computer Performance Diagnostic.exe ) in your Orca3D or Orca3D Network Server installation folder. If you do not have this file, you may download it from the Orca3D website at You must unzip the files into your Orca3D Network Client and/or Server installation folder, where filechck.dll is located. 2. Run the utility by right-clicking on the file and selecting "Run as Administrator." When the utility starts, click the "Check Computer Functionality" button. The diagnostic may take up to 15 minutes to run depending on your system configuration. 3. When the diagnostic has completed and opens a Results window to show a diagnostic report, you can click the Exit button. Next, the diagnostic utility will ask you if you want to save the results. You should say "Yes" (noting the file name and location reported in the next pop-up window). 4. The report file is typically named LANComputerReport.txt and is located in the root directory (e.g. C:\). Please send both the client and server reports to support@orca3d.com for troubleshooting. Unable to install Windows Service In some cases, this error may occur on an Orca3D Network Client computer which previously had the Orca3D Network Server installed. If this is not the case, please disregard the following and contact Orca3D support at support@orca3d.com. Although the Network Server has been uninstalled, a registry entry may have persisted from the network installation that is causing a service runtime error. Please make the following change: 1. Start the registry editor ( regedit.exe ) and navigate to the registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NalServ\Parameters 2. Delete the registry entry Networked, if it exists.

8 7 No connection to LAN If you are getting this error, please first verify that all of the conditions of Step 1 of the installation instructions are satisfied and make sure that the server and client computers can see each other on the network. To test this, make sure that bidirectional pinging is successful between the network server and the client using computer name (not IP address) resolution. As of June 2016, Microsoft has released a Windows security update (KB ) which restricts NetBIOS communication between subnets. If you are utilizing Orca3D network licensing across multiple subnets, please create the following registry entry to reverse the NetBIOS hardening (requires restart): SUBKEY: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters Value Name: AllowNBToInternet Type: DWORD Value: 1 If you are still getting the error, this typically correlates to a network timeout issue. The default network timeout period is 4 seconds, which has been satisfactory in most of the network installations to date, but for some networks this is not sufficient for license server communication. It is possible, however, to modify this setting through a registry modification (on both the server and client machines) to give the machines more time to communicate. Please make the following change on both the server and client: 1. To change the timeout period, start the registry editor ( regedit.exe ) and navigate to the registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NalServ\Parameters 2. Add a REG_DWORD value named Timeout to the Parameters key and set it to The timeout values are in milliseconds, so setting the value to will give a timeout of 10 seconds while Rhino loads and Orca3D connects to the license server. You must restart the Nalpeiron Control Service after making the registry change on both machines so that the change takes effect (either through Services or by restarting the machine).

9 8 Licensing service file is missing If you see this error on the Orca3D Network client computer, this means that the appropriate registry entries of network licensing do not exists and the active licensing service does not know to look for a license server. This is commonly due to the client not being installed using Install Product.exe, which sets up the registry entries necessary for Orca3D Network licensing. Please uninstall the Orca3D client and re-install it using Install Product.exe. Get service update from publisher Your computer is running an outdated version of the network licensing service. Please contact Orca3D support at support@orca3d.com for updated service files. You did not enter a LAN license number When activating your Orca3D Network license on the Orca3D Server, please double-check that your license code is accurate and is formatted as such: N389xxxxxxxxxxxxxxx. Error Reporting / All Other Issues For all licensing issues, the first thing to do is to make sure that the Nalpeiron service is running on both the Orca3D network server and client (detailed above in Nalpeiron Windows Service ). Create and send the LAN diagnostic report files (detailed above in LAN Diagnostic Tool ) from both your license server and client computer, along with a description of the problem that you are having, in your support request to support@orca3d.com. While not as important, it is also helpful for us to know some of the details of your computer and operating system. You can run the Belarc Advisor PC Audit Utility found here: This utility will create a pdf file that should be sent to us.

10 9 Checking Out a License Please see the Orca3D Help File for details on this function. [Orca3D Help] -> Licensing -> Network Licensing -> Checking out a license Tracking License Usage The netnls Service v7.2+ supports user logging. 1. The logging function is turned on and off by a Windows Registry setting. Using regedit or another registry editor, locate the key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\NalServ\Parameters. To turn on the logging function, create a new string valued named LoggingPath and store in it the path including the first part of the log file name. (e.g. C:\Orca_ ). The actual name of the log file will be: <user defined start of name>lan_usage_log_<date as MM-DD-YYYY>_ <time as HH-MM-SS>.txt So for example in this case the attached log's real name might be: Orca_LAN_Usage_Log_ _ txt. Each time the Nalpeiron Control Service is stopped and started a new log file is created. This is so if a license server is turned off, on, restarted, or the service restarted, all of the usage logs will be stored and nothing overwritten. 2. Restart the Nalpeiron Control Service to start the logging process. 3. Since we do not add the app name to the service, individual apps are numbered. If five LAN protected products are run on a particular license server, each product would get an App # 1,2,3,4, or 5 that is shown in the usage log. 4. The computer name in the usage log is the client computer's Microsoft name. If a product is run from the server directly or under Citrix, the name stored will be the name of the server. 5. Action in the usage log will be START or STOP. a. START corresponds to LoggedOn b. Date in the usage log is the logged on or off date. c. Time in the usage log is the logged on or off time. d. Users in the usage log are the total number of concurrent users for that product. Keep in mind, that if you just shut down a Terminal Services or other remote connection without closing the app, that user was never logged off.

11 10 License Tracking Sample Log The following is an example of a netnls license tracking log: Usage Logging on start date: Time: 12:30:08 App #: Computer Name: Action: Date: Time: Users: 1 LAB1 START :37: LAB1 STOP :42: LAB1 START :11: LAB5 START :15: LAB1 STOP :43: LAB3 START :47: LAB3 STOP :47: LAB5 STOP :53: LAB2 START :58: LAB2 STOP :59: LAB-SERVER START :17: LAB2 START :18: