Jump to content


  • Content Count

  • Joined

  • Last visited

About hayleyit

  • Rank
  1. That got me on the right track, thank you. Looks like I need to update all of my client NetAgent installs to use the new KSC server hostname. I have tried re-installing NetAgent via KSC to some of the computers, but it seems like a re-install doesn't actually change the target/admin server's hostname. Does this sound right? It's a bit disappointing as I didn't want to have to run klmover.exe on my entire estate. Regards, EJ
  2. Hi, We have 650+ devices managed by our KSC server. 100+ of which are portable devices (i.e.: laptops), which are on public networks most of the time. I want KSC to be able to see and manage them 24/7. We have a public DNS entry, ksc.domain.com (for instance), which internally resolves to our KSC server's internal IP, and externally resolves to our firewall's public IP address. I have created rules on our perimeter firewall to allow Kaspersky services in and forward them to our internal KSC server. Our NetAgent policies use the same ksc.domain.com hostname for the administration server connection profile. In theory, this should all work fine? Problem is, it doesn't. I don't see any connections hitting our firewall. Not sure if this is the source of the problem, but if I run klnagchk.exe, it tries to ping my KSC server's internal primary hostname: " Attempt to connect to the Administration Server...Transport level error while co nnecting to http://svr-h002640.domain.local:13000: failed to resolve address. An attempt to send ICMP packet to the Administration Server Unknown device svr-h002640.domain.local " I can't see svr-h002640.domain.local anywhere in any of our KSC profiles, so why is the Agent trying to ping it? How can I get it to run this test against ksc.domain.com instead? Thank you in advance for any advice. EJ
  3. Hello, I have just upgraded our KSC to v10.4.343. Now, it's been a while since I worked with KSC, so I'm a little rusty. I am trying to clean it up, by removing old, unused or obsolete tasks, but I am having problems with a specific one. Here are it's details: Task type: Install application remotely Application: Kaspersky Security Center 10 Administration Server Group: Tasks for specific devices Schedule: Manually It's not currently, running, and I have removed any computers from its targets list; but despite this, every time I try to delete it, it fails with "Fail to delete the task "Deploy KES 10 SP1 MR2 for Windows ("." I have triple checked it's not running, and even rebooted the entire server, but it will no go. How can I delete it please? Thank you. EJ
  4. Fantastic! All of the lock icons were unlocked! Changed them to lockd and let it reapply and they are all now picking up everything correctly. Thank you so much!
  5. We are currently running KSC 10.3.407 and clients are using the same version of NetAgent and KES 10 SP1 MR2. I don't know how long this has been happening but many of the policy settings are not being applied correctly. One good example of this is that we password protect the interface but users are now able to shut it down without a password. KSC is reporting that the clients are connecting correctly and if I run a connectivity test from the client, it can see the server just fine. How can I find out why they are ignoring policies? And it there a simple was to force the policy to push out again? Thanks in advance.
  6. KSC v10.1.249c Hi, I have set an additional update folder ('Repositories'...right-click 'Updates', choose 'Configure Updating Settings', 'Settings', then 'Configure' 'Other settings'), but how do I tell certain Net Agents to use this update folder instead of the primary one? Thanks in advance. Elliot
  7. Hi, this isn't an option as our users love turning their PCs off, and doubtlessly it'll be the user's machine running the update agent. The update folders I am trying to configure are on site NAS devices which are locked away so this is ideal.
  8. We have a lot of remote sites with multiple users so I want to configure KSC (at HQ) to update at night, then copy the updates to each site's local store. Each client (at each site) can then pull updates from the local store, as opposed to pulling across the slower WAN. This task has been scheduled to run each night (one update per night, which SHOULD then copy all updates to each site's local store). Following each night's update, KSC has failed to copy so much as a single file to any of the stores since I cleared them the other day to start clean. From what I can see, this function seems to be massively buggy and unreliable or there is something not obvious which I also need to configure.
  9. No one has any experience or advice with this?
  10. Hi all, We recently installed KSC10 and have decided to use the "Deploy downloaded updates to additional folders" feature within the "Download Updates" task for the Administration Server. I have added about eight additional folders for updates to be deployed to but when the update runs it seems to only copy the updates to the first folder in the list. Not any others. I have tried rebooting the whole server but it persists in behaving this way. Am I missing something? Thanks in advance. Elliot
  11. I just realised the log wasnt attached kl_install_2012_07_12_11_01_28.7z
  12. I managed to get the logging to work. I had to uninstalled Net Agent, run Kaspersky removal tools and reg cleaner. Also had to run CCleaner and regrepair then manually remove any temp files. After a reboot the logging worked. So, now I have reinstalled Net Agent and tried to deploy KES through the KSC and also manually in the PC. It still fails and generated the attached log. Please help!
  13. Hi, I've tried to got hold of the install logs as requested but looks like logging isn't running. I have tried to enable the logs using this guide msi_log.zip but still nothing. I don't know where to turn with this. Is there a list of known products that cause issues with Kaspersky? If not I think it would be useful for Kaspersky to collate and publish the information for troubleshooting purposes.
  • 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.