When your Intella setup involves a standalone license server, there are some important considerations, which also provide benefits.
USB dongle licenses involve plugging a physical USB device into a computer to activate licensed software installed on that machine. The software periodically checks that the attached dongle contains the right license confirmation data. In contrast, a network license hosted on a separate server computer can activate software on multiple machines across an organization. Instead of a physical dongle for every computer, the software contacts the network license server remotely to verify licensed use rights. The license server manages what devices have an available license at any given time from a central dashboard. Therefore, network licensing enables concurrent usage while USB dongles lock licenses to individual computers - making network licensing preferred for large multi-machine deployments.
With Intella products, you can host your licenses separately from the machines running your Intella software. Whether using a network-enabled dongle or a software license, configure your setup in the Sentinel Admin Control Center to achieve this license sharing.
More information on using this setup can be found here: Sentinel Admin Control Center Setup
A fixed IP address is key for this setup to work properly. For example, if the server IP address changes from 192.168.1.1 to 192.168.1.2, access to the license server will be lost, preventing products from functioning.
When your Intella setup uses a standalone license server, there are some considerations, but it also provides benefits.
Benefits of a license server setup
- No need for dongles or software licenses for each individual client. All access is managed in a central location.
- Software license servers allow for seamless testing when using a virtual machine to host your software.
- For license servers using a software license, Intella can run entirely off-premise in a cloud environment.
Static IP setup (fixed IP)
With static IP addresses, the address of a device does not change. For example, if Computer A has the static IP address of 123.456.789, that address will stay the same and not change over time.
This makes it much easier for other computers to connect to Computer A. If Computer B knows that Computer A's IP address is 123.456.789 today, Computer B can rely on that address still working tomorrow, next week, or next month. Even if Computer A gets turned off and back on, its static IP remains the same.
So the IP address acts like a stable "identity" that other devices can always use to see and communicate with Computer A. They know where to find it instead of the address changing constantly. Just like if your friend John always has the same phone number, 555-1234, even if he switches cell phones. You can always call 555-1234 and reach John.
That is why static IPs make it straightforward for devices on a network to keep tracking of each other. The addressing does not change, so machines can dependably see other machines when they need to connect or transmit data back and forth.
Dynamic IP setup
Dynamic IP addresses are addresses that can change. When a device has a dynamic IP address, it means its address today may be different tomorrow.
This causes a problem when other devices try to connect. For example, if Computer A knows Computer B's IP address is 123 today, tomorrow Computer B may have a new IP address of 456. Computer A would still try to connect to 123 but Computer B will not be there anymore.
It is like if your friend John told you his phone number was 555-1234 yesterday. But today he has a new phone and number of 555-5678. If you try to call 555-1234 still, you will not reach John.
So, with dynamic IP addresses that change often, devices have a hard time keeping track of and connecting to each other. They cannot rely on the address staying the same. That is why dynamic IP makes it tricky for machines to always see who else is on the network. The addresses are not dependable over time.
Setting up a static ip-address
Configuring a device to use a static IP address instead of a dynamic address should not be attempted without coordination with your organization's network management personnel. Network managers have oversight on the allocation of IP addresses across the corporate infrastructure. They ensure each device has a unique address that properly integrates with routers, switches, servers, and other networked equipment.
At a high level, setting a static IP involves manually entering a permanent, fixed numerical identifier for a device in its network settings instead of using an automatically-assigned dynamic address. However, there are implications when altering something this fundamental to enterprise connectivity. Potential for IP conflicts, network routing failures, loss of internet access, and more.
Therefore, policies at most companies require submitting a formal request for allocation of any new static IP addresses. This is handled by IT teams who consult IP address management inventories and infrastructure capacity plans. They determine address availability, complete necessary configurations, consider location parameters, test connectivity impact, and implement suitable IP addresses after approval processes.
In summary - non-specialist staff should not directly make changes between static and dynamic IPs. Formal organizational procedures overseen by dedicated network managers must be followed to introduce new static IP devices or convert existing dynamic addresses. Consult your IT department and infrastructure support teams accordingly about deployment needs requiring static addressing.