TomMat

I wrote this in my first post. It was already done - repository renewed, but some KESs are not able to find current version - the version dated 7th October is newer as dated 14th October. KSC is working, serveral KES clients with WXP or W7 or W8 are automatically updated and up-to-date. Maybe those clients were not active in week begining with 7th and wrong definitions were skipped? But our machine which is checking updates and makes release for KSC is working 24/24 and is updated properly. How can I run in KES (or over KSC) update task in “God-Mode” and force the update? One sample: workstation WKST054, installed databases dated 7th October. Log: Keine Update verfügbar = no new updates Why?

Hi, no way. Mixed manufacturing environment... Maybe it is hard to imagine, but our newest manufacturing machine (bought this year) is using Windows XP as control-unit and has to be integrated with the network. Which is the highest supported version of KSC/KEC for work with XP/2003? Microsoft is for us too fast with product life cycle 😬 But I hope, there is a very simple trick to mark the database as obsolate or corrupt and perform the update. If standrard repair from KES does (set very old database), it should be not to complicated.

Hello, I found the similar topic already but not answered yet. KSC10 (10.1.249) works properly. KES10 (10.2.1.23) is not able to get a newest databases. In two different locations/installations there is the same behavior. Mostly clients are with definition from 7th October. I’ve tried already to reset KES by All tasks->Clear updates repository, now the repository is up-to-date but… The client reporting “database is obsolete” but “cannot” perform the update. Update is working quickly and says “no new updates”. It looks like database clean-up by Kaspersky (reduced qty of definitions)… Is the client checking not a date but the qty of definitions (see screenshot below)? Some of clients are updated properly, but most of them – not. How can I force the update? Only one solution which I found is to reinstall KES or start the repair of KES. But I have in my locations over 100 clients. Is there a simply possibility to mark the local definitions as corrupted and force the update? Best regards, Tomasz