Jump to content

jkfweb

Members
  • Content Count

    12
  • Joined

  • Last visited

About jkfweb

  • Rank
    Candidate
  1. This sounds like the issue we had with the Network Threat protection module with KES 11. Periodically we would lose the network connection for a few seconds and then it would start working normally again for awhile.
  2. Last time I tried to gather traces the problem didn't happen for about 20 minutes. I wasn't able to find a quick and easy trigger to easily reproduce the issue. It seems to happen more often when sending emails, but I could be wrong about that.
  3. We started rolling out KES 11 with 10.5 Agent a few months ago and have noticed some users will drop their network connection for a few seconds many times during the day. This causes applications to not respond and generally is an inconvenience. Working with Tech Support we were able to isolate the issues down to the Network Threat protection module. If we set a policy with this module disabled the users have no problem at all. Kaspersky is still waiting on me to get some additional traces from some employees who are extremely busy right now and not interested in helping me troubleshot. I just have a hard time believing our company is the only one having this problem, which is why I'm reaching out to the community here to see if any others are having the same problem. The only thing unusual about our setup/deployment is we install using the MSI method rather than the exe packages generated through the console.
  4. Thanks for your help Evgeny, I used the moving rules for the unassigned devices and have a workable solution. Out of curiosity why can't we specify the destination group name for the computer as part of the installation when using an MSI? I know when you create a packaged EXE from the KSC for the Network Agent you can specify the group it will go to, seems like an oversight to not include the same functionality as part of the MSI install. Joshua
  5. Evgeny, I used this site, https://support.kaspersky.com/12396#block1, to review the parameters currently available. I'm specifically looking for a command line parameter for the MSI installation to put clients to the proper location or group. I would also be happy if there was another application packaged with the Network Agent install that I could use to execute remotely and move the client into the proper group. We are using the 10.5 version (latest) of the Kaspersky Network Agent but there are no error logs, or relevant information to post since there is no problem installing. We don't deploy using the KSC console since about 1/3 of our clients are not directly connected, and we have not had good luck deploying to clients offline in the KSC console. We use BMC Client Management to deploy application installs world wide.
  6. I've gotten the MSI installer working perfectly for the client and the agent with the exception of one thing. I want the Network Agent install to automatically move the client to a specified group. Currently with the command line below it will install and show up in Unassigned Devices if it's a new client. msiexec.exe /i "Kaspersky Network Agent.msi" /qn DONT_USE_ANSWER_FILE=1 EULA=1 PRIVACYPOLICY=1 SERVERADDRESS="<serveraddress>" OPENUDPPORT=0 GATEWAYADDRESS="<serveraddress>" GATEWAYMODE=2 CERTSELECTION=GetOnFirstConnection Can anyone assist with this? Thanks, Joshua
  7. We are running KES 10 also and are getting calls that Chrome is not working. When we investigate on the client we find that Chrome is partially uninstalled, and Kaspersky is the reason. I've seen in the logs where Kaspersky detected a false positive. Yesterday on a machine that had this problem I was reinstalling the Chrome enterprise edition and during the install it came up with a message to disinfect or don't run. I choose don't run and the installation finished window never came up but I was able to start Chrome and it seemed installed. This never happened before roughly three months ago, not sure what changed but I'd like to know how to fix it.
  8. Kirill, Damn you are right! I uninstall the Network Agent and now all of the components are showing as installed where they weren't before so it was definitely the policy and the restriction you mentioned rather than something I was doing wrong. Thanks for your feedback, that saved me more time troubleshooting this issue. Joshua
  9. So I have the MSI Install working for my clients where I can push out the Kaspersky Uninstall/Install with a deployment software we are using internally. We are currently disabling firewall and mail modules using the setup.ini files so they are not installed, but I was thinking in the future if we wanted to re-enable those features we should be able to run something like: msiexec /i {7A4192A1-84C4-4E90-A31B-B4847CA8E23A} /qn ADDLOCAL="MailAntiVirusFeature,FirewallFeature" KLPASSWD=pwd /l*v %temp%\Log.txt Unfortunately I can't get it working, the installer will take awhile and show that it's performing tasks but the features are not installed. I've attached the log that was generated.
  10. Dustin, I really appreciate your time. The information you provided was great. We are almost exclusively Windows 7 and Windows 8 in our environment though some of our smaller international operations still have a random Windows XP or Vista machine.
  11. That is actually helpful Dustin. How many of these clients did you run into problems with(Crashes, Blue Screens or other serious issues)?
  12. I am trying to plan a deployment to multiple clients across the world in many countries. Some are directly connected to a Kaspersky Server via lan and will be managed by a Policy, while a few others are just floating on the internet with the base client and no agent. We currently use a piece of software called BMC Footprints for Software deployment and it's very similar to SCCM except we can push to any client on the internet. Below I have worked up a few scenarios from the information I have gathered Option 1: 1) Create a Standalone Package with Client and Agent (Setup.exe 225MB) with current virus database updates for each managed server 2) Create an Install Package in Footprints and push out to all clients 3) Restart Machine and manage updates with KSC Option 2: 1) Create a Standalone Package for the Agent (Setup.exe 26MB) for each managed server 2) Create an Install Package for Footprints based on the MSI (117MB), Setup.ini, CFG File, and Key to push out to all clients 3) Restart Machine and manage updates with KSC Option 3: Deploy updated KES client from KSC to clients in different locations with Kaspersky Server Use Option 1 or 2 for clients not connected to a local Kaspersky server I am leaning towards Option 2 because it would only weigh in at 143MB total, MSI installs seem to go smoother than Standalone, and all the clients are configured the same. The agent/policy installs would have to be the only thing customized per location which weigh in at 25MB and are much easier to manage. I originally leaned towards Option 1 but after some thought we wouldn't be keeping those packages up to date with the Virus Definitions and the clients would have to update anyways and I just didn't think the extra 81MB was worth it in that case. I do have a few questions, and hope some people who have done this in past can provide some feedback: 1) Do I have to uninstall the previous client before installing the new one? I've been told by 3 support agents that if the client is 8.1.0.1042 or higher then we shouldn't have to uninstall first but the install but I have a co-worker who is telling me that is wrong. 2) What is the best way to perform the install if the previous version requires a password to uninstall. 3) Any other issues I should be expecting or looking out for. I am just now starting testing but am seeking the wisdom of my predecessors and those who have done this before. Thanks, Joshua EDIT: I forgot to mention most of our clients are 8.1 or 10.1 right now, and the goal is to upgrade to 10.2
×

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.