Hello,
I'm an IT service provider for several clients, and
I'm currently testing WAPT Enterprise.
My question is:
is it possible to manage the IT infrastructure (updates, package deployments) of my various clients from a single console located within our company?
If so, could you please provide me with a brief procedure?
Thank you in advance for your help.
Have a good day.
managing the IT infrastructure of our various clients on a single console
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Cédriclj,
If you're dealing with small clients, the best approach is to put them on the same WAPT server, without giving them access to the console, but only to self-service. Then, it's possible to create a separate self-service package for each client with the software they can install (Enterprise version only).
The WAPT server can be directly connected to the internet with proper security (authentication via client certificate directly on the nginx server). Currently, this requires configuration, but it will be integrated directly into the Enterprise version in a future release.
Alternatively, there's also the option to configure the console to connect to multiple WAPT servers and display an aggregated view. This allows for an architecture where the largest clients have their own server with console access, and the IT manager can have a single console that aggregates data from the different servers. This feature is in tech preview and is not yet well documented.
Best regards,
Denis
If you're dealing with small clients, the best approach is to put them on the same WAPT server, without giving them access to the console, but only to self-service. Then, it's possible to create a separate self-service package for each client with the software they can install (Enterprise version only).
The WAPT server can be directly connected to the internet with proper security (authentication via client certificate directly on the nginx server). Currently, this requires configuration, but it will be integrated directly into the Enterprise version in a future release.
Alternatively, there's also the option to configure the console to connect to multiple WAPT servers and display an aggregated view. This allows for an architecture where the largest clients have their own server with console access, and the IT manager can have a single console that aggregates data from the different servers. This feature is in tech preview and is not yet well documented.
Best regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
