Private cloud settings are not written to SEPM after adding certificate to SEDR certificate store until service is restarted

book

Article ID: 210260

calendar_today

Updated On:

Products

Endpoint Detection and Response Endpoint Protection with Endpoint Detection and Response Advanced Threat Protection Platform

Issue/Introduction

Private cloud settings are not written to SEPM after adding Synapse Connection until SEDR is rebooted

Cause


After configuring a Synapse entry, SEDR retrieves a certificate used for communication with the SQL server from the SEPM.
As part of this process, an error occurs when the force encryption functionality is enabled on the SQL server, and the "replication is enabled between all SEPM's"
option on SEDR is also enabled.  The issue occurs due to the handling of applying policies to the SEPM under these specific
circumstances until a reboot is done

Environment

The private cloud policy push fails if the following conditions are met:

  • secure connection to sql is used
  • replication is enabled

Resolution

  1. Upgrade to EDR 4.6.0.
  2. After upgrade, if you either add or edit a connection to a SEP Database and the following conditions are true, then reboot EDR appliance: 
    - SEPM sites with replication 
    - Replication option enabled 
    - Force encryption is configured on the SQL server