Tranquil IT Forum

Hello,

we are using WAPT version 1.8 with an enterprise license.
Our server is Debian Buster (version 10).
The workstation used to create the packages is a Windows 10 machine, version 1903.

We are currently testing the Windows Update functionality. I understand the workstation installation interval, but we would prefer to use a time range to allow deployment, in our case, 00:00 - 05:00.

Do you have a solution?

Another question: Previously, we used a WSUS server for updates. We configured the clients via GPO, specifying that only our server was authorized to deliver updates.

What are your recommendations regarding this configuration? Should we simply disable downloading updates from the internet, or should we authorize the WAPT server?

Thank you for your answers.

Good morning

By default, wapt agents do not install wua updates themselves.

The typical case is that the installation of WUA updates starts when the computer is shut down.

If you do not wish to use this mode, you can run the following command as a scheduled task at 12:00 for example:
The controls:
Also available.


Regarding your current wsus server, waptwua is not compatible with a wsus server; it only works with one or the other, so you must disable the gpo or you risk encountering problems.

In your case, doing it between midnight and 5:00 AM could be problematic if the workstations aren't turned on. Unless you're referring to downloading the updates from the server?

Hello,

commands do indeed seem like a good solution, thank you.

We currently download and install updates between midnight and 5:00 AM to avoid overloading the network and remote sites during the day. The workstations are powered on at 11:00 PM via a BIOS option and shut down via a command line and a scheduled task at 5:00 AM.

For the local network, there are no problems!

For remote sites, you would simply need to set up secondary repositories:

https://www.youtube.com/watch?v=MGe2ItyfxZY

Thank you for this information, I will run some tests.
I'm marking this issue as resolved.