Jump to content

Device has become unmanaged


Recommended Posts

We are implementing a new instance of KSC 11 (11.0.0.1131) and migrating our systems a few at a time from our KSC 10 system by installing the new server agent then deploying either endpoint protection for windows (11.1.0.15919), linux (10.1.1.6421) or security for windows server (10.1.2.996) as appropriate to the system. What we are seeing with a number of the windows systems (both desktop & server) is that after a few days, some of them tend to become unmanged. Checking in the systems event logs we see the following entries... #1687 File transfer module not initialized. Service 'klnagent' has been stopped due to an error. #1687 File transfer module not initialized. Failed to start service "klnagent". #1687 File transfer module not initialized. The service won't restart from within services. Sometimes a reboot cures it, sometimes it doesn't. We've run the agent cleaner and reinstalled the agent but the problem can reoccur. It's not happening on every machine but it's happening on enough that it's becoming a problem!
Link to comment
Share on other sites

We are implementing a new instance of KSC 11 (11.0.0.1131) and migrating our systems a few at a time from our KSC 10 system by installing the new server agent then deploying either endpoint protection for windows (11.1.0.15919), linux (10.1.1.6421) or security for windows server (10.1.2.996) as appropriate to the system. What we are seeing with a number of the windows systems (both desktop & server) is that after a few days, some of them tend to become unmanged. Checking in the systems event logs we see the following entries... #1687 File transfer module not initialized. Service 'klnagent' has been stopped due to an error. #1687 File transfer module not initialized. Failed to start service "klnagent". #1687 File transfer module not initialized. The service won't restart from within services. Sometimes a reboot cures it, sometimes it doesn't. We've run the agent cleaner and reinstalled the agent but the problem can reoccur. It's not happening on every machine but it's happening on enough that it's becoming a problem!
Hello! Please create an incident to your company account with this error. Thank you!
Link to comment
Share on other sites

  • 2 months later...
Elthon, raise a support ticket as it requires a patch for the net agent. We have had to install the patch then run klmover -server %servername% -logfile klmover.log "C:\Program Files (x86)\Kaspersky Lab\NetworkAgent\klmover.exe" where %servername% is the name of your kaspersky security center instance The log file is just so you can confirm the command has completed ok
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now


×
×
  • Create New...