Deployment filters
Published: August 14, 2024 - 08:29
Hello,
We've been using WAPT for about 5-6 months now and are generally satisfied with the tool, but coming from SCCM, we realize that we're missing some features.
Specifically, the ability to filter package deployment based on certain criteria before downloading the package to the workstations.
For example, let's say we have a fairly large piece of software (>1GB) that needs to be installed on all workstations except for virtual machines spread across the OUs.
Unless I'm mistaken, there's no way to do this in WAPT.
Of course, we can add conditions to the setup.py file and tell the tool to do nothing if it installs a VM, but to still complete the script. But this means having to cobble together several packages where we'd like to install just one, or telling WAPT that the package has installed when it hasn't actually done anything.
Given that WAPT has knowledge of the hardware and even software components of each workstation, I think it would be extremely useful to be able to use this data for deployments BEFORE downloading the packages to each workstation (and therefore running setup.py).
Another example: we want to deploy VPN software across an entire network, but only on laptops and not desktops. Knowing that all the workstations are mixed in different OUs and that there is no AD group encompassing all the desktops or all the laptops,
it would be incredibly useful to be able to launch the deployment at the root level, thus covering the entire network with some kind of exclusion, thereby avoiding unnecessary downloads on the desktops.
While waiting for a possible addition of this kind of functionality, I will continue to browse the numerous community sharing tools to try to find good solutions to these problems!
We've been using WAPT for about 5-6 months now and are generally satisfied with the tool, but coming from SCCM, we realize that we're missing some features.
Specifically, the ability to filter package deployment based on certain criteria before downloading the package to the workstations.
For example, let's say we have a fairly large piece of software (>1GB) that needs to be installed on all workstations except for virtual machines spread across the OUs.
Unless I'm mistaken, there's no way to do this in WAPT.
Of course, we can add conditions to the setup.py file and tell the tool to do nothing if it installs a VM, but to still complete the script. But this means having to cobble together several packages where we'd like to install just one, or telling WAPT that the package has installed when it hasn't actually done anything.
Given that WAPT has knowledge of the hardware and even software components of each workstation, I think it would be extremely useful to be able to use this data for deployments BEFORE downloading the packages to each workstation (and therefore running setup.py).
Another example: we want to deploy VPN software across an entire network, but only on laptops and not desktops. Knowing that all the workstations are mixed in different OUs and that there is no AD group encompassing all the desktops or all the laptops,
it would be incredibly useful to be able to launch the deployment at the root level, thus covering the entire network with some kind of exclusion, thereby avoiding unnecessary downloads on the desktops.
While waiting for a possible addition of this kind of functionality, I will continue to browse the numerous community sharing tools to try to find good solutions to these problems!
