Table of Contents
- Overview
- Do I need a server computer for the license server?
- How many licenses can be installed per machine or host?
- What if there are two licenses for a University—one for research and one for education?
- What are concurrencies (seats) and how are they used?
- Can I install the Server and OLI Software on the same machine?
- I have two different license servers with different serial numbers. Do I use one client serial number for both?
- What is the OLI Network License Manager/provider?
- What is the difference between the OLI Network License Admin Program and the OLI Network License Admin Tool?
- Why do you have to update the client serial number?
- If you are upgrading the software, do you need to upgrade the license file or server components?
- Conclusion
Overview
This FAQ explains how OLI’s network licensing works in simple terms. It covers what kind of computer is needed to host the license, how many users can access the software at the same time, and how different types of licenses (like those used for research vs. education) can be managed. It also clears up common questions about the license files, serial numbers, and software updates. If your team uses OLI software across several machines or departments, this guide will help you understand what’s needed to get everyone up and running smoothly.
Do I need a server computer for the license server?
Yes. A physical or virtual machine is required to host the license server, where the license manager software runs. This server must be online and running 24/7.
How many licenses can be installed per machine or host?
A server can host only one network license. In other words, one machine may have only one network license installed.
What if there are two licenses for a University—one for research and one for education?
Each license must be hosted on a separate server. OLI can provide two separate licenses (one for research and one for education). Alternatively, the two licenses can be combined into one file by summing the concurrencies, though this may lead to resource contention.
What are concurrencies (seats) and how are they used?
Concurrencies represent the number of users who can access the software simultaneously via the license server. There is no limit on the number of installations, only on the number of concurrent users.
Can I install the Server and OLI Software on the same machine?
Yes, although it is not recommended. If installed on the same machine, the server must remain on and connected to the network so that other users can access the software.
I have two different license servers with different serial numbers. Do I use one client serial number for both?
No, the client serial number must be paired with each server individually. They are not interchangeable.
What is the OLI Network License Manager/provider?
The terms OLI Network License Manager and OLI Network Security Provider are used interchangeably.
What is the difference between the OLI Network License Admin Program and the OLI Network License Admin Tool?
They refer to the same program.
Why do you have to update the client serial number?
Typically, the client serial number does not require updating when the server license expires (usually on a yearly basis). It is updated only if there is a change in the product configuration—such as the addition or removal of a product.
If you are upgrading the software, do you need to upgrade the license file or server components?
No, the software version is independent of the license file and server components; no upgrade is necessary.
Conclusion
Setting up and managing OLI’s network licenses doesn't have to be complicated. With just a few key requirements, like having a dedicated computer to manage the license and knowing how many people need access at once, your organization can ensure that the software is always available when needed. If your needs change or you're unsure how to proceed, OLI’s support team is here to help with clear, straightforward guidance. This FAQ is a great starting point to make sure your software setup works for everyone.