Jump to content


  • Content Count

  • Joined

  • Last visited

About khgiese

  • Rank
  1. Attached is a snapshot that is totally confusing me. I am trying to add a workstation to a slave KES system. The server Windows 2003 (32bit) can resolve the ip no issue. The KES 10 admin server can not. I can only assume KES does not update the dns table in a timely fashion. (the machine I am trying to add again is pingable from the command prompt of the server) Here is my confusion, WHY? how do I fix this? I need this software to be more attentative. Thanks, P.S. Please look at the attached screenshot before commenting.
  2. I was able to get my issue resolved. Seems I had phantom machines that had been removed from AD and I thought from KES admin servers. After some additional searching I found the computers still listed under unassigned computers, after removing them from unassigned computers, the unprocessed objects report cleared the machines. Never assume, always verify and re-verify each step, it can save you alot of stress. Thanks to all the people out there that assisted me in resolving this.
  3. I know this is an old thread, but I just recently discovered it. We recently started having this issue. I was able to use the step provided to delete the unporcessed objects from the Admin console. Now I have some very old records in the unprocessed container that do not clear out, these machines have beed removed from service and Kaspersky month ago. Is there a way to make these reports clear the old information?
  4. I would like to see the local task schedules be set to manually, rather then every single deploy being on Monday at 7pm or having to use the outdated format of using the command-line.
  5. Can anyone explain to me why Kaspersky developers saw fit to allow an administrator to turn off tasks from the command line with an INI file but not through the console push of a package? That is TOTALLY unacceptable. Please update your next version to be completely functional from the Console or stop setting the deault values for critical and full scanns. That is why the console was created yes? centralize management? Now for evey machie that we want to install Kaspersky on we need to go back into each and change the tasks on each and every machine since we push out installs and upgrades instead of being forced to use an unacceptable stratagy of using GPO or commandline. GPO give you no control of when or how updates and reboots are to be scheduled. Having a "prompt the user for reboot" on production servers is not an opetion. Batch file push out of command line installs in at the very least incombersome and time consuming.
  6. Agree Mike, we are in the process of developing a plan like we had with KES 8 and MP4 version 6xxxx. We had a bit of a sticky when we deloyed KES 10, but that is a given when you try to implement a program this insightful and overseeing. Our company has a very small IT department which covers everything from printer cartridge replacement to server DR. unfortunately we do not have decidated server admins. This may be a bit of a disadvantage compared to some companies. so somethings take more time to develop. The point I was trying to make was the changes in the default settings from the older version to KES 10 did not work in the favor of our IT department, the caused more issues then leaving the old defaults of setting these tasks manually. While setting defaults is probably a good idea for home users, in my humble opinion it is best leave the settings to the IT profrssionals setting up the systems. this is feed back, not complaining, just expressing my thoughts.
  7. I was mistaken, it is the remote unistall OS timer that seems to run on seconds instead of minutes. Running task remove KES 8 for WS, Remove MP 4 (6.0.1424) all result in the timers seeming to run on seconds instead of minutes. We have duplicated the issue several times.
  8. After some testing it appears the OS reboot timer isn a push delpoy of KES 10 (10.0.3361) from KSC10 is set for seconds, not minutes. I post here as my past experience with tech support is less then satisfing. However my experience with finding answers from other administrators has been very helpful. Thanks,
  9. Another "new" feature in KES 10 is the timer for prompting the user. If you leave the default settings under OS reboot, which are prompt every 5 minutes and force reboot after 30 minutes, this don't work. What is happening here is the user gets the prompt every 2 seconds and after postponing the update 5 times, the PC reboots on its own. If I uncheck the force reboot after 30 minutes, the user is prompted every 2 seconds but no reboot is forced, which is VERY VERY ANNOYING. I am trying to change the default settings to a larger time interval for prompting and eliminating the force reboot. Defualt are good, but NOT if they cause control issues and annoy the heck out of end users. if you have a selection box that states "every 5 minutes" it should take 5 minutes, not 2 seconds. Thanks
  10. Please either set the default settings for full scan to manually. Setting every machine to default to Monday night 7pm is just not well thought out. We have several VMWare server farms that hold 100s of VM servers. Now imagine the server all hitting the update servers are the exact same time every Monday night. When you have 400+ servers running full scans, the CPU cluster core goes nuts. When the CPU cluster core goes over the defined limits it sets off alarms. When alarms are tripped, sms messages are sent out. When sms Messages are sent out, I get calls about the "emergency". When I get calls about the "emergancy"........ well I am sure most of you know the rest but here is the wrap up. When alarms go off and sms messages are sent out, I have to answer so poinent questions. "Why did the alarms go off?" "Why was the Cluster core CPU spiked?" "Why are all the Full scans running on Monday night at 7pm on ALL the servers" I think you see where this is going...... The biggest stinker to this all is we now have to go through 200+ servers and manually set the full scan task to Manually, not the best plan, but I don't have 32 CPU cluster core lighting up all red and flashy. While now I know about the setup.ini file and how to use it properly, this information is not up front and forthwith, you have to dig it out, you have to basically get a degree in Kaspersky. Thank you for letting me vent. I hope some developer sees this and with some grain of compassion understands the IT plight of this setting.
  11. Since Switching to KES 10 we can no longer set a task that allows the user to run a manual update from their machine. I set up a Task same as I did in KES 8 but it will not allow the user to run the update from inside their client. HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
  12. I am in the process of updating servers in my company. I can not find anything on installing KES10 on a windows 2003 Terminal Service server. The install fails but does not say why. Just says failed unexpectedly. If I try to install locally, I get the same error. IS KES 10 compatiable with server 2003 sp2 in terminal service mode? IF so, what are the steps to install? IF not, is kes8 the latest version to work with Terminal service mode? Thanks
  13. Uninstalling KES 8 then rebooting, then deploy KES 10 still activates the ICW. So your "Work Around" is bogus and invalid. When is the patch going to be released? Thanks,
  14. We have this problem as well, how do you push out an install using the switches mentioned in this thread?
  15. Networking in XP Mode appears to be working today. Not sure what changed, maybe the policy took longer to apply then it showed in Admin Kit. Again not sure as not other chagnes were made, today KES 10 is not blocking the XP Mode network.
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.