Re: NOD32 2.50.25 program component update released Dear Marco, We have noticed that after the component updates for version 2.50.25 any work stations in our networks not updated to this version will not update to the latest virus signatures and remain that way until a manual update is triggered and the component update prompt is actioned with a 'YES' to the update. Our problem is we have several hundred machines to worry about with NOD32, and we can not go around each one doing a manual update if we can avoid it. Looking from the documentation there is not much I can read on 'Component Updates' and how to go about setting these up correctly via the configurations on large corporate networks. Is there a easier way to perform 'component updates' group wide via the remote admintrator or via config updates so the component update are carried out ASAP and hence, on the next restart the new virus sinatures beging to roll out again to these workstations. Any info. on this appreciated.