Jump to content

ITTWP

Members
  • Content Count

    13
  • Joined

  • Last visited

About ITTWP

  • Rank
    Candidate
  1. 2. We don't know what "NAP SHA" is....this error has never come up before in previous versions of KES10. Screenshots using the Standalone Installation Package (created in KSC10, then copied and run on the computer using "Run as Administrator"): 3. Then, if we try to find out what's wrong by installing ONLY the Network Agent (like the previous User: vicksel, using the KSC installer), we get the following result:
  2. 1. Screenshots when installing using KSC10's Remote Installation Wizard:
  3. Well, I tried the above. This is what I encountered when it reaches the "Registering Network Agent as NAP SHA" stage -- mine's a Network Agent install on a clean setup of Win10 Pro x64 1709 (10.16299):
  4. Can I say that that is the stupidest reason I have ever come across. Wholeheartedly agree with user "Fleon"'s comments above. Please reinstate the previous method of deploying keys. I spent more than 30mins trying to fix this when it turned out that you guys were the ones who broke it...intentionally, it seems.
  5. Good info, Ben, but this didn't solve my issue. C'mon Kaspersky! Pull your socks up and fix this already!
  6. SYMPTOM Running KSC 9.2.69 on a WinServer 2008 Std x64. Push-installed KSCNA and KES8 onto a network of Windows machines in a Domain consisting only of the SERVER, CLIENT-A and CLIENT-B. CLIENT-B does not show up on KSC Managed Computers, but the other two installed successfully. Multiple refreshes (and restarting CLIENT- solves nothing. All DNS/DHCP/networking confirmed to be fine. Manually installed KES8+NA using a newly created "standalone installation package" onto CLIENT-B. Installs successfully. Checked in KSC, and found that CLIENT-A has disappeared from the list, replaced by CLIENT-B. Installing KES8+NA back onto CLIENT-A results in CLIENT-B disappearing from the Managed Computer List. This has happened on two different sites with the same setup. OBSERVATIONS Both are Dell machines of similar specs and model (Dell Vostro 230). Both are Windows 7 machines, with different MAC Addresses, IP Addresses (of course), etc. Both machines were cloned/imaged from the same image, but are activated with different Windows license keys (activated). QUESTION What identifier is being sent by the Clients, or being read by KSC9, to populate details on the Managed Client List? Someone from Kaspersky, please answer. What needs to be different between one Client to another, in order for KSC9 to identify one Client as unique and different from another (as in the case of CLIENT-A and CLIENT-?
  7. Yup, just coming back to underscore how shitty this product is. Installed it on a Win Server 2008 Std x64 this afternoon, pushed KES10 out onto itself, and found that I couldn't RDP to this machine anymore (eventhough Kaspersky Firewall is OFF). Had no such issues with KSC9-KES8. And this Server is in a remote location (but within our WAN). Stumbled across this post: http://forum.kaspersky.com/index.php?showtopic=258857. Fortunately we could still gain access via some other remote access tool. Otherwise I would've had to drive out to our remote site. Imagine if this happened to some poor Sys Admin whose machine was interstate, or worse, out of the country! OMG. Ultimate FAIL, Kaspersky! P/S: Don't bother to get me to post logs etc. Other Users would've supplied enough information for you Kaspersky Devs to determine where the issue is, and it should've been quickly patched/updated a long time ago.
  8. You know, this workaround works, but IT SHOULDN'T HAVE TO BE LIKE THAT. :angry: Come on, Kaspersky Devs! Test your product better before release! Having to use a workaround that requires mucking around with such an important aspect/role/function of a Domain Controller shouldn't have to be employed in order to get your shabbily designed application to work! We had issues with KAK8, then KSC9, and now this with KSC10. C'mon...enough with the inane, ridiculous issues, Kaspersky Devs! Do the job properly the first time round so that we Sys Admins can just deploy it and have it working out of the box.
  9. This is f*ckin ridiculous...this issue has been ongoing in almost all iterations of Kaspersky and it's still unresolved. Buck up, Kaspersky Support and Kaspersky Devs... I'm moving my company to another antivirus solution once our contract expires...you've just managed to lose a customer here. We may not be a big corporate customer, but remember that customer that you lose is unlikely to ever try any of your products ever again.
  10. This is f*ckin ridiculous...this issue has been ongoing in almost all iterations of Kaspersky and it's still unresolved. Buck up, Kaspersky Support and Kaspersky Devs... I'm moving my company to another antivirus solution once our contract expires...you've just managed to lose a customer here. We may not be a big corporate customer, but remember that customer that you lose is unlikely to ever try any of your products ever again.
  11. This is f*ckin ridiculous...this issue has been ongoing in almost all iterations of Kaspersky and it's still unresolved. Buck up, Kaspersky Support and Kaspersky Devs... I'm moving my company to another antivirus solution once our contract expires...you've just managed to lose a customer here. We may not be a big corporate customer, but remember that customer that you lose is unlikely to ever try any of your products ever again.
×
×
  • Create New...

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.