blocks|key|2304501|text|转到服务器->单击开始->运行->键入mmc+->输入->选择带有本地计算机的证书管理单元选项->转到控制台根目录->证书->个人->证书->选择证书->右键单击->转到所有任务->管理私钥->添加权限|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2304502|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Go to server -> click Start -> Run -> type mmc -> enter -> select Certificates snap-in with Local Computer option -> Go to Console Root-> Certificates-> Personal-> Certificates-> Select a cert-> Right click-> Go to All tasks-> Manage Private Keys-> Add permissions

blocks|key|4416944|text|当我第一次尝试添加证书时，缺少管理私钥选项。最后通过以下两个步骤对其进行了更正。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4416945|4416946|以管理员身份运行MMC。文件->添加或删除管理单元->选择证书->单击Add+button.This将打开一个对话框。此管理单元将始终管理以下内容的证书:选择计算机帐户。选择希望此管理单元管理的计算机:选择“本地计算机”。单击Finish。单击ok。|ordered-list-item|4416947|导入个人文件夹中的证书(所有任务->导入)时，请确保导入的是.pfx文件，而不是.cer文件。|4416948|4416949|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|L|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|M|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|N|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|J|$]]

Manage Private Keys option was missing when I first tried adding the certificates. Finally corrected it by following two steps. 

<ol>
<li>Ran MMC as an administrator. File-> Add or remove Snap-ins-> Select Certificates -> Click on Add button.This will open a dialog. This snap-in will always manage certificate for : choose Computer account. Select the computer you want this snap-in to manage : choose Local computer. Click Finish. Click ok.</li>
<li>When you import the certificates(All tasks -> Import) in the Personal Folder, Make sure you are importing the .pfx file and NOT the .cer file. </li>
</ol>

blocks|key|4416866|text|我也遇到了同样的问题(管理私钥选项丢失)。为了让它出现，我必须使用“计算机帐户”选项而不是默认的“我的用户帐户”添加证书管理单元。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4416867|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had this same problem (Manage Private Keys option missing). In order to get it to appear I had to add the Certificates snap-in using the "Computer account" option instead of the default "My user account"

blocks|key|5833405|text|在Windows101809中，管理私钥选项似乎只对个人存储区中的证书可用。解决方法是将证书拖放到此处，根据需要添加权限，然后将其拖回需要的位置。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|5833406|entityMap^0|G|4|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

In Windows 10 1809, it seems that the Manage Private Keys option is available only to certificates in the Personal store. The workaround is to drag and drop the certificate there, add permissions as needed and drag it back to where you need it.

blocks|key|2304519|text|可能还有另外一个问题，所以我会提一下。使用makecert.exe创建证书时，除-pe参数外，请确保导入的是.pfx文件，而不是.cer。如果没有.pfx文件，请使用其他工具(如pvk2pfx.exe+)来创建。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2304520|entityMap^0|14|3|1I|4|1S|4|21|4|2H|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|G|$]]

There can be one other problem, so I will mention it. Except <code>-pe</code> argument when creating a certificate using makecert.exe, be sure you are importing the <code>.pfx</code> file, not the <code>.cer</code>. If there is not a <code>.pfx</code> file, use an additional tool such as <code>pvk2pfx.exe</code> to created.

blocks|key|1773333|text|管理私钥选项仅适用于具有可导出私钥的证书|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1773334|在我的例子中，尽管配置了证书管理单元来访问计算机帐户，我还是遇到了这个问题。此外，在this+answer中获得.PFX证书的建议对我来说不是一个选择。|offset|length|1773335|我通过在创建证书请求时指定私钥是可导出的(我正在通过证书MMC管理单元执行此操作)解决了这个问题：|1773336|​|1773337|📷|atomic|1773338|1773339|尽管我从公共CA得到的证书是一个.CER文件，但是Manage+Private+Keys菜单选项对它是可用的。我对证书了解不多，但我得出的结论是，只有在可以导出私钥时，才会出现菜单选项。根据this+answer，也许.PFX格式的证书总是允许这样做。尽管如此，知道其他证书格式也是可能的，这是件好事。|style|CODE|1773340|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/37867991/2227908|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/a3f8b994dfb3d7da2d01aee3dfa26e16.png|imageAlt|2^0|0|16|B|0|0|0|0|0|1|1|0|0|G|4|2N|B|2|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@$D|18|E|19|1|1A]]|A|$]]|$1|F|3|G|5|6|7|1B|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1C|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1D|8|@]|9|@$D|1E|E|1F|1|1G]]|A|$]]|$1|M|3|I|5|6|7|1H|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1I|8|@$D|1J|E|1K|P|Q]]|9|@$D|1L|E|1M|1|1N]]|A|$]]|$1|R|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]|Z|$5|10|V|11|A|$12|13|14|-4]]|15|$5|U|V|W|A|$X|Y]]]]

