Hello,
I've been a WAPT user for a few years (Enterprise Edition, currently v2.4.0.14143 / rev 2.4.0.14143-9847ee8b) and we're starting to encounter a problem related to IT resource sharing.
Is there a way to group machines without changing the Active Directory (AD) structure?
The idea is to keep the structure defined in AD, which is often geographical, say, one organizational unit (OU) per building and its sub-OUs per room, and add a functional layer, for example, all the machines used by a category of staff, machines that are distributed across several buildings in different rooms.
Perhaps this is a feature request: the ability to switch from the geographical view (AD) to the functional view (managed in WAPT) in the console.
Example:
<AD>
[Building A]
(Room A1)
pc1
pc2
pc3
(Room A2)
pc4
pc5
[Building B]
(Room B1)
pc10
pc11
pc12
I want to assign packages to a group of machines: pc1, pc2, pc4, and pc10. Is there a way to do this all at once?
Currently, I use the "All" view and select the machines to then press Shift+Ctrl+O to modify multiple machines, but I have to reselect each time. If we could save this functional group under a name like "Administrative Workstations," for example, it would make it easier to manage the software suites needed for a function that uses machines shared between several buildings.
Thank you for taking the time to read this. If you have any ideas, I'd appreciate them.
Create groups of machines outside the UO
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello,
if you wish to stick with an Active Directory model, you can use AD groups and profile packages.
https://www.wapt.fr/fr/doc/wapt-console ... se-feature
This way, you create your groups in AD, add your machines to the groups, and then create a profile package with the same name. The member machines will then install the corresponding profile package.
Without using Active Directory, you can more simply create a group package (one of WAPT's oldest features):
https://www.wapt.fr/fr/doc/wapt-console ... up-package
You create your group package "administrative workstations," and add the "administrative workstations" package as a dependency. The machines must be members of this group.
Now, to manage the "administrative workstations" machines, you just need to add dependencies to the "administrative workstations" package.
You can even filter which machines have "administrative workstations" as dependencies from the inventory tab using "WAPT groups."
if you wish to stick with an Active Directory model, you can use AD groups and profile packages.
https://www.wapt.fr/fr/doc/wapt-console ... se-feature
This way, you create your groups in AD, add your machines to the groups, and then create a profile package with the same name. The member machines will then install the corresponding profile package.
Without using Active Directory, you can more simply create a group package (one of WAPT's oldest features):
https://www.wapt.fr/fr/doc/wapt-console ... up-package
You create your group package "administrative workstations," and add the "administrative workstations" package as a dependency. The machines must be members of this group.
Now, to manage the "administrative workstations" machines, you just need to add dependencies to the "administrative workstations" package.
You can even filter which machines have "administrative workstations" as dependencies from the inventory tab using "WAPT groups."
