Tranquil IT Forum

To put it simply, in terms of functionality I would need a WSUS-type update server, an MDT-type deployment server, and an application deployment server. The management of all three would be centralized via the WAPT console, and each repository would have its own specific functionality.

Hi Vincent,

regarding your number of workstations in a single site, load balancing shouldn't be necessary. We have universities with 11,000 workstations on a single virtual machine... If the VM or the KVM hypervisor can't handle the load, then there's an issue with the sizing of the hypervisor or the VM. Is

the machine experiencing CPU, RAM, or IODisk usage?

Denis

Hello,

The purpose of this post is not to discuss the limitations of my network. We have constraints on our infrastructure that cannot be resolved, or at least not immediately.

One of these constraints is network congestion, which slows down traffic on the rest of the network.

This bottleneck is primarily WAPT, due to very large Windows updates.

In advanced WAPT training, we learned that it was possible to alleviate congestion on the central WAPT server by setting up secondary repositories or peer caching on our machines (this solution is not feasible given our IT policies).

Therefore, the remaining solution is to set up secondary repositories specifically for WAPTWUA.

Could you please advise me on how to achieve this?

Thank you in advance.

Hello,

the configuration you've set up should work:

please refer to my post to verify that it works:

viewtopic.php?p=16852#p16852