COPE IT

Thanks - now have contact established 😊

Thanks THask, I've been put in contact with one sales partner, although they have not yet responded with a quote. That locator link is helpful thanks - may need to resort to this if the suggested contact was perhaps not UK based.

Hi Demiad - thanks for your suggestions. We already have SSL inspection disabled under our settings. The setting is locked from end-user editing as set by policy on the Admin Server. In the Policy, we have defined a small set of Trusted web addresses which are local services on the LAN, defined by DNS or IP addressing. Our 3CX (VoIP) server is included in this list (by wildcard on local sub-domain addresses). I have two policies, one for the majority of users, and one for my small Developer team, where we needed to add a couple more trust exclusions. However, that trust list was not getting pushed down to the client computers under this policy, which was apparently because the setting was not "locked" to prevent end-user adjustments. I tested locking the setting in the policy, applying the policy and reloading 3CX - it then worked OK. (I had to re-unlock the setting and reaply in order to review the list under the local KES setting to confirm that it now had the exclusions list, then go back and lock it again and reapply).

Hi, After updating to KESB 12.3.0.493 for Windows through yesterday, our 3CX calls are now badly impacted. There are a number of methods of using 3CX; Windows app, Microsoft Store desktop app, "Electron" Desktop app (soon to be deprecated) and Web browser. With the Windows app, I am now unable to dial any target (voicemail, other extension or outside line). It immediately hangs up as "call failed". In both the new Microsoft Store app version and Web browser, these are allowed to dial, but call quality is poor and very quiet, despite microphone input level being at maximum. I uninstalled KESB 12.3.0.493 and immediately all call functions and audio quality was restored under 3CX. Reinstalled KESB 12.3.0.493 and all problems with 3CX returned. Any suggestions as to how to remedy this, perhaps by policy etc? Or does this need a code/database fix from Kaspersky? Thanks

Thanks Demiad. So is switching from Ethernet to WiFi perhaps seen as a "change of network card"? That's the only suggested cause that could match. The suggestion there to just delete the duplicates (leaving one original version) is helpful to confirm our actions to tidy the list. I was a bit worried about doing that in case it caused any further problems.

Hi - wondering if anyone else gets similar issue of devices listing multiple times in the Kaspersky Security Center, with the copy usually having a random number suffix added? Example snippet of one device duplication: The device copies can also be split between the Managed and Unmanaged devices lists, despite being the same device. (We are still currently running v.12.2 of the Security Center, but plan to update this to 14.)

Thanks DonKid - we don't have a Sales Manager so far as I know. We originally purchased through GreyMatter, but due to Ukraine, they are electing not to process Kaspersky purchases at this time.

Our renewal date is imminent (24th Jan) and we'd like to increase the number of systems our licence covers from 50 to 75. The renewal page only lets us select 50 as the maximum quantity. Is it possible to renew and expand our licence count at the same time? I have already read the help/FAQ at https://support.kaspersky.com/common/buy/15468, but we can't increase the cover beyond 50. Do we have to purchase a separate licence for the additional number? If a separate (second) licence is required, how does Security Centre (server) know which licence to deploy when installing? Or would we be better to avoid using Renew totally, and just buy 75 as a direct "initial" purchase? In which case, how do we then go about updating the licences on the already-deployed systems?

Thanks for posting this Pierre. I had started to get exactly the same issue on a number of our systems for some reason (bit random). But this has helped resolve the issue for us.