Console error: Strong name verification system contains exclusion entries in the registry. Blocking access

Version 2

    Verified Product Versions

    Endpoint Manager 2016.xEndpoint Manager 2017.x

    Problem:

     

    When opening a LDMS 2016 Remote Cnsole, almost immediately the error:

    "Strong name verification system contains exclusion entries in the registry. Blocking access"

    pops up

     

    Cause:

     

    This is .NET related. Strong name contains of an Assembly identity, that means the Assemblies can be assigned a cryptographic signature. The strong name guarantees the integrity of the assembly which prevents it from anyone else taking over the name of the assembly. Strong Name includes the name of the .net assembly, version number, culture identity, and a public key token. It is created from an assembly file using the corresponding private key.

     

    LANDESK relies heavily on Strong Name for security reasons and exceptions are not allowed. Exceptions are configured in the registry under the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\StrongName\Verification" key.

     

    Solution:

     

    As LANDESK doesn't support any exceptions, there should be no sub-keys under the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\StrongName\Verification" key. Often a "," key is seen. Export this registry-key for backup purposes and than delete this key. You can now start the console.

     

    If there are any other keys that seem application related, contact LANDESK Support or the Vendor support for further assistance.