[RESOLVED] waptdeploy parameter {{ip}} not working

[stephaneB]

Hello,
as the title indicates, for the past few days the deployment command line has stopped working because the parameter {{ip}} is no longer being translated by waptdeploy. I had to replace it with the server's IP address to fix it.
So there's no rush, but if anyone has an explanation or solution, I'd appreciate it. Thanks.

[blemoigne]

Hello,
is the command launched via PowerShell? PowerShell interprets the mustaches.

[stephaneB]

Hello,
no, no, it's an immediate scheduled task that directly launches waptdeploy.exe with its parameters.
It used to work fine, but not anymore...

[sfonteneau]

It used to work fine, but not anymore...

Is there a specific change? A Wapt upgrade or something else?

We looked at it and we can't reproduce the problem here

[stephaneB]

Actually, I'm not sure if it's related, but there was a mistake with the antivirus software that blacklisted waptdeploy.exe and waptservice.exe instead of whitelisting them. We quickly corrected it, but they were soon removed from a large part of the network. :(
The redeployment via GPO went smoothly on many machines, then a number remained unredeployed until I realized, while testing the command line, that this was the problem.
But at this point, correct me if I'm wrong, but is the variable {{ip}} interpreted by waptdeploy.exe?

[sfonteneau]

{{ip}} is the IP address of the workstation.

Waptdeploy replaces {{ip}} with the IP address of the workstation, and the server redirects to a secondary repository if necessary.