<h3>The Manage Private Keys Option is only available for certificates with an exportable private key</h3>
In my case, I experienced this problem despite configuring the Certificates snap-in to access the COMPUTER account. Further, the suggestion to get a .PFX certificate in <a href="https://stackoverflow.com/a/37867991/2227908">this answer</a> isn't an option for me.
I solved the problem by specifying that the private key be exportable when creating the certificate request (which I'm doing via the Certificates MMC snap-in):
<a href="https://i.stack.imgur.com/UMvFA.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/UMvFA.png" alt="enter image description here" /></a>
Even though the certificate I got back from the public CA was a <code>.CER</code> file, the Manage Private Keys menu option was available for it. I don't know a lot about certificates, but I conclude that the menu option only appears when the private key can be exported. In light of <a href="https://stackoverflow.com/a/37867991/2227908">this answer</a>, perhaps certificates in the .PFX format always allow this to be done. Nonetheless, it's good to know it's possible for other certificate formats.

blocks|key|4417045|text|命令提示符打开(以Administrator)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4417046|Enter身份运行并执行|unordered-list-item|4417047|，|ordered-list-item|4417048|4417049|4417050|certutil+-repairstore+my+"+thumbprint“(用32个字符替换指纹)|offset|length|style|BOLD|4417051|如果成功，您将收到消息，|4417052|4417053|certUtil：命令已完成successfully.|4417054|entityMap^0|0|0|0|0|0|0|8|0|0|0|0|8|9|I|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|Y|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@$L|12|M|13|N|O]]|9|@]|A|$]]|$1|P|3|Q|5|D|7|14|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|16|8|@$L|17|M|18|N|O]|$L|19|M|1A|N|O]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|V|$]]

<ol>
<li>Open the Command Prompt (Run as Administrator)</li>
<li>Enter and execute command, 
certutil -repairstore my "thumbprint" (replace thumbprint
with the 32 characters) </li>
<li>If succesful, you will recieve message, 
certUtil: -repairstore command completed successfully.</li>
</ol>

I'm developing WCF service with Transport Security hosted on IIS 7.5 under Windows 2008R2. I have a certificate, generated in IIS 7.5 which is stored in Local folder.

When I use BasicHttpBinding or WSHttpBinding with Transport Security - everything works fine. But when I change it to NetTcp I get an exception :

<pre><code> CryptographicException 'Keyset does not exist'. 
</code></pre>

After a bit of googling I found out that the problem can be because my NETSERVICE IIS account doesn't have premission to the private key of my certificate. 

The solution could be to set the rights to accesss in MMC by right-clicking on my certificate and selecting "MANAGE PRIVATE KEYS" option. But there is no such option in the select menu!!! The Certificate was created under administrator account and where I open it - it says, that it has private key. What I'm I doing wrong?

'MANAGE PRIVATE KEYS' option missing

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在Windows 2008R2下的IIS 7.5上开发带有传输安全的WCF服务。我有一个在IIS 7.5中生成的证书，它存储在本地文件夹中。当我使用具有传输安全的BasicHttpBinding或WSHttpBinding时，一切都工作正常。但是当我将它更改为NetTcp时，我得到了一个异常： CryptographicException 'Keyset does not exist'. 在谷

问缺少‘'MANAGE私钥’选项
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问缺少‘'MANAGE私钥’选项EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问缺少‘'MANAGE私钥’选项
EN