[WAPT 1.5] GPO deployment issue

[Intra1910]

Hello,

(WAPT Server 1.5.1.23 Debian Stretch 9.4 / Console under W10 / W.Server 2016 for GPOs)

Some workstations don't yet have the WAPT agent installed, and I don't know why.

I chose to deploy via GPO as indicated in the WAPT documentation.
The DeployWAPT command was taken via the WAPT server's web interface, and the script parameters were: "waptdeploy.exe --hash=MyKey... --minversion=1.5.1.23 --wait=15" (which I found in my WAPT server's web interface).

Then, in my GPO, I targeted authenticated users (this is the default) and a group that has access to all PCs.
In the "Delegation" section, I granted edit permissions to the group in question.

It installed on some workstations, but not others...

Do you have any ideas?

Thank you in advance for your answers!

[dcardon]

Hello Intra1910,

(WAPT Server 1.5.1.23 Debian Stretch 9.4 / Console under W10 / W.Server 2016 for GPOs)

Windows Server 2016 --> You should try Samba Active Directory; it's the best AD solution on Linux! For more information, see our wiki at [link to wiki] https://dev.tranquil.it/wiki/Samba4

Some computers don't yet have the WAPT agent installed, and I don't know why.

One problem we occasionally encounter is having Windows workstations with crashed GPO clients. You would need to run `gpupdate /force` in an elevated cmd.exe command prompt to see what it says.

Another fairly common problem with laptops is that the network connection is never available when the computer starts up. If the only installation GPO is a startup GPO, it will never run. In this case, you also need to create a scheduled installation GPO.

I chose to deploy via GPO as indicated in the WAPT documentation.
The DeployWAPT command was run through the WAPT server's web interface, and the script parameters were: "waptdeploy.exe --hash=MyKey... --minversion=1.5.1.23 --wait=15" (which I found in my WAPT server's web interface).

Then, in my GPO, I targeted authenticated users (this is the default) and a group that has access to all PCs.
In the "Delegation" section, I granted edit permissions to this group.

There are no delegations required per se. For targeting, a machine GPO will only apply to machine accounts. Targeting is only necessary if you have servers that you want to exclude from this GPO.

Sincerely,

Denis

[Intra1910]

Okay, thank you for your reply!