Tranquil IT Forum

Good morning

I'm posting this because I think I either don't understand the purpose of this package or there's a problem when shutting down client workstations (homogeneous fleet under Windows 10)

In fact, when the client workstation is shut down, I can see wapt trying to install software updates, but nothing happens.

Here is the package group placed on each machine by wapt Is there a conflict or problem with the PC's installation and shutdown time?

The nowaptexit package removes the local GPO that is set up by default to launch waptexit.exe when the computer shuts down.

If this package is correctly installed, packages should no longer update when the computer shuts down.
You will then need to install waptexit or perform an upgrade by another method.

htouvet wrote: ↑March 29, 2018 - 4:18 PM The nowaptexit package removes the local GPO that is set up by default to launch waptexit.exe when the computer shuts down.

If this package is correctly installed, the packages should no longer update when the computer shuts down.
You then need to install waptexit or perform an upgrade by another method...

Okay, thanks for the info

So either I manually push waptexit.exe via the wapt console or via domain GPO when the workstations are shut down, is that correct?

Good evening MaintenanceVLA,

maintenancevla wrote: ↑March 30, 2018 - 08:40

htouvet wrote: ↑March 29, 2018 - 4:18 PM The nowaptexit package removes the local GPO that is set up by default to launch waptexit.exe when the computer shuts down.

If this package is correctly installed, the packages should no longer update when the computer shuts down.
You then need to install waptexit or perform an upgrade by another method...

Okay, thanks for the info

So either I manually push waptexit.exe via the wapt console or via domain GPO when the workstations are shut down, is that correct?

As Hubert mentioned, the tis-nowaptexit package removes the local GPO that runs WAPTExit when the machine shuts down, and configures the InnoSetup environment to take this choice into account during the next update [1].

The local GPO is created when the WAPT agent is installed (unless you modified the `--tasks` parameter during installation). The GPO may not function if the local GPO environment is corrupted. This is often seen on networks using SambaEdu.

Creating a domain GPO to launch WAPTExit might work, but it shouldn't normally be necessary. You could reinstall the WAPT agent explicitly specifying all the tasks, or you could use the tis-nowaptexit package as a guide to create the tis-enable-waptexit package...

Happy Easter weekend!

Denis

[1] https://store.wapt.fr/package_details?p ... 2_all.wapt

Hello again

Sorry for my late reply, but I've been very busy at the moment

I don't understand this:

You can optionally reinstall the WAPT agent by explicitly specifying all the tasks,

What tasks are you referring to?