[RESOLVED] Slow Waptagent deployment

[adgm11]

Hello,
when I try to deploy the agent on the workstations, it takes a very long time, more than 10 minutes. The installation goes smoothly in less than a minute, then it gets stuck at the end. When I try to deploy it manually by running the waptagent.exe file, it gets stuck on the "Updating packages when the workstation shuts down" window.

Using the command line
`waptdeploy.exe --hash=blablabla --minversion=1.8.2.7393 --wait=15 --waptsetupurl=https://172.16.11.11/wapt /waptagent.exe`, I get this error message after 10-15 minutes: `

An unhandled exception occurred at $00432E12:
EProcess: Failed to execute c:\wapt\wapt-get.exe --version: 2
$00432E12
$00401F42
$0040538F`.

Any ideas on how to speed up the installation process?
Thanks.

[dcardon]

Hello,

version 1.8.2 is no longer supported by Tranquil IT, and this forum, which is maintained by Tranquil IT, is dedicated to questions about supported versions (or updating to these supported versions).

Unfortunately, no one has come forward to take over maintenance of the 1.8.2 Community version or to run a dedicated forum for this version. If you're interested, you can start one and post a link here to share it.

If you manage to reproduce the bug in version 2.1 or higher, you can open a new ticket; I'm marking this one as resolved.

Sincerely, thank you,

Denis

[adgm11]

Received, thank you.
So, versions higher than 1.8 and 2 are licensed versions? Is it possible to upgrade from a free limited version to, for example, 2.1?

[dcardon]

Hello adgm11,

WAPT 2 comes in two versions: Discovery and Enterprise. The Discovery version is free (but not open source) and includes the features of the Community version, with the only difference being a limit of 300 users.

Regards,

Denis

[adgm11]

Okay. So I just need to install version 2.2 of the console to overwrite version 1.8, and everything else is preserved? The agents will remain up-to-date, and the packages already created will still be usable?

[dcardon]

You need to update the server and the agent (waptsetup.exe) on the admin machine, regenerate the agent (waptagent.exe), and then push it to the entire network. All of this is explained in detail in the documentation.

Regarding the packages, Python is changing from Python 2 to Python 3, but it shouldn't be too complicated to update them if you installed them initially. All packages in the store are WAPT 2 compatible (unless we've missed something).

Sincerely,

Denis

[adgm11]

Okay, I've updated everything. I now have everything on version 2.2.
My problem remains unchanged: it takes at least 10 minutes to deploy an agent because of this step which goes wrong: "Updating packages on system shutdown." It takes a very long time.
How can I fix this? Is this the normal time for this step to complete?
What does "An unhandled exception occurred at $00432E12" mean?
I also get this error: "Unable to speak with waptservice... continue (Is a server available on this address:port? THttpClientSocket.OpenBind(127.0.0.1:8088) [Connect Timeout - #10])."
Thank you.

[dcardon]

Okay, I've updated everything. I now have everything in 2.2.
My problem remains unchanged: it takes at least 10 minutes to deploy an agent because of this step which goes wrong; "updating packages on system shutdown." It takes a very long time.
How can I fix this? Is this the normal time to complete this step?

No, the computer must be faulty... Well, with so little information, it's hard to say. Maybe a bad antivirus program; have you checked that?

Basically, this step creates a local GPO to trigger WaptExit when the machine shuts down. If your machines have configuration issues related to this, I don't know what to do.

What does "An unhandled exception occurred at $00432E12" mean?
I also get this error: "Unable to speak with waptservice... continue (Is a server available on this address:port? THttpClientSocket.OpenBind(127.0.0.1:8088) [Connect Timeout - #10])"?
Thank you.

As the message indicates, it is trying to connect to the local machine on port 8088... Is the wapt service running correctly? What is the output of `wapt-get --version`, `wapt-get update`, `wapt-get upgrade`, etc.?.

Try installing it on a clean machine to begin with.

And thank you for starting a new thread. The previous thread concerned a problem with version 1.8.2. Now we're dealing with version 2.2.

Sincerely,

Denis

[adgm11]

The `wapt-get-version` command gives this:
Win32 Exe wrapper: wapt-get 2.2.1.11899
wapt-get.py: 2.2.1
common.py: 2.2.1
setuphelpers.py: 2.2.1
full-version: 2.2.1.11899

No packages found to upgrade.

When we say a clean machine, are we referring to the WAPT server or the machine running the console? Because the server is a Windows 10 machine, OK. The PC with the console is our WinServ 2016 application server, so that's OK too.
However, we do have an antivirus, it's Trend Micro. Should we offload the Trend Micro client to the server machine?
For GPOs, we're using Scribe, so it doesn't work with gpedit but with another program called ESU. That could explain the bug, but at the same time, it works; it's just very slow to install the waptagent.

[dcardon]

When we say a clean machine, are we talking about the WAPT server or the machine running the console? Because the server is a Windows 10 machine, okay. The PC with the console is our Windows Server 2016 application server, so that's okay too.
However, we do have an antivirus, it's Trend Micro. Should we offload the Trend Micro client to the server machine?

For GPOs, we're using Scribe, so it doesn't work with gpedit but with another program called ESU. That could explain the bug, but at the same time, it works; it's just very slow to install the WaptAgent.

Ah, the Scribe... When I was talking about a clean position, it was more or less this kind of thing I was referring to

Are you using Scribe with a domain in NT4 mode or AD mode?

I can't remember if it was SambaEdu or Scribe, but I've seen local GPOs malfunction in the past due to poor modifications made by SambaEdu/Scribe scripts. The creation of a local GPO is extremely strict on several points (UTF16 with BOM for some files, UTF8 without BOM for others, etc.), and if these rules aren't followed correctly, side effects can occur.

Could you test on a machine that has not been integrated with Scribe (fresh install, not a machine removed from the domain, as it will probably still have traces of the local GPOs created by Scribe), to confirm that this is the problem.

Sincerely,

Denis