Tranquil IT Forum

Hello everyone,

I am testing WAPT at the company I work for.
It is currently fully functional on our infrastructure, but we installed it directly with the agent on a few workstations.

I would like to put it into production across our entire fleet but I have a problem with the deployment GPO available in the documentation.

So I successfully created a GPO following the wapt documentation on our Windows 2008 R2 server.

Computer GPO -> Policies -> Windows Settings -> Scripts -> Startup

waptdeploy.exe in my script folder and the parameters containing the information I retrieved from my wapt server:
--hash=(myhash) --minversion=1.7.4.6165 --wait=15
But I'm not getting any updates from my GPO. (My other GPOs are working without any problems)

I am reaching out to you for guidance on my problem; I have already looked at related topics, but it doesn't solve anything.
Help me!

Windows 10 1903 workstation
WAPT 1.7.4

Good morning,

By not explicitly specifying the WAPT agent download address as an argument (--waptsetupurl="http://xxxxxx/wapt/waptagent.exe"), the utility waptdeploy.exe will attempt to retrieve this address automatically via several DNS queries:

• SRV type record _wapt._tcp

• CNAME record at wapt.mydomain.com

• Type A record at wapt.mydomain.com

If no DNS query returns a result, then the WAPT agent cannot be downloaded and installed on the machines.

Sincerely.

Yoann wrote: ↑September 27, 2019 - 4:01 PM Good morning,

By not explicitly specifying the WAPT agent download address as an argument (--waptsetupurl="http://xxxxxx/wapt/waptagent.exe"), the utility waptdeploy.exe will attempt to retrieve this address automatically via several DNS queries:

• SRV type record _wapt._tcp

• CNAME record at wapt.mydomain.com

• Type A record at wapt.mydomain.com

If no DNS query returns a result, then the WAPT agent cannot be downloaded and installed on the machines.

Sincerely.

I just tried it by adding the argument --waptsetupurl

--waptsetupurl="http://10.8.100.40/wapt/waptagent.exe" --hash=monhash --minversion=1.7.4.6165 --wait=15

I still didn't have a positive result, but the script wouldn't run due to a permissions issue... Oops!

Thank you for your help