Tranquil IT Forum

Hello,

we use WAPT Discovery, and I would like to deploy an application on a specific date.

I navigate to the private repository and edit my package.
To do this, I set a start date of May 24, 2023, at 7:00 AM, with an end date and forced installation on May 27, 2023, at 12:00 AM.

To test, I go to the inventory and modify the test machine.
I then add the modified package.

However, it installs immediately, ignoring the start date.

I've searched extensively in the documentation and the forum, but I haven't found a guide for programming packages.

Could you help me understand what I'm doing wrong?

Wouldn't you happen to have another package that doesn't have an expiry date in the older version of the package?

So I edited the packages in the Pyscrypt editor and removed the expiration dates.

What should I do next?

I really don't understand this application.
I simply entered the start date, and the programs didn't install immediately.
I had scheduled them for 5 AM the next day.
This morning, after 7 AM, I don't see any logs on the target machine. I log in, but there's still no installation.
In the console, I see a GUID that still says "NEED TO INSTALL," but I don't understand what it means.
A short tutorial would be very helpful, I think.

What format did you use for the date?

I can't remember if it should be UTC or not.

I used the graphical interface (see attached image) )

Actually, you need to specify a start date and an end date. I thought the end date would uninstall the software on a given date.

I'm sorry to say, but your documentation is really unclear.

Hello

, I looked into this to see what was wrong. I was able to identify an issue in my tests.

There is indeed a small problem, but it's not related to `valid_until`; it's more subtle, which is why the tests are random.

When you use `valid_from`, if the date hasn't been reached, the package is hidden, and WAPT schedules an update at the specified time.

The problem is that the WAPT agent will indeed perform an update, but if the server's Packages file hasn't changed since the last update (because you haven't done anything else on the server), then it won't realize it needs to download it again to perform the diff and therefore see the package.
However, if you trigger an update through the console in this case, then it works because you're forcing the update.

Here, we rarely use `valid_from`, but rather `forced_install_on` directly, bypassing `valid_from` and `valid_until`. This forces the installation of a pending package on a given date.

If you had a subscription and support with us, I would have suggested calling to avoid further troubleshooting on your end, but since you're in the discovery phase...

Thank you for taking the time to reply.

However, you wrote:

Here we rarely use `valid_from`, but directly `forced_install_on` without `valid_from` and `valid_until`. This way we force the installation of a pending package on a given date.

But in the console in Discovery mode in French I have Force the installation before which I think is different from the translation forced_install_onThis feature installs the program before a given date, but not from a given date.
Is it different in Enterprise mode?

For your information, we were forced to abandon WAPT because of another mandatory solution. This one really doesn't suit us, and so we have to "prove" that WAPT is more efficient.

yann83 wrote: ↑June 5, 2023 - 1:28 PM But in the console in Discovery mode in French, I have " Force installation before," which I think is different from the translation "forced_install_on."

No, it's exactly the same thing, but it's true, the message isn't good...

It should be something like: "Force installation of the pending package starting from this date". Or something like that.

I'll look into changing