SIR

Hello, Our problem has been solved by the Kaspersky’Support. We have some tools installed on our desktops and some processes of these tools are called when we launch Skype for example. Some of the .EXE’s of these tools were not identified (or known) by KSN (Kaspersky Security Network), so there were added in the “Low Restricted” category. Therefore, it blocked access to all audio capturing devices. Kaspersky added the files in their KSN databases and everything is working correctly now. Best regards,

Hello @Lee Ogley Sadly the issue reappeared today (7th of May) on our machines… we got our microphone access blocked again. The symptoms and behavior is the same as last time. We have re-openend the case at Kaspersky’s B2B Support... Please let me know if it is the same situation for you. Thanks ! Best regards,

Hello @Lee Ogley We have noticed that today our microphone access was back at working normally with all our videoconference softwares. We at not sure yet if Kaspersky has releasted an update within Kaspersky Updates or through KSN to correct this issue. We are waiting for their answer. May i ask you to try again your software with the microphone to see if it is working ? Be sure of the following to run the tests: Host Intrustion Prevention module is activated on the desktop you will test your mic. Latest Kaspersky databases downloaded on your Kaspersky Security Center. The desktop has it’s Kaspersky databases up-to-date (today’s date) The executable file is in “trusted” category or has a granted access to audio capturing devicesThank you ! I will send you more infos when i got the answer from Kaspersky’ Business Support. Best regards,

Hi @Lee Ogley We are experiencing the same microphone sound issue in our organization with various videocalling apps (such as Zoom or Skype) with KES 11.6.0 We noticed that only the outgoing human voice is blocked (= microphone) but the incomming sounds works fine (=headphones). We tried to manually add the “.exe” in the trusted applications area within the “Host Intrusion Prevention” module, but didn’t solve the issue. We have openend a ticket regarding this case at Kaspersky Business Support and are waiting for their answer (Ticket n° INC000012735950). For now you can do 2 things to bypass this issue: Disable the “Host Intrusion Prevention” Module (which lower the security) Stop the “Host Intrustion Prevention” module temporarly locally on the machine, launch the videocall app, and then restart the “Host Intrustion Prevention” module. It will allow the voice but just until the next OS reboot…I’ll let you know when i got an answer from Kaspersky Support’ Team. Cheers,

Hello @Larsene Try to add th application in the “Trusted” group within the “Application rights” tab of the “Host Intrustion Prevention” feature (Advanced Threat Protection module): In the “Add application to trust group” window, type the name of your executable file in the “Application” textbox. Then click on the “Refresh” button: Check the restriction group added by Kaspersky on the .exe. (! Beware of the versions ! it might have multiple ones): If it has antoher value than “Trusted” (Low Restricted, etc...), change it to trusted using the drop-down list above the “OK” button: Check that the app has been correctly added: Double-click on it. Check the applied restrictions. See if everything is unblocked (green ticks everywhere): Apply the policy and close / re-launch completely your Softphone app. See if it is working properly now. Cheers,

Hello, I would like to have some indications about the configuration of moving rules for non-persistent desktops (VDI). In a nutshell, those desktops are “refreshed” everytime a user logs off and then are recreated automatically wit the same hostname. CONTEXT: Those non-persistent desktops have the following kaspersky’s products installed: Kaspersky Network Agent 12 (KNA) - Configured with VDI configuration options Kaspersky Light Agent 5.1 (KLA) The configuration of the KNA with these VDI options are made specifically for non-persistent desktops. It executes an automatical suppression of each computer object in the Kaspersky Security Center (KSC) when the desktop is “refreshed” (=when the connection of the KNA is lost with the KSC). This behavior avoid to have multiple entries for the same computer hostname as they can be recreated a numerous number of time. GOAL: When the computer has been automatically recreated by my VDI infrastrcuture, the computer will be back again in “unassigned computers”. The creation of moving rules are then essential to be able to “push” this new freshly reinstalled computer in the right administration group again. PROBLEM: When the non-persistent desktop has been “refreshed” it appears again in the “unassigned computers”. The moving rules i have set for moving those computers is not working. I try to change the execution of the rule (“Run once for each device, then each time after reinstalling the Admin Agent” as well as “rule applied continuously”) but no changes. i have other parameters related to my environnment in the moving rule conditions but i double checked them and they are correct: Name pattern → Ok Domaine membership → Ok Member of a specific Active Directory OU → Ok “The administration agent is installed” → “Yes” “Is a virtual machine” → “Yes” “Member of a Virtual Desktop Infrastructure” → “Yes” Thank you for your suggestions.

Hello KarDip Of course i have already checked if the agent connects successfully to my gateway in the DMZ. I used the "klnagchk.exe" in "%programfiles(x86)%\Kaspersky Lab\NetworkAgent" on the client computer to check if the connection is established or not. The gateway and the distribution points are correct and all the synchronisation requests from my client to the gateway are successful.

Hello KarDip Thank you for the links. I have already followed them to put in place my config so nothing new here unfortunately. All my desktops are reporting their status, the policies are pushed and well, etc... Any further ideas ?

Hello Community, I have setted up a Kaspersky Network Agent in "gateway mode" in my DMZ to be able to still manage my roaming machines (like laptops) when they are connected to foreign networks (WAN) with internet access. I noticed that i can't launch local tasks manually from my KSC on these "out of network" machines. An error message is shown saying "Cannot launch the task". Is it normal or did i forgot something in my configuration ? Thanks for your answers !

The issue was solved by the support. The file "klcssrv.dll" file seems to have been corrupted during the update from KSC 10 to KSC 11. The support sent me a new .dll file to replace to old one. A reboot of the service after and then everything was back on track ! Details: File location: %programfile(x86)%\Kaspersky Lab\Kaspersky Security Center\ File name: klcssrv.dll Stop "kladminserver" service Rename the actual "klcssrv.dll" in "klcssrv.bak" Copy the new "klcssrv.dll" file provided by the kaspersky support in the same path Restart "kladminserver" service

A case have been openend at Kaspersky support desk (INC000010332110) to investigate the crashing service on the server hosting Kaspersky Security Console. I'll keep you updated about the resolution process.

Dear members, I have experienced a weird issue with the new Kaspersky Administration Console: Problem: I've updated my KSC to the version 11.0.0.1131 a few days ago, as well as my Kaspersky Administration Console, but time to time the console suddenly put an error message and disconnects from the Kaspersky Administration Server. After like 30-45 secondes, i am able to reconnect to my KSC. Details: Kaspersky Security Center v. 11.0.0.1131 Kaspersky Security Console v. 11.0.0.1131 Port used by the Kasperky Adm. Console to connect to KSC: 13291 KSC is installed on Windows Server 2012 R2 Console is installed on Windows 7 x64 with latests Windows Updates Checks and debugs: Error in Windows Event Logs on the server hosting the KSC (code 7031): "The Serveur d'administration de Kaspersky Security Center 11 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service." The restart of the service of course would resolve the issue but i am wondering why this service is crashing so often ? Anyone has experienced the same behavior ? Thanks for your update folks