LouisLewis
-
Posts
27 -
Joined
-
Last visited
Posts posted by LouisLewis
-
-
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?
-
3 minutes ago, ElvinE5 said:
for Windows solutions you can set a password
agent
KES (you can specify a domain user with different rights)
yes, make sure they are available between the server and the client for interaction. Of course, to run the application you need the agent to be connected and accept requests on UDP port 15000
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?
-
-
On 9/1/2023 at 2:11 PM, ElvinE5 said:
I can’t boast that I had the opportunity to install the solution on MacOS, in my environment they are not very common.
As for the instructions
I would start from here ... https://support.kaspersky.com/KESMac/11.3_adminguide/en-US/118670.htm
or here - https://support.kaspersky.com/KESMac/11.3_adminguide/en-US/127691.htm
about installing via SSH ... here - https://support.kaspersky.com/KESMac/11.3_adminguide/en-US/127692.htm
I think that you can basically just copy the "SH" created by you to your device and run it as an administrator,
./install.sh --accept_eula
only both the agent and the security solution if you want to manage them from the center ... check the correctness of the agent connection settings before creating a standalone package
if I were you, I would try to deploy the solution remotely, using the appropriate tasks
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?
-
On 8/22/2023 at 1:03 PM, ElvinE5 said:
good day
I think this is quite possible, requests are not particularly needed for echo to work ... here is a summary of all ports used by KSC
https://support.kaspersky.com/KSC/14.2/en-US/158830.htm
here is more detailed information on the interaction
https://support.kaspersky.com/KSC/14.2/en-US/158520.htm
in particular client-server
https://support.kaspersky.com/KSC/14.2/en-US/158525.htm
with such a spread of sites, I would suggest using a hierarchy of servers, if this is acceptable in your case and available in your license (not lower than advanced)
https://support.kaspersky.com/KSC/14.2/en-US/3304.htm
https://support.kaspersky.com/KSC/14.2/en-US/158529.htm
in this way, clients will connect to their local server, and it will already be a slave to the server in the EC
https://support.kaspersky.com/KSC/14.2/en-US/183051.htm
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.
-
36 minutes ago, ElvinE5 said:
in principle yes, but in the future you may need something else
TCP 13000 - both directions
UDP 15000 - from server to clients (for sending push notifications, for forced synchronization)
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,
-
1 hour ago, ElvinE5 said:
good day
I think this is quite possible, requests are not particularly needed for echo to work ... here is a summary of all ports used by KSC
https://support.kaspersky.com/KSC/14.2/en-US/158830.htm
here is more detailed information on the interaction
https://support.kaspersky.com/KSC/14.2/en-US/158520.htm
in particular client-server
https://support.kaspersky.com/KSC/14.2/en-US/158525.htm
with such a spread of sites, I would suggest using a hierarchy of servers, if this is acceptable in your case and available in your license (not lower than advanced)
https://support.kaspersky.com/KSC/14.2/en-US/3304.htm
https://support.kaspersky.com/KSC/14.2/en-US/158529.htm
in this way, clients will connect to their local server, and it will already be a slave to the server in the EC
https://support.kaspersky.com/KSC/14.2/en-US/183051.htm
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,
-
On 7/24/2023 at 4:37 PM, ElvinE5 said:
The keys in the "lab licenses" tab are simply records of available licenses that the server compares with which key you have activated the product (KES for example) on devices, and counts them.
1. Removing their keys from this section will not result in their removal from the client computer.
2. if according to the records of the KSC server, at least one device connected to the server is still using this key, then this key will be marked for deletion (its icon will turn gray) and it will not disappear until no device uses it.
Yes, this is equivalent to uninstalling KSWS locally from the device.
I meant the following
1. Connect to the server using the KSWS console (I wrote about this earlier)
2. Go to the license section
3. remove all licenses well, either wait for auto distribution or try to make it a task
I understand now, thank you for supporting me all this time
-
2 hours ago, ElvinE5 said:
Sometimes this behavior occurs ...
Try on a test machine to go through the KSWS console, and first delete all the keys that are on the server ... then try to re-run the key installation task ... and it should wait until the server receives it on its own (if you have auto-discovery of licenses enabled)
another option is to remove the KSWS solution remotely and install it again...
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?
-
On 7/18/2023 at 3:34 PM, ElvinE5 said:
1. Use of licenses
1.1 You need to understand that licenses are counted only from those devices that are connected to the KSC server. If you install a security solution on the device, activate it manually, but don't install the agent, and don't connect it to the KSC... this license will not be registered on the KSC server. This is not a problem, but excessive abuse of this feature (activating more copies than the license allows) can lead to legal claims, and blocking the active key.
1.2 In the standard scenario, when the client was connected to the KSC server, when removing the security solution (we no longer want to use it, or for example, before decommissioning the device), the network agent will send information to the server that the device no longer has a security solution - in this case, KSC will "release " license by increasing the number of free licenses by one.
1.3 in a scenario where it was not possible to remove the security solution (by standard means) for a reason, let's say that the hard drive failed, the agent did not transfer information to the server, and the license will not be released until information about this device is in the system. To revoke the license, simply remove the destroyed device from the KSC server, twice. First from managed devices, and then from a group of unassigned devices. The server will "forget" this device and release the license by incrementing the free license counter by one.
2. Key distribution problem
I will assume that on the remaining devices (those that "did not receive" a new key) the current keys are still active (the validity period has not expired), and you have not unchecked the key distribution task
KSWS
KES
the key has been added, but is not applied to the device until the current (old key) expires. To replace the key with a new one right now, just restart the execution of this task by first unchecking this item.
Hi Elvin, I apologize for bothering you again.
My current issue is that I have added a key and unchecked the "Use as an additional key" option, but it seems that everything is not going smoothly.
The Task report shows "Completed Successfully," but when I checked the machines, they still haven't received the key!?
I checked each machine by selecting the client machine -> Properties -> Applications -> KSWS -> Properties -> License keys, but the License keys table is completely empty.
I recreated the Task and started over, but it didn't help. Have you ever encountered a similar situation?
-
On 7/18/2023 at 3:34 PM, ElvinE5 said:
1. Use of licenses
1.1 You need to understand that licenses are counted only from those devices that are connected to the KSC server. If you install a security solution on the device, activate it manually, but don't install the agent, and don't connect it to the KSC... this license will not be registered on the KSC server. This is not a problem, but excessive abuse of this feature (activating more copies than the license allows) can lead to legal claims, and blocking the active key.
1.2 In the standard scenario, when the client was connected to the KSC server, when removing the security solution (we no longer want to use it, or for example, before decommissioning the device), the network agent will send information to the server that the device no longer has a security solution - in this case, KSC will "release " license by increasing the number of free licenses by one.
1.3 in a scenario where it was not possible to remove the security solution (by standard means) for a reason, let's say that the hard drive failed, the agent did not transfer information to the server, and the license will not be released until information about this device is in the system. To revoke the license, simply remove the destroyed device from the KSC server, twice. First from managed devices, and then from a group of unassigned devices. The server will "forget" this device and release the license by incrementing the free license counter by one.
2. Key distribution problem
I will assume that on the remaining devices (those that "did not receive" a new key) the current keys are still active (the validity period has not expired), and you have not unchecked the key distribution task
KSWS
KES
the key has been added, but is not applied to the device until the current (old key) expires. To replace the key with a new one right now, just restart the execution of this task by first unchecking this item.
I truly appreciate your help in the past few days. It has been very meaningful to me.
Almost all the issues have been resolved.
Thank you once again.
-
2 hours ago, ElvinE5 said:
Good day
I will try to explain
1. Licensing
first of all, familiarize yourself with the capabilities of your license package ...
https://b2b-compare.kaspersky.ru/
unfortunately I found only the Russian version, try using the translation of the page Google Chrome
you need to understand that the applications you install have a full range of functions, but their activation depends on the type of your license
Select license (as well as other licenses) allows you to use many solutions to protect end devices running different systems
KES - for workstation (7,8,10,11) and Servers
KSWS - for Windows Servers (2008, 2012, 2016, 2019 etc)
IOS
Android
Linux
these are different solutions, however, you will need the same license to activate them, counting licenses by total number of devices, for example...
KES - 5, KSWS -3, Linux - 2, Android -2, iOS - 1 = 13
2.what to use for servers - KES or KSWS
in terms of licenses - no difference KSWS - initially better tested for working with servers, and has a completely different set of components than KES. What to use depends on your security approach and functionality requirements.
however, I would like to clarify that at the moment the version of KSWS is 11.0.1 - and its further development is not planned, everything is being replaced by a single KES solution (now KSWS capabilities are being actively added to it), support for the solution will be extended until the end of 2024. Therefore, it is worth thinking about the transition to this solution.
https://support.kaspersky.com/help/KESWin/12.1/en-US/181834.htm
3. problems with network blocking of scanners ...
more information is needed here to understand the essence of the problem ... in any case, you can always contact technical support through your personal account
https://companyaccount.kaspersky.com
support is available to all business license users
4. local management of the KSWS client (adding keys)
if KSWS is connected to a KSC server, the installation of licenses can be done either automatically or using a task, there is no need to do it manually on each server.
By default, KSWS does not have such a local interface for managing the solution (like KES for example), to connect to the interface, you will need to additionally install the management console ... You can download it from the manufacturer's website (full distribution)
Extract the contents of the archive, and run setup.exe, on the server where you want to install the console, select the appropriate item for installation. It is not necessary to install the console on all servers in the network, the console has the ability to connect remotely to the KSWS solution, you will be asked about this in one of the console installation steps.
after that you can launch the console from the start menu or tray icons... add or remove a license or configure the settings manually if the device is not connected to the KSC
5. no ability to create tasks and policies for KSWS
you probably forgot to install the management plugin for the KSWS solution ... it will allow you to customize the solution ... you can install it from KSC
download and run the installation of the plugin, after it is completed, restart the console... you should now be able to pop in and set up policies and tasks
6. tasks
for each of the products there is a list of tasks, and if I understand correctly you did not find the virus scan task ... for KSWS this is an on-demand scan
sorry for such a long post
Thank you so much, it's been very helpful to me.
I have one more question for KSWS regarding transferring the license key from this machine to another. In the event of a malfunction (data wiped), will the activated key on the machine be automatically removed? Or is there a way to revoke the key from the KSC server?
Currently, I want to apply a new key for 11 client machines (3 of them haven't been activated, while the others are using different keys). After running the 'Task add key,' only the 3 new machines received the key (I checked in the 'Kaspersky Licenses' section on KSC). Thank you once again.
-
15 hours ago, betoO said:
If what I read is correct, now the Endpoint app for Windows can also be used on servers
You are right, I have read it in the document
"Kaspersky Endpoint Security supports core components of the application on computers running the Windows operating system for servers. You can use Kaspersky Endpoint Security for Windows instead of Kaspersky Security for Windows Server on servers and clusters of your organization (Cluster Mode)"
But I still have one question, is there anything noteworthy about the Security for Windows Server version? Have you tried using it? Please give me some advice. Thank you.
And with the KES Select license that my friend currently has, is it the best option to use the Endpoint for Windows version?
-
Apologies, the title might still be a bit vague as I'm not sure how to express it properly. Currently, my friend has purchased a Kaspersky Endpoint Security - Select license. He has installed Kaspersky Security Center (KSC) on the management server. However, on the client machines, he has installed the Security for Windows Server package (In my case, I only used the Endpoint for Windows package before).
Additional information is that both my client servers or his servers are using the Windows Server operating system.
I want to ask if it is correct for me to only install the Endpoint for Windows version on my servers? And is it correct in terms of the license for my friend to use the Security for Windows Server version? (I also don't see a manual activation option for servers like the Endpoint for Windows version).
And the Task section for these two versions in KSC is also different; I don't see the Scan task for Security for Windows Server. Am I missing any part?
On the server with Security for Windows Server installed, my friend encountered a minor issue where he had to disable the Local Server (TCP) blocking in order to perform scans, even though he had added the IP range of the scanning machine to the exclusion list. I would like to ask if there is any way to resolve this issue? Or have we misconfigured something?
These are some issues I am currently facing and I hope you guys can help me overcome these issues. English is not my native language, so some parts may be difficult to understand. Thank you for your understanding and support. thank you very much.
-
2 hours ago, ElvinE5 said:
this is an error, cannot establish an SSL connection, probably the certificate does not match.
try on the client on the same path there is another utility
C:\Program Files (x86)\Kaspersky Lab\NetworkAgent\klmover.exe
run cmd as administrator, and go to folder
cd C:\Program Files (x86)\Kaspersky Lab\NetworkAgent\
command format - klmover -address <you server name or IP>
for example - klmover -address KASSRV
you have a server DNS name KASSER, I would recommend using the IP address ... it's more reliable that way.
the command will reconnect the client to the server and get the necessary certificate from it.
wait a few minutes for the agent to restart, check the connection with the utility again and try to send a heartbeat packet, if everything is fine the device should appear on the KSC server, possibly in the "unassigned devices" section
Thank you very much, it solved my problem
I changed the name to my server IP using the klmover command and now it works
-
21 hours ago, ElvinE5 said:
Good day
There may be errors in the operation of the network administration agent, unless of course you forgot to install it ?
check the correctness of specifying the KSC server in the package settings for the network administration agent
check on your 10.0.2.40 device whether the Network Administration Agent is working correctly. this can be done using the utility in the following way
C:\Program Files (x86)\Kaspersky Lab\NetworkAgent\klcsngtgui.exe
run as administrator
make sure everything is correct
run the utility - klnagchk
make sure there are no errors
well, and probably don’t forget to check that there is an opportunity to communicate on TCP ports 13000, 14000, UDP port 15000 on the network between the server and the client
First, Thanks for the advice
I checked and found the Administration Server Address is correct.
But when I select "send heartbeat" I get the message "connection has been terminated"
utility - klnagchk returns synchronization request values all return 0 like this
Spoiler
All TCP 13000, 14000 and UDP 15000 ports are allowed on both server and client
-
Hi,
Currently my KSC server (10.0.0.254) is managing devices in the same ip range
I want to install KES on target device with ip 10.0.2.40.
I have configured firewall, can ping from KSC to target machine and from target machine to KSC machine.
But when I discover device from KSC, the server still cannot find the target device. I've tried installing using stand-alone installation package but still not able to connect to KSC.
Am I missing out on something? Please let me know if there is any way to fix it.
Thank you
-
On 11/21/2022 at 6:13 PM, ElvinE5 said:
Good day
First, determine which of the components can affect the operation of this one.
I suppose that the work may be hindered by the protection component of the firewall.
after you determine which component interferes with the work (if, of course, the matter is in the KES settings), you can configure the appropriate exceptions for this application.
What I found was that KES was somehow blocking the PSC VPN.
I've tried turning off the firewall, but nothing seems to change.
But I haven't tried setting exceptions for the application yet, hope it will work. Thanks for the advice
-
Hello everyone,
My client uses the Pulse Connect Secure software to establish a VPN connection, but they're getting an "endpoint is not compliant" message.
Is this a compatibility error?
And is there any way to solve it? Please let me know
The endpoint installed on the computer is Kaspersky Endpoint Security 11
Thank you
Change activation email (my Kaspersky account)
in My Kaspersky
Posted
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.