Jump to content

mclawler75

Members
  • Content Count

    294
  • Joined

  • Last visited

1 Follower

About mclawler75

  • Rank
    Cadet

Recent Profile Visitors

798 profile views
  1. System seems to install fine on an EC2 instance with SQL Web 2016 installed on same host. Granted its a small install base, but all good.
  2. This does not appear to be an option in the Web Console, or the MMC Console. While I'm not a huge fan of the AD Polling, it is helpful if for nothing other than importing your OU Structure. Not sure if this option was removed, or overlooked, or I've been drinking to much and am just missing it. If it's the first two, it really should be added back in. If its the third, well, that's not going to change.
  3. Well, that explains this one. The test key expired on Feb 28th, 2019. Am I just to late to the game, or will there be a new one posted?
  4. I noticed when attempting to do some testing that I could not add additonal domains for AD Scanning. the Domain taht the KSC Server is part of was auto added, but I have 4 other domains in my forest that need to be added for internal testing. Root Domain Domain 1 - Where the KSC server is Domain 2 Domain 3 All domains have a full trust. There is an 'Add' button for adding IP Scopes, but not for AD Scanning.
  5. The ability to export from AD Sites and Services all of my Subnets, and then Import those into Kaspersky IP Polling. Entering them manually is fine if you've got a handful of subnets/sites.... but when you don't this is painful! Then you get to do it again if you wan to do Network Location Addresses based on subnet (because once is never enough?)
  6. Hello all, probably a simple issue and I'm doing something wrong. Installed Tech Release of KSC11 (11.0.0.1131), accessed via the web Console (11.0.95), attempting to apply the key file (572EABD.key) and I get 'Invalid Key File' Downloaded everything yesterday (12/3/19)
  7. Do you have relocation rules turned on in the 'Network Poll' section maybe? or possibly a rule to move clients on any new Network Agent install turned on? I think by default they try to move clients to 'Managed Devices' when you install the network agent.
  8. I run into this often, check that all the services are running (I have a dedicated KSC server, so when in doubt, I just reboot mine). Aside from that, it can take some time for KSC and SQL to start talking to each other correctly before you can log into the console. I've waited up to 45 minutes in the past after a reboot/patch weekend.
  9. This is a pretty common deal with Windows 7, I think you need to put in a web expection for: dns.msftncsi.com Because Microsoft is stupid, they put in a 'If you can't hit this URL, you must not have internet access' rule. By default, Kaspersky blocks that (which again is pretty stupid, since its fairly common knowledge that you need to be able to hit that URL). But when we were pushing out WIndows 7 still this is what we had to do in order to fix the alert. It fixed it for MOST clients, we still had a small handful that we just couldn't fix it for - we upgraded them to Windows 8.1 if I recall.
  10. I would LOVE a report that shows me who does not have Kaspersky AV installed on my network. I have AD Scanning turned on Kaspersky knows about every computer in my Domain I can setup a Tagging Rule for Network Agent Not Running - which will also include those that do not have a network agent, and then create a report based on Tags - and this is a decent measure of who does not have KES installed, but not 100%.... a lot of times I find that KES is installed, but the network agent is broken, or not reporting into the KSC (again). If you know the name of every computer on my domain, and I have it listed as what should be a 'Managed' computer - then tell me that it doesn't have AV Installed so I can get a good report out to my local admins all over the world for what they should be looking to fix. There HAS to be a way for me to pull this information from Kaspersky - maybe I'm writing my query wrong? Maybe there is already a report and I"m just not finding it? I know you cannot get a report from a new computer on the domain (someone got a new laptop, joined it to the domain, but didn't get Kaspersky Endpoint Security or Network Agent installed on it yet) - but I should be able to get a report that says "Hey, your AD Scanning just found this new PC and we have NEVER gotten a report from it about its status.... maybe someone should look into that'
  11. I've got a couple of PC's that updated to Windows 10 1803 and have 10.3.0.6294 installed on them. on reboot all they get is a black screen, I'm having to reboot into safe mode, remove Kaspersky, and re-install with version 10.2.6.3733. Anyone else seeing this, and if so, what all are you doing to correct it?
  12. Kaspersky Security 10 for Windows Server, Version 10.0.0.486 to be exact.
  13. Ran into an issue today on my 2016 Hyper-V Cluster. at 12:48 this afternoon I lost all iscsi traffic. could ping the filer, but couldn't connect to disk. tried rebooting, tried redoing the iscsi initiators. as a joke I did what my users always do and blamed AV.... after thinking about it I said what the hell, uninstalled KES10 for Server and rebooted. Cluster started to come back online on that node. did it on the other nodes, and they all came back online. Not sure what happened because I uninstalled everything on those nodes, but Kaspersky killed my production cluster today and for sure no one here is happy. I'll be opening a ticket with my TAM later to try to figure out what the heck happened, but just wanted to warn folks... 2016 clusters with iSCSI disk.... if you have an issue, try uninstalling AV and rebooting.
  14. I'm having a TON of problems on Dell Notebooks with Kaspersky FDE. I have tickets open for all of them (5 total so far).
  15. Personally I've tried KES10SP2, and KES10SP1MR3 and MR4.... But ANY version of KES10 would work for my questioning. I'm in the same boat as you Waterloo, our testing has been extremely painful, to the point that I'm questioning if we made the correct choice in using this for encryption. We have the keyboard issue, and on any new Dell we get BSOD after encryption. These are all latest generation systems.
×
×
  • 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.