I would recommend to concat official ESET support, as they will known what logs are required - especially in case this affects only specific systems. This specific error means that there is either no package for your operating system, something is not properly configured. Is XP somewhat supported in EE 7 or is it better to leave/downgrade these clients at 6.6?Ĭould you please try to manually upgrade to AGENT v7 on one of those systems to verify it will be successful? Could you verify that AUTOS ELECT repository is used in problematic AGENTs configuration. 1, but upgrade to the latest version seems to fail both via ESMC and ESMC integrated installer packages. Moving to the latest ESET Endpoint: while ESMC reports XP clients with Endpoint 6.6 as current, some were manually installed with. I always update the Agent before the AV: can I try upgrading the AV before the Agent? What do I do to avoid the error? These servers are marked as Outdated in ESMC, and another 2003 server updated successfully both AV and Agent, so I suppose they should upgrade too. I could not find an error code (maybe I didn't see the correct page in ESMC: if it's there, please point me to it). Which should approximately translate to 'Could not execute planned task: referred archive packet not available'. 'Impossibile eseguire attività: Il pacchetto dell’archivio con riferimento non è disponibile' I'm getting some strange errors when trying to install the latest Agent on some Server 2003 machines via ESMC: In the meantime, it is paramount that old equipment is protected as well as possible, and this brings me to the following questions. Changes are being done, but both management and staff are pulling hard on the handbrake. I'm sorry to resurrect very old OSes, but my production environment is crawling to Windows 10 at an appalling speed.

Eset endpoint windows xp