Hello,
I have several WAPT packages in my repository with a few test machines.
I want to deploy a package or a group of packages to all of my machines. Do I have to add the package to each machine manually, or is there a way to add a package to all machines, or at least a group of machines?
Installed WAPT version: 1.8.2
Server OS: Linux Debian 4.19
Administration/package creation machine OS: Windows 10
Thank you
[RESOLVED] Deploying a package to a group of workstations
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
-
Geovariances
- Messages: 15
- Registration: July 28, 2020 - 10:56 AM
Last edited by Geovariances on August 7, 2020 - 3:31 PM, edited 2 times.
-
Patrice_minagri
- Messages: 57
- Registration: Oct 21, 2016 - 4:56 p.m.
Hello,
Perhaps by associating a package group (previously created, even empty) with each workstation (selecting all workstations and adding the package group as a dependency).
This way, packages can later be added to this group, which is common to all workstations, so that the packages are installed there.
The advantage is that over time, packages can be added or removed from the group without having to reassign subsequent packages directly to those workstations. The work will be done through the group.
Patrice
Perhaps by associating a package group (previously created, even empty) with each workstation (selecting all workstations and adding the package group as a dependency).
This way, packages can later be added to this group, which is common to all workstations, so that the packages are installed there.
The advantage is that over time, packages can be added or removed from the group without having to reassign subsequent packages directly to those workstations. The work will be done through the group.
Patrice
WAPT 1.7.4
-
Geovariances
- Messages: 15
- Registration: July 28, 2020 - 10:56 AM
-
Geovariances
- Messages: 15
- Registration: July 28, 2020 - 10:56 AM
Indeed, it seems to work via this method, even if it's not a very natural way of doing things because we select a group of packages and not a group of stations.Patrice_minagri wrote: ↑August 5, 2020 - 4:13 PM Hello,
Perhaps by associating a package group (previously created, even empty) with each workstation (selecting all workstations and adding the package group as a dependency).
This way, we can later add packages to this group, which is common to all workstations, so that the packages are installed there.
The advantage is that over time, we can add or remove packages from the group without having to reassign subsequent packages directly to those workstations. The work will be done through the group.
Patrice
-
Geovariances
- Messages: 15
- Registration: July 28, 2020 - 10:56 AM
