Hosted multi-client Wapt server

[Tranbert]

Hello,

I'm currently exploring Wapt. I've already installed it locally on a Debian VM. It's really very interesting.

For my small maintenance business, I'm trying to use tools that I have as much control over as possible, but that aren't hosted on my workstation. I use Dolibarr for accounting and invoicing, GLPI for asset tracking, and MeshCentral for remote control of client PCs. Each solution is on its own hosted server (OVH).

In this context, Wapt is exactly the missing link for a true automation solution for software maintenance and workstation updates.

I have a question about the overall architecture: given that my client base includes "entities" of 30-40 workstations, but also small companies with 3-4 laptops and no local servers, what would be the best way to have a single point of management and be able to use all of Wapt's features?

- A "master" WAPT server hosted like my other solutions and accessible via wapt.mydomain.com
- A local mirror in each larger company for packages/updates.
- But the question arises regarding isolated clients...

And more importantly, is WAPT designed to be exposed on an external server or should it be kept in a purely LAN environment? And in the latter case, how do you manage multi-site licenses in the Enterprise version?

I haven't really found a direct answer to these questions, so I'm posting them here. Thank you for your insights and congratulations again on the work!

[vcardon]

- A "master" Wapt server hosted like my other solutions and accessible via wapt.mydomain.com
- A local mirror in each somewhat large company for packages/updates.
- But the question arises of isolated clients...

And more importantly, is Wapt designed to be exposed on an external server or should it be kept in a purely LAN environment? And in that case, in the Enterprise version, how do you manage multi-site licenses?

Since the WAPT server is not a sensitive asset, you can host it in a data center or on your DMZ. Server confidentiality and authenticity will be ensured by deploying a client certificate on your managed workstations. This is the simplest approach and will handle isolated clients.

A mirror is only useful for large sites that don't have huge bandwidth. In the Enterprise version, mirrors are very easy to manage since version 1.8.

Multi-site licenses will be managed like a normal license shared between several end customers if you are an IT manager using WAPT to provide better service to a group of end customers, you will just have to not give access to the full console to your customers because they will see the machines of your other customers (this is being resolved).

Vincent

[Tranbert]

Thanks for the reply, I hadn't seen it...

Well, since then I've been able to do a test installation on an OVH VPS and the 25 machines from my trial pro license are working fine. I'm having an issue with the mirrors, but it's not critical; we have plenty of other problems going on right now.

However, the licensing model seems a bit complicated for my intended use.

Is this the right place to discuss it?

[vcardon]

However, the licensing model seems slightly complicated for my intended use.

Is this the right place to discuss it or not?

Yes, this is a good place to discuss any questions you may have. Tell us about your use case and we'll find the best way to proceed.

[Tranbert]

Okay, after a day of frantic efforts installing OpenVPN for people who are only just waking up... I'll elaborate on my question about licenses:

I have a variable number of machines, which tends to increase (for now), so I can estimate an initial "stock" of licenses to buy, with a little extra if necessary.

But to add more licenses, I understand it involves a manual process: ordering, payment, collection, and delivery.

However, when I take over a client or new machines, I often have to put them into production or management mode immediately. The risk is switching all the machines to community mode as soon as an "extra" machine is added, which isn't very nice for existing clients.

I'm well aware that license management seems to be all-or-nothing.

But ideally, if we could have a defined number of professional licenses, and the subsequent ones become community licenses before being regularized, that would mitigate the risk of mistakes...

Is that a feasible way of working?

[vcardon]

But ideally, if we could have a defined number of pro licenses, and the subsequent ones become community licenses before regularization, that would mitigate the risk of mistakes...

Is that a feasible system?

That's more or less how it already works. If the number of devices equipped with a WAPT agent exceeds the subscribed number, then the console switches to Community mode without data loss. The same happens if the contract expires.

By increasing the number of licenses above the number of equipped devices or by renewing the contract, the Enterprise features return.

We are looking at what we can do to improve the administrative and commercial process to allow more flexibility for low-volume orders.

In the meantime, the best approach is indeed to anticipate your volume increases. And if you find yourself stuck, we're human and never far from the phone to answer your questions and find a solution with you.

Sincerely.

Vincent

[Tranbert]

We are looking at what we can do to improve the administrative and sales process to allow more flexibility for low-volume orders.

In the meantime, the best approach is indeed to anticipate your volume increases. And if you find yourself stuck, we are human and never far from the phone to answer your questions and find a solution with you.

Okay, great.

Well, I think my type of use is quite marginal, so don't waste resources on it; it just so happens that I also have a phone and that I am sometimes human...

[Lamidupc]

Hello,

I'm currently exploring Wapt. I've already installed it locally on a Debian VM. It's really very interesting.

For my small maintenance business, I'm trying to use tools that I have the most complete control over, but that aren't hosted at my workplace... I use Dolibarr for accounting and invoicing, GLPI for asset tracking, and MeshCentral for remote control of client PCs. Each solution is on its own hosted server (OVH).

From this perspective, Wapt is exactly the missing link for a true automation solution for software maintenance and workstation updates.

I have a question about the overall architecture: given that my client base includes "entities" of 30-40 workstations, but also small companies with 3-4 laptops and no local servers, what would be the best solution to have a single point of management and be able to use all of Wapt's features?

- A "master" WAPT server hosted like my other solutions and accessible via wapt.mydomain.com
- A local mirror in each larger company for packages/updates.
- But the question arises regarding isolated clients...

And more importantly, is WAPT designed to be exposed on an external server or should it be kept in a purely LAN environment? And in the latter case, how do you manage multi-site licenses in the Enterprise version?

I haven't really found a direct answer to these questions, so I'm posting them here. Thank you for your insights and congratulations again on the work!

Hello, I'm contacting you again regarding the use of GLPI on an OVH hosted server. I also use Dolibarr, installed on OVH, but I can't seem to do the same thing with GLPI...
Could you explain the procedure to me if possible?
Sincerely.