Audit empty packages in the case of a new installation via WADS

[esberard]

Hello,

We just upgraded to version 2.6.1.17654 on our production server and I've noticed a bug when deploying a machine via WADS and installing packages through its OU. A number of packages are not showing up for audits in the General tab.

Even using the "Run all package audits" function, these packages remain with an empty audit status (I've tested this multiple times, rebooting and refreshing the machine inventory).

However, if we manually select each package in the General tab with an empty audit status, right-click, and choose "Run package audit" for that group, then the package audits are displayed correctly.

It seems that the "Run all package audits" and "Run package audit" buttons have different functions and therefore produce different results.

Despite this, we've noticed that quite a few of our packages are having trouble automatically submitting their audit trail in version 2.6.1.17654.

Thank you for your feedback.

Rémy

[htouvet]

Hi Rémy,
To compare the behavior in the code, which version of Wapt did you upgrade from?

Hubert

[esberard]

We came from 2.6.1.17576

[sfonteneau]

One more quick question:

Was the machine already in the inventory before deployment?
Is this a redeployment?

[esberard]

Not at all, it's a brand new machine straight out of the box.

[esberard]

I also have a case with a machine that was reinstalled and was already present

audit-wapt.png (134.85 KB) Viewed 7753 times

[htouvet]

Hi Rémy,
Between these two versions, I don't see what could be causing this.

Could you share the current WADs post-installation script?

Ideally, we should take a look at it with screen sharing.

[esberard]

After manually forcing each package to be audited and passing them to OK, I reinstalled the machine and the problem is still the same after the fresh installation:

audit-wapt1.png (79.02 KB) Viewed 7696 times

However, the issue does not seem to be present on your latest release released Wednesday evening (2.6.1.17705).

[esberard]

Hello Rémy,
Between these two versions, I don't see what could be causing this.

Can you share the current post-installation script for wads?

Ideally, we should take a look with screen sharing.

Here is our post-installation script, which is identical between our production environment and the production environment:

ping 127.0.0.1 -n 30
"C:\Program Files (x86)\wapt\wapt-get.exe" ping >> c:\installdir\postscript.log
"c:\installdir\wads.exe" --server-url=https://wapt-xxxxxxxx.fr --send-status="Installing zone certificates"
"C:\Program Files (x86)\wapt\wapt-get.exe" install unistra-ixxxxxx >> c:\installdir\postscript.log
"c:\installdir\wads.exe" --server-url=https://wapt-xxxxxxxx.fr --send-status="Download software update"
"C:\Program Files (x86)\wapt\wapt-get.exe" update -F >> c:\installdir\postscript.log
"c:\installdir\wads.exe" --server-url=https://wapt-xxxxxxxx.fr --send-status="Started windows update"
"C:\Program Files (x86)\wapt\wapt-get.exe" waptwua-install >> c:\installdir\postscript.log
"C:\installdir\wads.exe" --server-url=https://wapt-xxxxxxx.fr --send-status="End windows update installs"
"C:\Program Files (x86)\wapt\wapt-get.exe" update -F >> c:\installdir\postscript.log
"c:\installdir\wads.exe" --server-url=https://wapt-xxxxxxxxx.fr --send-status="Install software update"
"C:\Program Files (x86)\wapt\wapt-get.exe" upgrade -S >> c:\installdir\postscript.log
ping 127.0.0.1 -n 15
"C:\installdir\wads.exe" --server-url=https://wapt-xxxxxxxx.fr --send-status="Rebooting for windows udpate finalization"
shutdown /r

[esberard]

Hello Rémy,
Between these two versions, I don't see what could be causing this.

Can you share the current post-installation script for wads?

Ideally, we should take a look with screen sharing.

You can call me directly if needed.