Jump to content

Different Update Trigger Behaviour Between GUI and Schheduler Task

Go to solution Solved by Marcos,

Recommended Posts

Hi All,

I see that the uPCU update starts only when update is triggered via egui. the update that triggered via task scheduler, esmc update task, ermm do not start uPCU update, just signature update. All update methods pointing same update profile. Is this a known behaviour? How can I solve it?


Link to comment
Share on other sites

  • Administrators
  • Solution

That's because of the activated spread control on repositories which limits uPCU to clients with certain probability. Manual update enforces also program updates.

Once the spread control is turned off, any update attempt will download and offer a program upgrade via uPCU.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...