Page 1 of 1

Errored workstations - machine configuration

Published: October 3, 2017 - 2:49 PM
by MDM-SI
Hello,

Following a series of software demonstrations with various test packages, and a wave of software updates/installations, many machines are showing errors.
I've tried deleting packages from the repository, removing the WAPT folders and archives from the hard drive, deleting package groups, "uninstalling" packages, and even forgetting about them, but nothing works.

I then tried resetting the machines by selecting "Delete the machine and its configuration," but as soon as the machine updates, it reverts to its error status, as if its configuration hadn't been deleted (contrary to what the window that opens indicates).
I've tried following the instructions provided here, but nothing helps. I even have fewer files than machines in the console inventory.

I updated the WAPT server with the latest version available on the website, but the problem persists.

Wapt console version: 1.3.13.0.
Server and console installed on Windows Server 2012 R2, with Apache.

Re: Errored workstations - machine configuration

Published: October 3, 2017 - 9:33 PM
by sfonteneau
Hello,

you need to remove the package or forget the package and remove the dependency from the workstations.

Warning:
- If the dependency is still present, the package will reappear.
- If the machine is unavailable when you forget or uninstall it, this will not work.
- An upgrade may be necessary after all these steps.

The error status is logged in c:\wapt\db\waptdb.sqlite on each agent.

Simon

Re: Errored workstations - machine configuration

Published: October 10, 2017 - 8:38 AM
by MDM-SI
Hello,

I've tested all of that, but I'm still getting errors on some machines, including some that I'm sure are powered on and connected to the network.

What I don't understand is the "Delete the machine and its configuration" option.
If the computer's status is recorded in the agent's log, it implies that the server can send the command to reset the waptdb.sqlite file.
However, this isn't working for me.

Re: Errored workstations - machine configuration

Published: October 10, 2017 - 09:08
by sfonteneau
MDM-SI wrote: Oct 10, 2017 - 8:38 AM Hello,

I've tested all of that, but I still have some workstations showing errors, including workstations that I'm sure are turned on and on the network.

What I don't understand is the "Delete the machine and its configuration" option.
Doc: https://www.wapt.fr/fr/doc/Utilisation/ ... figuration
Doc2: https://www.wapt.fr/fr/doc/Theorique/in ... quets-hote

The option allows you to remove the machine from the wapt inventory and also to delete the machine package.
This has no impact on the SQLite database
MDM-SI wrote: Oct 10, 2017 - 8:38 AM If the computer's status is recorded in the agent's folder, this implies that the server can send the command to reset the waptdb.sqlite file.
However, this doesn't work for me.
The agent's file ????

Re: Errored workstations - machine configuration

Published: October 19, 2017 - 4:14 PM
by MDM-SI
I was referring to the folder created during the installation of the agent: C::\wapt.

If we delete the machine package, does this not delete the history of installed packages, packages with errors, or packages marked as needing upgrade?
sfonteneau wrote: Hello,

you need to remove the package or forget the package and remove the dependency from the machines.

Warning:
- If the dependency is still present, the package will reappear.
- If the machine is not available at the time of forgetting or uninstallation, it will not work.
- An upgrade may be necessary after all these steps.
I've tried all that, but the error persists. This includes mine, which is switched on, connected to the network, and isn't doing anything unusual (no programs open, etc.).

In short, I don't see how, on about fifty machines/workstations, to reset the status to the default "ok" before deploying new programs or updates.

Moreover, although initially I suspected a problem with my packages given the number of affected workstations, on some computers everything went well/was installed.

I did remove my previous packages and package groups. So far, I've just redeployed the new version of Firefox without any particular problems, except that on the same machines, the error persists.

I could potentially remove wapt from these machines via GPO, then reinstall it, but I would prefer a less "brutal" solution.