Jump to content

Axel2016

Members
  • Content Count

    27
  • Joined

  • Last visited

About Axel2016

  • Rank
    Candidate

Recent Profile Visitors

445 profile views
  1. Answering Dmitry Parshutin's comment which seems not to be available anymore: "Hello! So, this problem reproduces only when you trying to set an exclusion for the exact user? Is this behavior applicable for different accounts? Thank you! " We have tested 3 different users on 3 different workstations, they all show the same behaviour: same KES version on the three clients, they all work fine when the exclusion is set for "everyone" (which is not an ideal condition for us) but they keep prompting the error message when the exclusion is set for a single user.
  2. Updated KSC to 11.0.0.1131. Updated Network Agent to 11.0.0.1131. KES version currently installed on the client: 11.0.0.6499. When adding the exclusion for a single user I am still having the same issue. Just for the record, I tried to add the exclusion for "everyone" instead, and it worked perfectly, although I need to unlock the device for a single user only.
  3. Good morning. We've used the Device Control feature for a couple of years now, blocking USB devices and Card readers, and everything worked fine until we upgraded KES to version 11 on two workstations. The access and block to the devices are still working properly, but when an exclusion is added, KES keeps prompting the message that the device is blocked, even if we can explore its folders, and when we unplug the device KES prompts the message for hours. We have clients running KES 10 SP2 with different releases and they all work fine (we obviously have a criteria for each version). KSC version is 10.4.343. Is there any fix?
  4. Hi Ivan, thanks for your support. Could you tell me where to find it on the KSC? Thanks in advance.
  5. Good morning. I enabled the Device Access control on my KSC as we've blocked USB devices on most of the clients. I've been looking on the Security Center where to find the list of all the attempts to access a blocked device (assuming it's displayed somewhere) but I just can't find it. Also I would like to know if there is a report where I can read all the Device Access Requests sent by the users when they try to access a blocked device, so that it would be easier for me to add an exception for the trusted removable devices. I've seen your guide about a temporary permission but that's not what I am looking for. Thank you in advance.
  6. Good morning Nikolay, and thanks for the help. Here's the number of the request: INC000008303070
  7. Good morning. Ever since we upgraded KSC to 10.4.343 and KES to SP2 we've had this problem on several clients. The USB and CD-DVD block is enabled but the CD-DVD message is displayed randomly even if the user is not trying to access any device. I've seen a similar topic where Bug 2175144 was mentioned and I was wondering if there is a fix or a workaround that does not include disabling notifications. Thank you.
  8. Hi Kirill, thanks for the reply. Is the Network Agent update mandatory after the installation of the new KSC? Also, is there a link or documentation with the existing Kaspersky products showing which are the compatibilities and what is the date of the end of support for each version? Thanks again.
  9. Good morning, I am planning to upgrade a KSC version 10.2.434 to 10.4.343. The clients in our network have Network agent 10.2.434 installed and most of them have KES 10.2.4.674. We also have a few computers with KES 10.1.0.867 which we are going to update in the future. I've read this guide but I am wondering if the Network Agent update is required as well. Also, if I install the new version of Network Agent on my clients, will KES 10.1.0.867 and its policies still work properly? This is my first time updating a KSC so I am open to suggestions. Thanks in advance.
  10. Good morning, shortly we will create a new domain and we will move all our clients on it. We are not going to migrate the domain (dirty AD), we will create a parallel domain and migrate the clients with a tool. At the moment, the clients are connected to the KSC using FQDN. Since the KSC is on a server with static IP, is it enough to change the connection between agent and KSC and make it via IP using the Klmover? Will that work even after joining the new domain? Thanks in advance for your support.
  11. il client puntano come FQDN. Però forse mi sono espresso male. Il dominio non verrà fisicamente migrato (struttura AD troppo sporca) varrà fatto un domino parallelo e migrati i client con un tool. La domanda era più che altro, prima di migrare il client (o dopo) basta eventualmente disinstallare il connettore + network agent e lasciare l'antivirus installato per poi dal nuovo Security center fare il provisioning sulla classe di rete? o bisogna fare altre operazioni per non incappare in client "orfani" che poi non si aggancino al nuovo security center? Grazie.
  12. Buongiorno, a breve dovrò migrare un'intera struttura di dominio sotto nuovo dominio. Sul "vecchio dominio" al momento è presente un Security Center a cui sono agganciati tutti i client. Vorrei sapere se è possibile migrare il KSC sul nuovo dominio, ammesso che convenga procedere per questa strada. Nel caso invece convenisse invece installare un nuovo Kaspersky Security Center, sarebbe sufficiente agganciarvi i vari client utilizzando il network agent? Grazie.
  13. Ciao Shazer, grazie per la risposta. Purtroppo non posso inviare uno screenshot in quanto il problema, se così possiamo definirlo, si è presentato sui computer di alcuni miei clienti. Io mi occupo, tra le varie cose, dell'aggiornamento degli antivirus, la mia domanda era più che altro per gestirmi con gli aggiornamenti nel caso ci fossero sostanziali differenze nel caso sopra riportato. Capisco tuttavia che rispondermi senza uno screenshot possa risultare difficoltoso.
  14. Buongiorno, ho notato che il KES installato su alcuni client mostra come versione 10.2.4.764 mentre su altri 10.2.4.764 mr2, qualcuno sa dirmi se vi è una differenza ed eventualmente quale? Grazie
×
×
  • 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.