Hi everyone, I was wondering how the content auto-update delay feature works when a CU borks a system. Last week we experienced a sudden spike in cpu and ram usage, and the affected machines crawled and stuttered, impacting production. Support told us to wait for a specific content update to be released, which would (as had been appened) correct the problem. So, in a scenario like this: Agent profile grp_CriticalServers : cu delay: 3 days. Agent profile grp_Workstations: cu delay: none day 0: CU 500-00001 released, applied on grp_Workstations , grp_CriticalServers still on CU 500-00000 day 1: CU 500-00001 works as expected day 2: CU 500-00002 wreak havoc on grp_Workstations, grp_CriticalServer still on 500-0000 day 3: CU 500-00003 and CU 500-00004 released , grp_Workstations now working normally. Question: at day 3, which content update will be served to the grp_CriticalServers? The last available 00004 ? 00001 and then after another 3 days, all the critical servers will be affected by the problematic CU 00002? In the first case, going straight to the last available come with some risks, the latter is not acceptable if there is no way to deprecate a CU. Or there is? The end goal is to use the vast majority of machines as canary for the critical servers. How did you manage a situation like that? Regards
... View more