Tranquil IT Forum

Hello,

I'm writing to ask a few questions.

I'm currently using WAPT Server Community version 1.5.26, and I've just seen this WAPT 1.6 RC2 update. I'd like to know if I can also use it in open-source mode.

Is this version stable so I can use it on my network?


Thank you in advance.

Hello maintenancevla,

maintenancevla wrote: ↑21 Sep 2018 - 09:26 I am writing this email to get some information.

I am currently using the wapt server community version 1.5.26 and I have just seen this wapt 1.6 RC2 update and I would like to know if I can also use it in open source mode.

WAPT Community version 1.6 is licensed under GPLv3, as are WAPT Community version 1.5 and earlier versions.

Is WAPT Enterprise version 1.6 subject to a commercial license (like WAPT Enterprise version 1.5).

maintenancevla wrote: ↑Sep 21, 2018 - 09:26 Is this version stable? So that I can use it in my fleet

We have been using WAPT Enterprise version 1.6 with our partners for several months now. The nightly community builds and the GitHub repository are updated regularly. WAPT Community version 1.6 is based on the same codebase as WAPT Enterprise version 1.6.

The RC2 version will be officially released this afternoon, barring any last-minute issues. We consider this version stable.

But nothing prevents you from having a borderline situation on your network that isn't covered and that we haven't encountered with our clients. That's the charm of system administration; every network, every Windows machine has its own personality, its own esoteric characteristics, and its own quirks. Otherwise, it would be too simple, it wouldn't be interesting

Sincerely,

Denis (Tranqui IT)

Version 1.6.2.5 rc3 is now online, fixing a minor issue (the waptservice_timeout of wapt-get.ini was not being used by the command `wapt-get --service upgrade`).
The default timeout for wapt-get and waptexit has been increased to 4 seconds from 2 seconds.

https://wapt.tranquil.it/wapt/releases/ ... 6.2.5-rc3/

Okay, thank you both.

Off to production then, so thanks again.