Private keys issue fixed.

Private keys issue fixed.

Hello Everyone,

This is a notification regarding the issue in the deletion of auto generated private keys.

 

We introduced the Client Certificate Authentication feature as an additional layer of security enhancement in the build 10.0.647. Due to this, the Agent will set the client certificate for every communication with the help of windows API and the agent will create client certificate key files under the windows directory. "C:\ProgramData\Microsoft\Crypto\SystemKeys".

 

These files were not deleted by themselves and hence resulting in disk space consumption in the OS installed Drive and caused storage issues.

 

This issue has been fixed now in 10.1.2137.11.

 

Even after the upgrade to 10.1.2137.11, the agent will still create the private keys under windows directory "C:\ProgramData\Microsoft\Crypto\Keys" but it will be deleted after its use. So no more private keys will persist under any windows directory created by Desktop Central Agent.


Note: Old private keys created by agent will not be deleted using this fix. We have a workaround to delete the old keys using a Collection configuration in Desktopcentral. Please reach Desktopcentral support team if you need guidance on deleting the old private keys using this workaround. 

Update: 
We have come up with a document to delete the old keys using a Collection configuration in Desktopcentral and restore the good ones. 

Regards,

Suriya Narayanan
Product Expert -- Presales

Unified Endpoint Management & Security

Direct Support : +1 408 916 9886

Toll Free: +1 888 720 9500 (US) | 0800 028 6590 (UK) | +1 800 631 268 (AUS)

[  Desktop Management  |  Desktop Management for MSP  |  OS Deployment  |  Device Control Plus  |  Remote Access Plus




                New to ADSelfService Plus?