Licensing clarification

[Mike Ficher]

Hi,

I’m trying to better understand the NoMachine Network licensing model, and I want to check if my understanding is correct.

This is how I currently see it:

– Personal – for personal use
– Business – for business usage
Based on what I understand, would I need to use business license, as this will be used to support my business process.

However, I’m not fully sure if my interpretation is accurate.

My actual use case is the following:
I would like two of my technicians to connect to our csutomers’ hosts for remote debugging and application support.

Based on that, I’m trying to understand:

– Which license type is the right one for this scenario?
– Do I need multiple licenses for concurrent connections?
– What would be the correct setup for two technicians connecting at the same time?
– Can my customers install free version or they need to install Enterprise Desktop in order that I can offer them support via NoMachine?

For reference, I was looking at: https://store.nomachine.com/network/

Thanks in advance for any clarification.

[Britgirl]

Hi Mike, thanks for reaching out. There is a detailed article in our knowledge base which outlines what software and subscription(s) are appropriate if you are in a remote support/technician scenario. Please read that and let us know if something is still not clear.

https://kb.nomachine.com/AR04X01355

I will sum up what you need here in any case 🙂

1) Your customers can install the free edition or one of the Enterprise products if they are using it in a commercial setting.

2) To connect to your customers’ machines, the software you require is either the Enterprise Client package which does not contain the server component and is completely free, or you can use Enterprise Desktop which will require an Enterprise Desktop Subscription. Which one you choose depends on whether you need to access your own computer(s) remotely as well. You have two ways to connect: “over IP” if on LAN/VPN environments and preconfigured corporate networks, or, if connecting over the Internet, “over Machine Id”.

3) To connect over Machine Id, the target computer must be added to NoMachine Network and your technicians will each require their own NoMachine Network subscription to connect. The Network subscription is required by the user who initiates a Machine Id connection, it is not tied to the software package you install, and it is activated only when the user logs in to NoMachine Network and starts a connection with the Machine Id.

4) Two technicians means each person has their own User Id (NoMachine account). Each User Id is assigned their own Network subscription. The number of supported connections per Network subscription depends on how many concurrent Network connections they need to start. Choose from 1, 4, 8 and more concurrent connections. Network connections are counted from the same device. We don’t ask you to declare which devices you want to connect from. What you cannot do is connect simultaneously from multiple devices over Machine Id using the same User Id.

5) To make management of Network subscription assignment hassle-free, you can use one User Id account (“the owner”) for purchasing all the subscriptions you need, and assign the Network subscriptions to other User Ids. You can assign and unassign as you need. Enterprise Subscriptions cannot be reassigned, they belong to the owner.

[Mike Ficher]

I just have one question regarding point #4. You mentioned choosing between options like 1, 4, etc., but I noticed that option 1 is labeled for personal use. Does your answer means that it can be used in a business context, similar to how I currently use [removed]?

Also, I’d like to highlight that I was really impressed with the performance of your solution, the connection quality and responsiveness felt noticeably better, even when using the easy access setup with machine id.

[Britgirl]

When you say option 1, do you mean my option 1 above? I’ve edited it to make it clearer about the commercial setting.

In a commercial setting, if your assisted end users are employees of your same legal entity, their NoMachine installations require an Enterprise server product and an Enterprise Subscription (so let’s choose Enterprise Desktop for the sake of the example) because it’s considered use of NoMachine in a commercial setting.

A slightly different scenario but perhaps closer to what you do: let’s say you are a company offering remote assistance services to customers who buy computer/tech products from your shop. There are two different entities here: your company and your customer, Joe from the other side of the town or country. Joe is ultimately responsible for his own computer, and all he wants is some help to get his drive working or to fix his Windows machine, so he can install the free edition of NoMachine.

To connect to machines over the Internet (for both scenarios I described above) using the Network service (over Machine Id), your two tech people, user1@yourcompany.com and user2@yourcompany.com, will each require a Network subscription. Choose the Network subscription which has the appropriate number of Network connections for their needs. Sharing a User Id is technically possible (like with the other product you mentioned) but it would be problematic if both wanted to connect using the Network service at the same time since multiple Network connections at the same time from multiple devices using the same User Id is not possible.

I’d like to highlight that I was really impressed with the performance of your solution, the connection quality and responsiveness felt noticeably better, even when using the easy access setup with machine id.

🙂 That’s good to know. If you contact us through the form (Contact Us), our sales team will be happy to provide a quote, also in comparison to the product you are currently using.

[Britgirl]

Also check out:

https://kb.nomachine.com/AR09V01249
https://kb.nomachine.com/AR06V01236
https://kb.nomachine.com/AR06V01237

https://www.nomachine.com/network/what-network-subscription

[Author]

Posts