[RESOLVED] GPO agent deployment issue

[Christophe]

Good morning,
I am on Windows Server 2022 with Wapt version 2.4.014143

I created a GPO that sets up a scheduled task to deploy the WAPT agent to my client workstations.

Everything worked correctly until the upgrade to version 2.4.0.14143 of WAPT.

I modified the hash as usual (--hash=5e80905b087b20818631dcbe765d89a788df2a5140bd55e5413e152d43861fd6 --minversion=2.4.0.14143 --wait=15 --waptsetupurl=http://"IP of my server"/api/v3/get_waptagent_exe/{{ip}}/waptagent.exe)

I tried running the command directly from PowerShell. Here's the error I'm getting:

Code: Select all

WAPT version: 
WAPT required version: 2.4.0.14143
Wapt agent path: C:\Users\ADMINI~1\AppData\Local\Temp\waptagent.exe
Wget new waptagent from http://172.18.50.13/api/v3/get_waptagent_exe/
Trying to reach http://"IP de mon serveur"/api/v3/get_waptagent_exe/...
Expecting hash sha256: 5e80905b087b20818631dcbe765d89a788df2a5140bd55e5413e152d43861fd6
Using proxy : 
Error trying to get http://"IP de mon serveur"/api/v3/get_waptagent_exe/ : Error downloading http://"IP de mon serveur"/api/v3/get_waptagent_exe/: [EHttpSocket] THttpClientSocket.WGet:
 "IP de mon serveur":80/api/v3/get_waptagent_exe/ failed as HTTP Error 404 - Not Found... sleeping
Delete sheduled task "fullwaptupgrade"
c:\temp\waptdeploy.exe : An unhandled exception occurred at $004038EC:
Au caractère C:\Users\Administrateur\Desktop\Pb Wapt.ps1:1 : 1
+ c:\temp\waptdeploy.exe --hash=5e80905b087b20818631dcbe765d89a788df2a5 ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (An unhandled ex...d at $004038EC::String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
 
Exception: Error downloading http://"IP de mon serveur"/api/v3/get_waptagent_exe/: [EHttpSocket] THttpClientSocket.WGet: "IP de mon serveur"/api/v3/get_waptagent_exe/ failed as 
HTTP Error 404 - Not Found
  $004038EC
  $00404A87

Do you have any idea where the problem comes from?

[dcardon]

Hi Christophe,

have you updated the waptdeploy.exe binary in the GPO to the latest version? We've added support for {{ip}} to allow the use of the remote repository during the initial deployment.

Also, did you restart the postconf after the update?

Regards,

Denis

[Christophe]

Yes, I've updated the Waptdeploy binary.

However, what is postconf?
How do I restart it?

[Christophe]

Can anyone help me?

I'm using Windows Server 2022, and I'm not sure if I'm affected by postconf.

[sfonteneau]

In your GPO, have you replaced waptdeploy with the latest version?


It's available on the server:
https://srvwapt.mydomain.lan/wapt/wapta ... deploy.exe

[Christophe]

Yes, I replaced it correctly.

[sfonteneau]

Does this work in your browser?

https://srvwapt.mydomain.lan/api/v3/get ... tagent.exe

[Christophe]

No, unfortunately.
After accepting the risk because the self-signed certificate isn't secure, I get this message:
Internal Server Error.

The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.

[sfonteneau]

Do you have any secondary deposit rules?

[Christophe]

Yes, indeed, I have rules based on the agents' IP addresses because I have 2 remote repositories