[RESOLVED] Computer Group and Package Group

[david.debray]

Hello everyone,

I'd like to create computer groups in the WAPT console. I work in a clinic, so for now I have 3 groups (easier for deploying my applications):
- IT
- Administration
- Care

I'd like to assign package groups (these groups already exist):
- BASE: Base package with WAPT and Fusion Inventory dependencies for inventorying the equipment
- Care: Programs related to care stations
- Administration: Programs related to administration stations
- IT: ... you get the idea ^^
- WAPTDEV: Packages for installing the WAPT console


All workstations in the domain should automatically receive the BASE package group as soon as they are detected by the console.

How can I do this?
Thank you in advance for your help.

[sfonteneau]

But for now it doesn't work in 1.5.22 viewtopic.php?f=10&t=1070#p3698

It should be tested in version 1.5.1.23, it should work.

[tdejesus]

Hello,

I'm on version 1.5.1.23 and I have the same problem.

[dcardon]

Hello david.debray,

All workstations in the domain should automatically receive the BASE packet group as soon as they are detected by the console.

How can I do this?
Thank you in advance for your help.

One way to do this is to assign a parameter when installing waptagent with waptdeploy, see. https://www.wapt.fr/en/doc/Configuratio ... index.html

Sincerely,

Denis

[david.debray]

OK, thanks, but that doesn't apply to my situation...
Let me explain: In the company, the GPOs were created by someone else without documentation or any apparent structure. Since I'm new, I'm avoiding touching them for now.

We're in the middle of a software migration, and I'm taking this opportunity to integrate the WAPT deployment into the batch script.
Here's what I'm using for WAPT:
`\\vm-admin\sa\waptagent.exe -updp "\\vm-admin\sa" /SILENT /NOICONS /SUPPRESSMSGBOXES /StartPackages=BASE`.

WAPT installs correctly, but the BASE package group isn't assigned to the machines... So I started adding
`wapt-get install BASE` to my script, but this option doesn't create any dependencies...

Is it possible to assign dependencies via the command line?

Sorry to be a pain . Thanks for any help!

[dcardon]

OK thanks, but that doesn't apply to my situation...

WAPTDeploy can be used even outside of a GPO. It is much lighter than waptagent.exe, and only initiates the agent download when necessary.

Let me explain: In the company, the GPOs were created by someone else without documentation or any apparent structure. Being new, I'm avoiding touching them for now.

We're in the middle of a software migration, so I'm taking the opportunity to integrate the WAPT deployment into the batch script.
Here's what I'm using for WAPT:
\\vm-admin\sa\waptagent.exe -updp "\\vm-admin\sa" /SILENT /NOICONS /SUPPRESSMSGBOXES /StartPackages=BASE

WAPT installs correctly, but the BASE package group isn't assigned to the machines...

The StartPackages option is supposed to launch the installation of the package on the machine after the agent is installed. However, it should launch the installation of the package and its dependencies after the agent is installed. If this is not the case, it's a bug.

So I started adding:
`wapt-get install BASE` to my script, but this option doesn't create a dependency...

Can I assign dependencies via the command line?

Sorry to be a pain . Thanks for the replies!

It's normal that the package in question isn't automatically added as a dependency to the machine. "Machine package" configurations are signed by the administrator, and the signing key is, of course, not available on the workstations during deployment. If you want to do things differently, you'll need to use a less secure product

However, the packages should indeed be present on the machine. A small caveat: /StartPackages uses the same methodology you indicated, that is, launching a wapt-get install BASETherefore, if the machine is restarted at that point, not all the packages may be installed. We will improve this by storing the current installation state in the local SQLite database, which will make the process more reliable.

Sincerely,

Denis

[david.debray]

Good morning,

Thanks for the replies, but unfortunately I'm still stuck...

I tried:

The only solution I found with the Community version is to link an AD security group to a package group on the WAPT side. https://www.wapt.fr/fr/doc/Utilisation/ ... de-paquets

Then, populate this security group with the machines on the AD side.

A security group on the WAPT_SI DC with a corresponding packet group, I tested it with two different machines (just in case) ) no joy...

When I go to the console and run "Add AD groups as dependency packages," I get "machines ignored (error)."

The command: "waptdeploy.exe --hash=ef94a1f674fe9072d2cd7eb6f9fa0ab8d8d353d398a7c241a8eebabea25fd0d7 --minversion=1.5.1.23 --wait=15 /StartPackages=Compdinateurs" completes without error but does not create a dependency.

Any ideas? Thanks in advance for your help