LouisLewis

Thank you for responding. In this case, it's just the Kaspersky Standard edition for individuals. Our customers are having issues with the activation email, and they're asking if there's a way to change it.

Hello, I'm unsure how to phrase the subject. In case I have this activation code with someone else's my Kaspersky account. Is there a way for me to transfer it to my own my Kaspersky account?

Hello, I am currently experiencing an issue where the nsqd.exe file (Kaspersky Security Center Web Console Message Queue service) is consuming 17GB of RAM on my computer, causing it to freeze. Has anyone encountered a similar situation? Is there a way to resolve this, or do I need to uninstall the KSC Web Console? Thank you.

A few days ago, while I was trying to fix the connection error to Kaspersky Endpoint Security (KES), I encountered an issue related to login credentials. According to my findings in the Event Viewer, I changed the login account to a local administrator account using klsrvswch.exe. After completing this process, I was able to log back into KES through the MMC console. However, when I tried to log in via the Web Console, I received an "invalid credential" error. I have double-checked the password and attempted to log in again, but it still doesn't work. Is there a way to resolve this issue?

My client reports that after installing the endpoint, Google Chrome keeps refreshing every 30 seconds, but this issue goes away when KES is exited. Do you know what might be causing this?

Thank you very much, that's what i was looking for

So, we don't have any way to prevent users from closing the Kaspersky application, even on the Windows version? But what I meant is that the client doesn't completely uninstall the application, it just exits (becomes inactive), but from the server side, I can't reactivate it myself (by clicking the start button). These client machines I mentioned earlier only open ports 13000 and 15000. Could this be the reason why I can't start the application from the server? Can we set up an admin password to prevent clients from closing the application?

Can we force start the solution from server??

Thank you, I run 2 command sudo sh ./klmacagent sudo sh ./kesmac11.3.0.320.sh --accpet_eula and it's work for me. And, I would like to ask if there is any way to prevent the Kaspersky client from self-deactivating?

Hello, I followed your instructions and successfully installed it on machines using the Windows operating system. However, I'm encountering a slight issue with machines running MacOS. With Windows machines, when I create a stand-alone installation package, there's an .exe file for installation. But for the MacOS installation package, I end up with 2 .sh files after creating it. I'd like to know if there's a way for me to install it locally on a MacOS machine. I've gone through the documentation, but it's still quite unclear to me.

I'd like to inquire a bit further. Because currently the server won't be able to pool client machines for remote KES installation, am I correct in assuming that I will need to create a stand-alone installation package from the KSC server and then manually install it on the clients? In the case where I have opened port 13000 on both sides and port 15000 on the KSC server, the network agent from the client machines will automatically connect to the KSC, is that correct? Thank you,

Thank you for your assistance. Based on what I've read in the documents you provided above, if we only open port 13000 on the KSC server, would that be sufficient? I noticed that port 13000 is responsible for communication between the client and server. Because the number of client machines at this time is also quite small. Thank you.

Hello, perhaps my title doesn't quite accurately reflect this situation. Our customers currently have the following server setup: 5 servers located in an office in Vietnam, 3 AWS servers (1 in Asia, 1 in the EU, 1 in China), and 1 server placed in a different office. They plan to install Kaspersky Security Center on the AWS server in the EU. However, the machines located in the office in Vietnam are currently using Private IP addresses and are unable to ping back and forth between the client and the server (the server located in the Vietnam office can still remote desktop to the AWS EU server). I would like to inquire in this scenario, if only ports (KSC used) are opened, will the server and client be able to communicate with each other? (Ping protocol is blocked) Many thanks,

I understand now, thank you for supporting me all this time

I tried to delete unused keys in the Kaspersky License tab, but I couldn't find a place to delete them. I attempted to delete them through the Web Console, but it still didn't work. I want to ask about remote KSWS solution deletion, is it similar to removing the entire KSWS from the client machine, or is it just removing the client from the Manage Device and Unassigned Device sections?