Help - Search - Members
Full Version: Kaspersky workstations default to running updater manually.
Kaspersky Lab Forum > English User Forum > Protection for Small and Medium Businesses
Dave Mack
On one of my clients' networks (a SBS 2003 server and XP Pro workstations), I uninstalled and reinstalled Kaspersky on all of the workstations following the update last week that caused the Kaspersky client to repeatedly crash on Windows startup. After reinstalling, I couldn't get any of the workstations to update at all. I figured out that when deploying the KAV client, I need to tell it to deploy the updater too or else they won't update. (I got the cryptic "update is controlled by your administrator" error message, rather than it just coming out and telling me that the updater component was not installed at the worktation level.)

The problem is that all of the workstations, by default, were set to update manually. This is despite me doing the following in the Kaspersky Administration Kit:

--Going to Updates -> Configure Updating Settings -> setting the schedule to "every 15 minutes" (excessive, I know, but I didn't want to wait too long to find out if it worked or not)

--Going to Global Tasks -> Download updates task -> setting schedule to "every 15 minutes"

--Going to Groups -> Group Tasks -> Antivirus Update -> setting schedule to "every 30 minutes"

I checked under Groups -> Policies -> Kaspersky Antivirus for Windows Workstations v6 -> Update and did not see any options relating to the update schedule, only the update source.

I eventually had to log into each workstation via RDP and manually set them to update "automatically" instead of "manually".

The workstations all have Kaspersky Network Agent installed on them. I tried uninstalling KNA and KAV from all of the workstations and reinstalling those components, but the KAV workstations still defaulted to update manually. All of the workstations are visible in the KAK and appear to be checking in with it regularly. So why, oh why, did I have to manually set each workstation to update manually?
Helmut
You can deploy the package with predefind settings.
Read this FAQ.
Dave Mack
QUOTE(Helmut @ 4.09.2008 01:29) *
You can deploy the package with predefind settings.
Read this FAQ.


Hi Helmut,

Thanks for the link. It looks like the FAQ simply says to copy the install.cfg file into the Packages folder where the KAV workstation installables are located. (The FAQ mentioned a key file as well, but I assume that's for the license key, and if the key is already configured on the KAK, then there shouldn't be any need to do anything with it in the Packages folder, right?) Well, I created the install.cfg file on one of the workstations after making sure it was set with the workstations options I wanted (specifically, Updates set to be applied automatically, not "every x hours" or manually). After doing a test push install using KAK to one of the workstations, the update schedule remained set to manual.

So either I'm doing something wrong or the steps in the FAQ don't work. (Hey, it's probably the former, but who knows.)

This doesn't make sense. Surely Kaspersky Labs doesn't require the network administrator to reinstall the application any time the update schedule needs to be changed. Any why would the default be set to update manually, essentially guaranteeing that the workstations WON'T get updates?

dash1.gif
namh
You can force the client kav setting, same as what you create in policy setting.. open policy properties, go to enforcement tab, click on advanced link on the bottom, choose to modify, and click change now and OK.. you will see user setting same as what you set in policy..
Dave Mack
QUOTE(namh @ 5.09.2008 02:15) *
You can force the client kav setting, same as what you create in policy setting.. open policy properties, go to enforcement tab, click on advanced link on the bottom, choose to modify, and click change now and OK.. you will see user setting same as what you set in policy..


I just checked that and it was set to "do not modify local settings". I changed it to "modify all policy settings to the local settings at first policy application". Hopefully that helps. Thanks for the suggestion, namh. I'm waiting to see if it takes effect on the workstations and forces them to update.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.