How are the updates distributed on a network?

How are the updates distributed on a network?

We support a particular setting, ensuring that updates are distributed over a specific time interval. The default is a 7.5-hour window, during which all agents will conduct scheduled inspections also will run the “approved” update tasks. This window can be slightly expanded but ensures the evenest distribution should be aligned with the most common work hours. 

Actual inspections are randomly distributed over an interval of up to 10 hours, starting at the selected time.
Applicable updates will run shortly after an inspection is completed.

    • Related Articles

    • Does VulnDetect support a peer 2 peer mechanism for the distribution of updates?

      VulnDetect uses BITS (Background Intelligent Transfer Service) from Microsoft and allows system administrators to download packages/updates with little impact on the network traffic and bandwidth. If you want to know more about BITS please visit: ...

    • What is the difference between Windows Updates and Windows Updates Approvals?

      The Windows Updates page only shows the updates that are available and not yet applied. The Windows Update Approvals page show some of the recently applied updates, but those covered in cumulative updates or other major updates of the OS seems to be ...

    • How does SecTeer VulnDetect fetch Windows Updates?

      The Windows Update feature pulls available updates via the currently configured Windows Update service, this means that it will query your WSUS if this is configured. If WSUS isn‘t updated with the most recent updates, these will not be visible in ...

    • Why can't I automate the approval of Windows Updates?

      Windows Update Approvals cannot be automated because Windows updates are not versioned, so a Windows Update Approval is never Out-of-Date. Setting a Windows Update Approval to approve updates is sufficient to make the system apply that Windows Update ...

    • Updates seems to hang (Applying) for a long time, why?

      The most common reason is that the host is offline or hibernates. Other times, the package may be waiting for the Windows Installer database, it will wait for up to two hours, before abandoning the update. The update will not be retried until the ...