Tranquil IT Forum

Hello,
I'm using version 1.8.
I'm testing WAPT.
I assigned the tis-vlc package to a Windows 8.1 client. Everything is fine; VLC is installed on the client.
The same goes for tes-mremoteng.
To uninstall the VLC package, I right-clicked on tis-vlc in the console and selected "Uninstall package." Then I ran the installation to be sure.
Still in the console, in the message window, I see:
{"msg":"1 actions launched, 0 errors, 0 skipped, 0 server errors","success":true,"request_time":null,"result":[]}

But neither package is uninstalled from my client!

I even ran `waptexit` on the client, but nothing happens.

Is this the correct method for uninstalling software?

Thank you.

This is the expected result...
When you requested uninstallation via right-click, the action started immediately (normally...).
Then, by clicking "Run installers," the packages must have been reinstalled because they are still associated (as dependencies) from the first action.

To truly uninstall, you must first double-click on the machine and remove the dependency. This indicates that it is not "required" to have this software on the machine.
Then you can force uninstallation by right-clicking in the list of installed packages.

I double-clicked on the machine, and in the "Packages required on the machine" tab, only tes-waptupgrade remained.
I then connected to the client (RDP).
And on the web page 127.0.0.1:8088, I see that the .cert files are old. The new .cert file isn't on this client!
Could the problem be related to this?

Yes, the agent must have the new certificate, so you need to reinstall the new agent (the one containing the new certificate).

The WaptUpgrade cannot be installed if it is signed with the new certificate.

Actually, I had to uninstall (via GPO) the old agent on all clients, which was therefore signed with the old certificate.
Then I deployed (via GPO) the new agent, which is now signed with the new certificate.
But on the clients, I have tis-xxx packages that won't delete via the console, even though I correctly signed all the packages with the new certificate on the server (CentOS 7.5).

In short, does changing the certificate pose problems that are difficult to resolve?

Thank you.

mouka wrote: ↑Jan 30, 2020 - 7:28 PM In summary, changing certificates poses problems that are not easy to solve?

Yes, exactly, all of Wapt's security revolves around the certificate

Key takeaways:

You must not change your certificate
You must not change the prefix

Thanks for the information.
I requested trial licenses to test Windows Update. I haven't received a response from Tranquill IT yet. I expect it soon.

Hello,

our sales department was quite busy with the FIC last week! Are you still waiting for your trial licenses?

I received the license.
But there are some really blocking problems.
I have a client who already has AbiWord installed, so I added tis-abiWord to their system for testing purposes. The result is disastrous:
On the console, I have two errors highlighted in red: one for the tes-abiword package, and one for the package with my client's name. Additionally, there are two blue NEED-INSTALL crosses on the same packages as above.

Even worse: the restart gets stuck on 'Updating. Do not shut down your computer'

Isn't all this discouraging?

Hello,

The fact that there are two errors is "normal".
The machine package is showing an error because a dependency package is also showing an error.

You can learn more about the error preventing the AbiWord installation by clicking on the package name.

Upon restarting, do you get any further information about the status of the WaptExit (installation pending, for example)?

Regards