Tranquil IT Forum

Good morning,

We are currently testing the product in our park.
We exclusively used the online documentation for the deployment and use of the tool. After two days, we encountered some roadblocks, questions, and needs:

1- I can't find any documentation that details the statuses in the console:

• RUNNING: When enrolling a new agent, the status is OK. Then, I want to push a package to them. After clicking "Start Installations," the remote console displays a popup indicating "1 error." The status consistently changes to RUNNING, with no trace of what is currently being executed in the running tasks

• TO-UPGRADE: I regularly see a package name in my "to-upgrade" list that matches the machine's UUID. What does this correspond to?

2- We tested the deployment of a higher version of Adobe (WAPT package created):

• It worked on 1 device

• On another machine of the same type, I get confirmation that the same package installation was successful, but the old one is still present (even after rebooting). This is confirmed by the WAPT software inventory and also directly on the machine: do you think this is a bug?

3- How can we remove software (which is visible in the inventory) that was not deployed by WAPT? I tried the code indicated here: viewtopic.php?t=835 but I get an error "WAPT" is not defined.
This is clearly a feature we would need to use extensively at the beginning of a production deployment.

Thank you for any help you can provide

Question 3 is solved with the following code:
However, is there a "cleaner" solution because this one is based on the keyword "putty", so it would potentially remove software that contains the same keyword?

To try and answer my questions 1 and 2.

I enabled debug information to understand why neither Checking for Updates nor Adding Packages was working on all my clients, switching them to RUNNING or TO-UPGRADE mode.

I noticed the following error: Whereas just below: When using Tools Preferences, the associated key verification is: OK.

So I'm stuck again.

Hello ADT,

ADT wrote: ↑Oct 19, 2018 - 10:53 PM Question 3 is solved with the following code:

Code: Select all

def install():
if installed_software('putty')
    for uninstall in installed_software:
        run(WAPT.uninstall_cmd(uninstall['key'])

However, is there a "cleaner" solution because this one is based on the keyword "putty", so it would potentially remove software that contains the same keyword?

You can retrieve the uninstallation key from the WAPT console in the "software inventory" tab when you select a machine. Copy the key in place of "uninstall['key']".

The PuTTY example is interesting. Uninstalling PuTTY isn't always silent, as it displays a popup asking if you want to remove the known_hosts entries from the registry before proceeding. For this software, it's preferable to install the WAPT package and then uninstall PuTTY. The WAPT uninstaller handles this detail.

Sincerely,

Denis

Good evening ADT,

ADT wrote: ↑Oct 19, 2018 - 03:56 We are currently testing the product in our park.
We exclusively used the online documentation for the deployment and use of the tool. After two days, we encountered some roadblocks, questions, and needs:

1- I can't find any documentation that details the statuses in the console:

• RUNNING: When enrolling a new agent, the status is OK. Then, I want to push a package to them. After clicking "Start Installations," the remote console displays a popup indicating "1 error." The status consistently changes to RUNNING, with no trace of what is currently being executed in the running tasks

• TO-UPGRADE: I regularly see a package name in my "to-upgrade" list that matches the machine's UUID. What does this correspond to?

WAPT's operating model is agent-centric. The statuses displayed in the console are the last statuses returned by the workstations. In this case, it must have sent the status "RUNNING" when it received the instruction to update. It should have subsequently sent an OK, WARNING, or ERROR status. More details are needed to understand the specific scenario. It might be beneficial for the server to force the status to UNKNOWN if the workstation hasn't returned a status update after a certain period (for example, a laptop that has been disconnected from the network).

ADT wrote: ↑Oct 19, 2018 - 03:56 2- We tested the deployment of a higher version of Adobe (WAPT package created):

• It worked on 1 device

• On another machine of the same type, I get confirmation that the same package installation was successful, but the old one is still present (even after rebooting). This is confirmed by the WAPT software inventory and also directly on the machine: do you think this is a bug?

The package returns an OK status if the Python script executes successfully from start to finish. If a problem is encountered, a `raise` operation can be performed on the package, which will throw an error. In version 1.5, the WAPT agent checks that the uninstallation key is present in the registry; otherwise, it throws an error.

Package creation is a rather empirical science. There's so much diversity in installer behavior that you need a programming language (Python), libraries (setuphelpers, etc.), and an efficient package development environment (PyScripter) to be truly effective. That's what makes WAPT! different and powerful

Sincerely,

Denis

PS: It's best to open a separate topic for each question in the forum; it makes it easier to follow!