Jump to content

technikarc

Members
  • Content Count

    99
  • Joined

  • Last visited

Everything posted by technikarc

  1. I tried one more time and it worked. I just had to wait more than half an our - about 40 min for connection to be made. And about 30 min till setup completed. Looks like it was just a delay.
  2. I can't even find the "Windows update synchronization" task. Nor in Tasks section, nor in "Create new task" list. How can I create it?
  3. OK. My question was which policy template to use for my KEA v10.2.6.3733? Kaspersky Endpoint Security 10 Service Pack 1 Maintenance Realease 2 for Windows or Kaspersky Endpoint Security 10 Service Pack 2 for Windows ? I can't update those Workstations to the latest KEA version now - they are running Windows XP.
  4. I have never performed 'Perform Windows update synchronization" task on any Workstations. But this error occurs only on some of them.
  5. I have KEA v11.0.0.6499 and KEA v10.2.6.3733 (for Windows XP only). And I can create Policies for: Kaspersky Endpoint Security 10 Service Pack 1 Maintenance Realease 2 for Windows Kaspersky Endpoint Security 10 Service Pack 2 for Windows Kaspersky Endpoint Security for Windows (11.0.0) How can I know wich digital version represent alphabetical version?
  6. Well the main question was is my products version is related to the Application category propagation mode setting and could cause this behavior. If it's not, I will try to set Transmission of modified data only (for Network Agents Service Pack 2 and later) on Monday again. Hope it will not paralyze my firm one more time
  7. Understood. Will let you know if problem reappears. I can check it only with the next updates of Kaspersky products though.
  8. Server is on Provider1 behind the router in local network. Client is on Provider2 behind the Wi-Fi router. Server can see Client status through NA, it's online (NA is configured to do so) but when I create a task on KSC to install KEA 11 the task hangs and says that it's waiting for connection.
  9. It was converted policy after updating KEA from v10 to v11 and KSC to latest version. Can't remember the original version of KSC. It is about half an year I last launched inventorization Task and ASC worked perfectly. As I create whitelisted directories in ASC I don't see purpose of this task. The thing is those workstations didn't saw these whitelisted directories (in picture they are though): I had to reinstall KEA because couldn't even login into Windows account. I'm guessing it was because I chose Transmission of modified data only (for Network Agents Service Pack 2 and later) lately. Now I came back to Full data transmission (for Network Agents Service Pack 2 and earlier). Could it be a problem?
  10. It was converted policy after updating KEA from v10 to v11 and KSC to latest version. Can't remember the original version of KSC.
  11. There are no results. Te Task hangs in progress saying "Waiting for connection".
  12. Can I remotely install Kaspersky Endpoint Security (KES) throug KSC (Kaspersky Security Center) if Workstation is in another network? Network Agent (NA) is running and reporting status that Workstation is online. But when I create install Task, it displays "Waiting for connection". It's about half an hour now. My product version are in my signature. Thank you.
  13. No, after enabling Transmission of modified data only I didn't performed inventorization task. Question 1: will problem be solved if I run Inventorization task after enabling Transmission of modified data only? Yes, I see executable files listed in KSC Advanced > Application management > Applications registry section. They are appearing briefly. Last ones are from yesterday. Although Inventorization task is set to run manually and has not been run recently. Question 2: if Inventorization task is set to run manually, why applications are still appearing in Applications registry section? Policies are attached. Kaspersky Endpoint Security for new KES (Managed devices).klp Kaspersky Security Center 10 Network Agent.klp
  14. Attached. Kaspersky Endpoint Security 11.0.0 for Windows (Managed devices).klp
  15. As I've mentioned a few posts above, I have ASC set in whitelist mode. None of Windows temporary folders are in this list so users can't launch any executables from there. Although NA managed to be installed on most of these Workstations.
  16. Right to launch any executable files from Windows temporary directories are strictly denied. Why NA was able to install itself on other Workstations?
  17. In my Administration Server Properties is a section Application categories. Inside Application category propagation mode has two options: Full data transmission (for Network Agents Service Pack 2 and earlier) and Transmission of modified data only (for Network Agents Service Pack 2 and later). My current versions of NA is in my signature, currently it's the latest. How can I know is my NA Service Pack 2 or not? Because problem is when I choose Transmission of modified data only (for Network Agents Service Pack 2 and later) on some Workstations list of whitelisted directories became empty in Application Startup Control (ASC) and started to prevent launch almost any executables.
  18. Your comment helped me to resolve this problem. Our Kaspersky Endpoint Antivirus (KEA) is using Application Startup Control (ASC) and on these particular Workstations I had to disable it to install Network Agent (NA). In Policy I have these paths whitelisted where any executable can be started: C:\_Extra\* C:\Program Files (x86)\* C:\Program Files\* C:\Soft\* C:\Windows\* C:\Users\Admin\* C:\Users\Administrator\* D:\Users\Admin\* D:\Users\Administrator\* C:\Documents and Settings\Administrator\* So this means installing NA temporary executable files are put somewhere else and can't be launched. Could you please provide more information about NA executables behavior when installing? Thank you.
  19. I tried to install Network Agent remotely once more, got the same error, generated GSI report immediately. It's here.
  20. Well looks like it's inside Kaspersky Security Center 10 for Windows (Full package). Very easy to find not counting the weight of the package (almost 1 GB). Extracted it from there, created a package in KSC using nagent10.kud. Got the same error. What else can be done to resolve this?
  21. Still some Workstations can't install this update. If the above scenario is the case, then how corrupted package managed to install on all other Workstations. Anyway - I deleted Kaspersky NA from KSC's Installation Packages. I can't find where to re-download it. Where can I find it?
×
×
  • 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.