Page 1 of 1

[SOLVED] Identifying a "ghost" packet

Published: May 16, 2022 - 7:30 PM
by adm.rb01
A long time ago I installed version 1.8 of WAPT to test it on a machine.
Since then, the subject had fallen into disuse, and now the opportunity has arisen again. The original machine is switched off.

So I decided to reinstall Discovery version 2.2 and start from scratch.

During the agent installation on a test machine, I see that a package is installed in addition to the test Notepad++.
No matter how many times I uninstall it, it keeps trying to put itself in the dependencies and I don't understand where this could be coming from.

Code: Select all

Installing 4C4C4544-0047-3710-8042-C6C04F463633(=7)
Delete C:\Program Files (x86)\wapt\cache\4C4C4544-0047-3710-8042-C6C04F463633.wapt
Installé : 4C4C4544-0047-3710-8042-C6C04F463633(=7)
I'm a bit lost on how to analyze/remove this "unwanted" package.
Do you have any leads?

With thanks :oops:

Re: Identifying a "ghost" packet

Published: May 17, 2022 - 1:29 PM
by dcardon
Hello,

this is the "machine" package, i.e., the package containing the list of packages that the machine must have installed (see documentation). The UUID in question, which is used for the name of the "machine" package, corresponds to the machine's BIOS UUID.

Regards,

Denis

Re: [SOLVED] Identifying a "ghost" packet

Published: May 17, 2022 - 1:41 PM
by florian777
Hello,
I wanted to revisit this issue. A colleague is trying to set up WAPT, but the package isn't available on any of his clients, and he can't deploy any software to them. Is there a way to install it manually?

Thank you.


Server: Windows 2016,
WAPT version 2.1.1.11935

Re: [SOLVED] Identifying a "ghost" packet

Published: May 17, 2022 - 1:44 PM
by dcardon
The machine package is an implicit package that the machine will want to install by default (i.e., it doesn't need to be assigned the package; it will look for it itself, like OU packages or profile packages).

If the machine package doesn't install (or doesn't update to the latest version), it's because it has a dependency that couldn't be installed, or it's incorrectly signed.

You can try running `wapt-get upgrade -l debug` on the machine in question to see what it says.

Regards,

Denis

Re: [SOLVED] Identifying a "ghost" packet

Published: May 17, 2022 - 1:53 PM
by adm.rb01
Thank you for your explanation!

Indeed, now it makes sense to me! 8-)