Jump to content

sbonilla

Members
  • Content Count

    7
  • Joined

  • Last visited

About sbonilla

  • Rank
    Candidate
  1. I had a BSOD issue when using the encryption feature on a test box. On our other machines that don't have encryption enabled, we haven't had any BSOD issues.
  2. I'd argue that it isn't. All you're doing is changing your alert criteria.
  3. Using SQL Management Studio 2008 R2 to connect to the SQL Server 2008 R2 express instance that runs my KSC instance, I can log in with windows authentication as a domain admin and query tables successfully.
  4. Thanks for your efforts, TSCADFX. I'm subscribing to this topic as this is affecting me too.
  5. In Remote installation > Installation packages, open the properties window for your KES package and go to the properties section. What is your installation type set to? What do you see for your key in this window? Is there one there? I had this same problem, needed to set my installation type to standard (no idea how it changed,) and readd my key to the package. I ran a task with the "Change application components" option to update the existing installations I have. Real pain. 3 days I've been trying to fix this, no response at all from kaspersky support...
  6. In Remote installation > Installation packages, open the properties window for your KES package and go to the properties section. What is your installation type set to? EDIT: I just noticed that you're dealing with the virtualization package so I'm probably off track here...
  7. I had the klvfs.sys error when turning encryption on and then off....then rebooting. Using F5 during bootup, I chose last known good config and was back up, easy. Still annoying, though,
×
×
  • 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.