Hi, 

have a look here, it solved the issue on our DS server. I think a reboot was necessary. 
https://docs.microsoft.com/en-us/windows-server/security/tls/tls-registry-settings

Hi SOTI Support Staff,
I think you missunderstood my request.
I was not asking about implementing or deploying Microsoft Defender.

We are using Microsoft Defender for Identity and alerts are being raised for the SOTI service user running the SOTI MC services due to suspicious kerberos activity.

Every time a device checks it's trying to do some kerberos authentication against our DCs using the device id of the device checking in. In the Event Viewer Security Log an Audit Failure is being logged:

An account failed to log on.

Subject:
    Security ID:        SYSTEM
    Account Name:        <SOTI MC SERVER>$
    Account Domain:        <OUR DOMAIN>
    Logon ID:        0x3E7

Logon Type:            3

Account For Which Logon Failed:
    Security ID:        NULL SID
    Account Name:        
    Account Domain:        

Failure Information:
    Failure Reason:        Unknown user name or bad password.
    Status:            0xC000006D
    Sub Status:        0xC0000064

Process Information:
    Caller Process ID:    0x2e0
    Caller Process Name:    C:\Windows\System32\lsass.exe

Network Information:
    Workstation Name:    <SOTI MC Server>
    Source Network Address:    -
    Source Port:        -

Detailed Authentication Information:
    Logon Process:        Schannel
    Authentication Package:    Kerberos
    Transited Services:    -
    Package Name (NTLM only):    -
    Key Length:        0