Background: I have about 35 client pc which have KES 10.2.1.23 with network agent 10.0.3361 I also had a corrupted installation of KSC 10.0.3361 because the admin task to take backup of the administration server's data was failing complaining about could not save a 'settings' file. Also every time i started the management console the initial configuration window poped up, tried to complete all the data needed & at the end it could not save some settings file again. Problem: So, i figured if i can't take backup of the old KSC then trying to upgrade to the newer KSC version 10.1.249 was not an option. So i uninstalled the old KSC & installed the newer version after. Installation completed successfully and i started to add clients to managed computers group. After i finished i noticed that the 'Agent/Anti-Virus' column showed '-/-' for everyone. Is this normal?
I mean i know that i personally went on every client computer & installed KES & agent, i don't understand why this doesn't show up on the management console. Can this be happening because the network agent on the clients is v10.0.3361 but the KSC is v10.1.249? Thanks for your time. Hi kyriakosanagnostou, S0QR1 is on the right track here.
When you install Kaspersky Security Center (KSC) it will create a unique certificate, so at this point your new KSC installation has a different certificate than the currently deployed Network Agents know about. You can use the KLMover utility (found within the KSC program folder) to reconnect your existing Network Agents to your new KSC. Here is an example of how to do this with a KSC task:.
Create a new text file with the following 2 lines of code: “c: Program Files Kaspersky Lab NetworkAgent klmover.exe” -address NewKasperskyServerIP -silent “C: Program Files (x86) Kaspersky Lab NetworkAgent klmover.exe” -address NewKasperskyServerIP -silent. Rename it to a.bat or.cmd file. Open your Security Center and go to: Repositories Installation Packages. Right click New – Installation package. Select: “Create installation package for specified executable file” and then browse to the.bat file you created above. Finish the import of the application. Go to “Tasks for specific computers” on the left pane and create a new task.
Give it a name and select “install application remotely.”. Choose the computer you want to target, enter an admin account and set the time you want the task to run. Hi kyriakosanagnostou, S0QR1 is on the right track here.
When you install Kaspersky Security Center (KSC) it will create a unique certificate, so at this point your new KSC installation has a different certificate than the currently deployed Network Agents know about. You can use the KLMover utility (found within the KSC program folder) to reconnect your existing Network Agents to your new KSC. Here is an example of how to do this with a KSC task:. Create a new text file with the following 2 lines of code: “c: Program Files Kaspersky Lab NetworkAgent klmover.exe” -address NewKasperskyServerIP -silent “C: Program Files (x86) Kaspersky Lab NetworkAgent klmover.exe” -address NewKasperskyServerIP -silent. Rename it to a.bat or.cmd file. Open your Security Center and go to: Repositories Installation Packages.
Right click New – Installation package. Select: “Create installation package for specified executable file” and then browse to the.bat file you created above. Finish the import of the application. Go to “Tasks for specific computers” on the left pane and create a new task.
Give it a name and select “install application remotely.”. Choose the computer you want to target, enter an admin account and set the time you want the task to run. Hey there, the command line that is the easiest to use in a batch file would be klmover -address 1.2.3.4 (Where 1.2.3.4 would be the new IP address of the security center) you don't necessarily need the rest of that line.
Also, if you were able to re-assign the server to its old address, you could run a Change Administration Server task as described here to realign the Network Agents on the clients Finally, be sure to open the Network Agent installation package on the Security center and click on Connection and change the Server address to the new one so any newly installed PCs will connect to the correct IP address. Let me know if there are any further questions, Charlie KL Presales Engineerig.
OK the move to production is proceeding perfectly - so to update my proceedure I performed the following. Exported exclusions and allowed apps from the policy in the container with my PCs (I have separate containers for servers and workstations and I also break down my workstations by department. I updated to SP1. Some of my clients are having issues with getting updates. Everything was running awesome with MR1. Now with SP1 the install updates tasks fails on these clients due to a 'physical connection error' or/and 'error interacting with security console.'
Not sure how this is possible when everything was great before. No hardware changes either.
During trouble shooting: I got it working I have to restart the agents on the few clients. Then updates work.
Kaspersky Administration Server
Workaround: I have these few clients getting updates from the Kaspersky Update Servers and not my security console repository. I have a ticket opened with support already.
I can imagine that it will take them some time to go through the huge amount of data I gave them. I am just letting people know. This sort of thing may not happen to you, I just want to pass along the info in case you see something like it.
TagYourIT wrote: I updated to SP1. Some of my clients are having issues with getting updates. Everything was running awesome with MR1. Now with SP1 the install updates tasks fails on these clients due to a 'physical connection error' or/and 'error interacting with security console.' Not sure how this is possible when everything was great before.
No hardware changes either. During trouble shooting: I got it working I have to restart the agents on the few clients. Then updates work. Workaround: I have these few clients getting updates from the Kaspersky Update Servers and not my security console repository.
I have a ticket opened with support already. I can imagine that it will take them some time to go through the huge amount of data I gave them. I am just letting people know. This sort of thing may not happen to you, I just want to pass along the info in case you see something like it. I have a ticket open for the exact same issue. They had me create some log files and asked me to post the logs on their FTP site but the link they sent was invalid. I have never been able to upload files to their portal so I am waiting on a new link to their FTP site.
Improperly Installed Carseat
Garnock12 wrote: TagYourIT wrote: I updated to SP1. Some of my clients are having issues with getting updates. Everything was running awesome with MR1. Now with SP1 the install updates tasks fails on these clients due to a 'physical connection error' or/and 'error interacting with security console.' Not sure how this is possible when everything was great before. No hardware changes either.
During trouble shooting: I got it working I have to restart the agents on the few clients. Then updates work.
Workaround: I have these few clients getting updates from the Kaspersky Update Servers and not my security console repository. I have a ticket opened with support already. I can imagine that it will take them some time to go through the huge amount of data I gave them.
I am just letting people know. This sort of thing may not happen to you, I just want to pass along the info in case you see something like it. I am also seeing these errors: Event type: Error in interaction with Kaspersky Security Center Result: Connection failed, physical error Object: Kaspersky Security Center Network Agent Object Name: Kaspersky Security Center Network Agent. Brian Steingraber wrote: Garnock12 wrote: TagYourIT wrote: I updated to SP1.
Some of my clients are having issues with getting updates. Everything was running awesome with MR1. Now with SP1 the install updates tasks fails on these clients due to a 'physical connection error' or/and 'error interacting with security console.'
Not sure how this is possible when everything was great before. No hardware changes either. During trouble shooting: I got it working I have to restart the agents on the few clients.
Contoh soal psikotes bank. No information is available for this page.Learn why. CONTOH SOAL PSIKOTES DERET ANGKA.pdf - Download as PDF File (.pdf), Text File (.txt) or read online. Jun 2, 2016 - Download soal psikotes dan jawabannya, Download soal psikotes PDF dan Jawabannya, Download soal psikotes dan Pembahasannya. Nov 23, 2017 - Soal Psikotes Ui Ebook Download >>> Was.$79.99.. Contoh soal psikotes Deret GambarDeret Gambar adalah jenis soal psikotes yang paling sering anda temui, baik ketika tes seleksi kary.
Then updates work. Workaround: I have these few clients getting updates from the Kaspersky Update Servers and not my security console repository. I have a ticket opened with support already.
I can imagine that it will take them some time to go through the huge amount of data I gave them. I am just letting people know. This sort of thing may not happen to you, I just want to pass along the info in case you see something like it.
I am also seeing these errors: Event type: Error in interaction with Kaspersky Security Center Result: Connection failed, physical error Object: Kaspersky Security Center Network Agent Object Name: Kaspersky Security Center Network Agent Jon (Kaspersky). Being a man on the inside, is there any light you can shed on this?. The error message indicates that the Network Agent can't connect to the KSC server, so I would try one of a couple of things to iron this out: 1. Go into the Remote Installation Installation Packages node, open up the properties of the Network Agent (10.2.434), and in the Connection section, set the 'Server address' setting to the IP of the server (rather than name). If only to remove DNS from the troubleshooting mix. Then do an uninstall/reinstall of the Network Agent on a test machine and see if this update task will now work. I'm thinking this should solve the problem in most cases.
If the above doesn't solve it, go ahead and run the klnagchk utility on one of your problem clients and post the results here so we can see what the Network Agent is complaining about and try to narrow it further from that point. KB: (Run from elevated cmd prompt:C: Program Files Kaspersky Lab NetworkAgent klnagchk - obv if 64bit, use Program Files (x86)). Hi Jon, Kaspersky support asked me to do the following which I have done but the FTP link doesn't work and the files are to large to email and I have never been able to upload files to the web portal so I have data they haven't looked at yet. Hello Jay, Unfortunately, the traces of just the network agent were inconclusive.
Our Level 2 techs have asked to gather more information. Unfortunately, this does consist of gathering more traces. Please enable the Network Agent traces on both the server and the Client, and then please also enable the Admin Server traces as well. Please have these enabled at the time the issue occurs or appears within the Security Center.
Administration Server Traces Download: Extract the.zip file Run the on.reg util for either x32 or x64 Run the off.reg util for either x32 or x64 Collect '$klserver-1093.log' located in the Administration Server installation folder. Administrations Server Network Agent Download: Extract the.zip file Run the on.reg util for either x32 or x64 Run the off.reg util for either x32 or x64 Collect '$klnagent-1103.log' located in the Administration Server installation folder. Local Network Agent Download: Extract the.zip file Run the on.reg util for either x32 or x64 Run the off.reg util for either x32 or x64 Collect '$klnagent-1103.log' located in the Network Agent installation folder. When you have gathered these logs, please also run our GetSystemInfo utility on the client machine that you gather the Network Agent traces from. You can download the utility here: You can upload all of these files to our FTP.
Jon, I was already using the IP of the server instead of the host name. Attached is a screenshot of the error from the results. I ran the agent check at 2:10pm - Starting utility 'klnagchk'. Hi Tag - yeah that definitely looks good as far as the basic config, nothing seems obviously out of place (provided you are sure about the IP/hostname etc., which I'll defer to you on of course). At this point, I'd say the best way to go forward is going to be to submit a case to our support team since this appears to be something beyond just basic/intermediate config problems. Thanks to Jay (Garnock), you might be able to speed up the process by proactively providing the logs they've asked him for, and I'm sure you'll surprise the tech who assists with your case with that info:) If for any reason you have concerns with the support experience, please feel free to PM me and I can try to help facilitate the service. Jon (Kaspersky) wrote: Hi Jay - certainly the traces can help them try and figure out more, but I'm curious if you've tried my step 1 above just as a last ditch effort before moving on with further log gathering etc.
I'm assuming probably so, but I figure it might be worth a shot. I didn't run into this when I upgraded my demo environment, so I don't have as much light to shed on it from personal experience, I can best suggest attempting that working path to try and help avoid having to t-shoot deeper. Uninstalling and reinstalling the agent works for some time, but at some point within 24 hours the agent screws up and doesn't let updates get installed. The same works if the agent service is just restarted instead of a uninstall/reinstall.
The effect is the same for both steps. The agent works for a period of time, but than craps out when working with updates. The interesting thing is that the agent works as intended for everything else except installing updates. Even more weird is that updates install just fine when downloaded from the Kaspersky Lap Update servers instead of the Security server. I already have a ticket with Support, the tech has already sent it to level 2 for further investigation. They have logs, traces, event logs, the whole deal:) Edited Mar 18, 2015 at 18:41 UTC.
Text Total number of synchronization requests: 89 The number of successful synchronization requests: 89 Total number of synchronizations: 0 The number of successful synchronizations: 0 Clearly the Network Agent isn't able to complete a sync with the server, so I think we're going to need to get the traces to figure out what's blocking. Are you sure your clients are receiving policies? I would think that they wouldn't, so they're just operating with default settings. You can verify by opening up the actual Endpoint Security client app and see if it indicates near the top right something like the attached.
Alrighty, it has been some time since I updated everyone. I worked with support and sent them trace files and pretty much all the information they asked for. It took a week or 2 to work everything out. I was given a patch to correct the issue. At first I pushed it to just the clients with the issue.
Once I noticed that they were no longer having problems, I pushed the patch to all the rest of the clients. I will not be sharing the patch here online, but I am sure that you could contact support and work with them. Its been 3 or 4 weeks now and I have not seen the issue come back. Looks like the patch did the trick. Hope this helps.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |