[SOLVED]Deploying WaptAgent GPO windows 7

[skoizer]

Good morning

I'm having trouble deploying the agent via GPO
I have correctly set up a machine GPO and I understand that the network is up to launch the GPO.
Using the command below as a local or domain administrator, it works; the WAPT agent installs

waptdeploy.exe --hash=myHash --minversion=1.5.1.23 --wait=15 use_fqdn_as_uuid=1 --waptsetupurl=https://srvwapt01/wapt/waptagent.exe
But nothing in GPO except under Windows 10 this gpo has no problems.
Windows 10 and Windows 7 have the same GPOs in my Active Directory
To simulate the installation under Windows 7 and Windows 10, I tested installing with psexec

see doc https://specopssoft.com/blog/how-to-bec...th-psexec/
"autorite nt\system"
Here is the error I got

Code: Select all

c:\tmp>waptdeploy.exe --hash=maHache
acae2f7ab4c78 --minversion=1.5.1.23 --wait=15 use_fqdn_as_uuid=1 --waptsetupurl=
https://srvwapt01/wapt/waptagent.exe
WAPT version:
WAPT required version: 1.5.1.23
Wapt agent path: C:\Windows\TEMP\waptagent.exe
Wget new waptagent from https://srvwapt01/wapt/waptagent.exe
Trying to reach https://srvwapt01/wapt/waptagent.exe...
Reachable, downloading...
Done.
Cleanup...
Unable to update immediately: Unable to download: http://127.0.0.1:8088/update.json?notify_server=1&notify_user=0 HTTP Status: 0
An unhandled exception occurred at $00416608:
EFOpenError: Unable to open file "C:\Windows\TEMP\waptagent.exe"
  $00416608
  $004164B0
  $00440216
  $004047C9

with Windows 10, which is why it works

Code: Select all

waptdeploy.exe --hash=maHache
acae2f7ab4c78 --minversion=1.5.1.23 --wait=15 use_fqdn_as_uuid=1 --waptsetupurl=
https://srvwapt01/wapt/waptagent.exe
WAPT version:
WAPT required version: 1.5.1.23
Wapt agent path: C:\windows\TEMP\waptagent.exe
Wget new waptagent from https://srvwapt01/wapt/waptagent.exe
Trying to reach https://srvwapt01/wapt/waptagent.exe...
Reachable, downloading...
Done.
SHA256 hash of downloaded setup file: 6f8d08eb448042eb1562063b93299093cec484e98936fcfbb3dacae2f7ab4c78
OK : Hash of waptagent match expected hash.
Got version: 1.5.1.23
Unable to speak with waptservice... continue (Unable to download: http://127.0.0.1:8088/tasks.json HTTP Status: 0)

Install ...
Launching C:\windows\TEMP\waptagent.exe /VERYSILENT /MERGETASKS=""useWaptServer""
Install OK : 1.5.1.23
Cleanup...

Does anyone have any idea what the problem might be with the installation?.
The system might not have the correct permissions?
I compared the permissions of C:\Windows\TEMP under Windows 10 and Windows 7 and it's the same

[skoizer]

Hello,
I tried installing waptagent.exe with the "nt authority\system" account and it worked.
So the problem is with watdeploy.exe.
It's a shame there isn't a command to get more logs.
Are there any known bugs with Windows 7 and waptdeploy?

[dcardon]

Good evening Skoizer,

Hello,
I tried installing waptagent.exe with the "nt authority\system" account and it works.
So the problem is with waptdeploy.exe.
It's a shame there isn't a command to get more logs.
Are there any known bugs in Windows 7 and waptdeploy?

Could you check if your antivirus software is deleting the file before it can be installed?

Sincerely,

Denis

[greening]

Hello,

sorry to revive this thread, but I'm practically in the same situation.

Following the installation of WAPT 1.6.2.7 to replace WAPT 1.3.12.13,

I created a GPO that works correctly if I don't set "use_fqdn_as_uuid=1", but we want to keep the FQDN.

Can you confirm that it's possible to pass it as an argument to waptdeploy, and if so, please provide the detailed command.

Regards

[dcardon]

Hello verdierr,

Sorry to revive this thread, but I'm practically in the same situation.

Following the installation of wapt 1.6.2.7 to replace wapt 1.3.12.13,

I created a GPO that works correctly if I don't set "use_fqdn_as_uuid=1", but we want to keep the FQDN.

Can you confirm that it's possible to pass it as an argument to waptdeploy, and if so, please provide the detailed command.

I recommend you start with version 1.7; it is possible to configure this setting directly when creating the agent.

Sincerely,

Denis

[greening]

Hello,

thank you, I just installed version 1.7.3.3.
The checkbox when creating the agent is exactly what we wanted.

Have a good day.

[James]

Hello,
I have exactly the same problem: after updating to version 1.6.2, waptdeploy doesn't work at all on Windows 7, while it works perfectly on Windows 10. I downloaded the latest version of waptdeploy, but the problem persists. My antivirus isn't the cause, as it's disabled for testing.
I also tried adding the parameter `--waptsetupurl=` (using HTTP, not HTTPS) to the Group Policy Object (GPO) and setting it to `--force`. The problem remains. Does version 1.7 fix this issue? I'd prefer to avoid updating initially. Would it be advisable to configure the GPO directly with the Waptagent instead of waptdeploy?
Thank you


Same error code as the colleague for win7:
c:\tmp>waptdeploy.exe --hash=maHache
acae2f7ab4c78 --minversion=1.5.1.23 --wait=15 use_fqdn_as_uuid=1 --waptsetupurl=
https://srvwapt01/wapt/waptagent.exe
WAPT version:
WAPT required version: 1.5.1.23
Wapt agent path: C:\Windows\TEMP\waptagent.exe
Wget new waptagent from https://srvwapt01/wapt/waptagent.exe
Trying to reach https://srvwapt01/wapt/waptagent.exe...
Reachable, downloading...
Done.
Cleanup...
Unable to update immediately: Unable to download: http://127.0.0.1:8088/update.json?notif ... ify_user=0 HTTP Status: 0
An unhandled exception occurred at $00416608:
EFOpenError: Unable to open file "C:\Windows\TEMP\waptagent.exe"
$00416608
$004164B0
$00440216
$004047C9