Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, April 5, 2017 9:14 PM
I have an issue where I have added a certificate via the MMC to the Computer Account. After I added the certificate, when I right click on the cert 'Manage Private Keys' is missing from the All Task options. I need to add Read rights to the AppPool for IIS.
This is my first time using Windows 2016 so I am not sure if I am missing something or it's not available in 2016.
Any ideas? Thanks in advance.
All replies (4)
Thursday, April 6, 2017 9:20 AM âś…Answered | 2 votes
Have you added the certificate into the trusted root certificates of your computer? Be sure to run the mmc service as an administrator. The following discussion has offered a solution to a similar query. Check if it helps: http://stackoverflow.com/questions/14337947/manage-private-keys-option-missing
Friday, April 7, 2017 5:19 PM | 1 vote
The problem was that the install was a .cer and not .pfx. As soon as I converted and reinstalled the 'Manage Private Keys' option came right up and I was able to give the App pool read access. Thanks for the answer and link!!
Thursday, December 21, 2017 3:19 PM
I had the same symptom but it was caused by my own stupid mistake. I had my certificate working but after exporting it as a pfx it stopped working.
Maybe no one else will make this mistake but just in case someone does, I mistakenly checked the option to delete the private key after export (I had not read it correctly).
The simple fix was to delete the certificate then re-import the pfx file.
Friday, November 2, 2018 10:55 AM
There are 2 requirements which helped me solving this issue:
The mmc must run under "run as admin" or you cant manage the private key.
When you choose "manage private key" from the "view actions" menu give the account how needs to access the private key the right to read the private key. Then it works as expected without any error messages.
It took me 2 day to figure out.