WAPTDEPLOY.EXE deployment error via GPO

[alxinfo]

I'm answering my own question; by rebuilding the WAPT agent, the correct configuration can be redeployed via GPO and WAPTDEPLOY.

Now I still need to authorize it in User Account Control; if I find a solution, I'll post an update here.

[agauvrit]

You have followed the correct procedure; an agent rebuild is necessary to define the correct parameters for:

• - the WAPT server address
  - the main WAPT repository address

Related documentation: https://wapt.fr/fr/doc/Installation/wap ... nsole-wapt

I didn't understand about user account control, what is it?

GPO installations are launched in the System account, WAPT uses a service in the system account.

[alxinfo]

I didn't test the deployment via GPO, only using the BAT command, which explains why it asked me for installation validation (user account control).

I'm testing the deployment via GPO now.

[alxinfo]

After testing... the GPO doesn't work, but I have several leads. For example, the administrator account is disabled on the domain, and a third-party user is a domain admin. Could that make a difference?

As a reminder, here's the link in my GPO for WAPTDEPLOY and then the command

: The link: \\srv-ot\SYSVOL\ot.local\scripts\waptdeploy.exe

And the parameters: waptdeploy.exe --hash=f9eb3f7be7cd5796f23da667341b9a245f3caa691f2fa44cf27f2253984e9aaa --minversion=1.3.9.3 --wait=15

Via script = OK
Via GPO = Doesn't work

[sfonteneau]

First, check that you have correctly created a computer GPO!

The administrator account is not involved because GPOs are launched with the system account when the machine starts up.

However, I think you are experiencing a Microsoft behavior:

http://winintro.com/?Category=Windows_8 ... uage=fr-fr

By default, Microsoft does not wait for the network to be available at startup before applying GPOs.

This problem is becoming increasingly common with the new generation of ever-faster PCs. The problem is that waptdeploy needs a network connection to download waptagent.exe.

Solution:

Enable "Always wait for network access": Computer Configuration > System > Logon > Always wait for network access...

Ironically, for this GPO to activate at startup, the network must be available at startup... QED...

So, for your tests, in order, enable the GPO and then run `gpupdate /force` on the machine for the new setting to take effect. (Or wait 90 to 120 minutes for the GPOs to be cached.)

Alternatively, a workaround: Enable waptdeploy when the computer shuts down.

Keep us posted!

[Paul]

Hello,

I installed the WAPT console version 1.5.1.26 on a Windows 2008 server for testing purposes.
I believe this first part was successful since I can manually install the WAPT agent.
I would like to be able to deploy the WAPT agent automatically, but I haven't been able to.

I can install WAPT by manually accessing the executable on my server via:
https://my_wapt_server_ip/
or via:
Win + R -> http://my_server_ip/wapt/waptagent.exe.

I have correctly configured a Group Policy Object (GPO) (active at startup and shutdown) applied only to the computers that will have the WAPT agent installed.
I also tried applying the GPO to a user to change their desktop background, which worked.

I uninstalled Sophos from the computer, thinking it might be blocking the agent installation.

When I restart my computer, I get the following error:

WAPT version:
WAPT version required: 1.5.1.26
wapt agent path: C:\Windows\Temp\waptagent.exe
Wget new wpatagent from https://ipdemon_serveur_wapt/wapt/waptagent.exe...
Reachable, downloading...
Done.
Cleanup...

So I'm currently a bit stuck. If you have any ideas,
thank you.