Jump to content

Renan Corassa

Members
  • Posts

    10
  • Joined

  • Last visited

Everything posted by Renan Corassa

  1. The KSC Server must have access to the internet or at least the addresses listed in the documentation. https://support.kaspersky.com/KSC/14.2/en-US/255242.htm
  2. Create the task for Change Components and add the KES EDR
  3. Acessar a console Vá até a política que gerencia esse dispositivo Acesse a opção da proteção contra ameaça web e deixe o cadeado aberto. Aplique a política e aguarde comunicação.
  4. Pessoal, caso ainda tenho problema com a Alura. Tentem colocar esses endereços na lista de confiáveis *.alura.com.b/* *cdn12.com/* *s3.amazonaws.com/*
  5. The image is cropped on purpose. Just follow the arrow and the cursor in the shape of an index finger will appear. Just click that will return what you need
  6. How possibility is the problem to be on the database side and not the KSC console? I'm facing the same problem. =( KSC 13.2 SQL Server 2019 Standard Additional recommendations have already been made. USE KAV GO ALTER DATABASE SCOPED CONFIGURATION SET TSQL_SCALAR_UDF_INLINING = OFF GO Unfortunately, most of the time the processing is high, close to 100%.
  7. Of course, this bar could have been better displayed.
  8. Hello. @Max404 Do not freak out. I had this same "problem". The information is collected on the side. Hope this helps.
×
×
  • Create New...