Collections:
Other Resources:
Import a Certificate
![]()
You should only import certificates obtained from trusted sources. Importing an unreliable certificate could compromise the security of any system component that uses the imported certificate.
You can import a certificate into any logical or physical store. In most cases, you will import certificates into the Personal store or the Trusted Root Certification Authorities store, depending on whether the certificate is intended for you or if it is a root certification authority (CA) certificate.
Users or local Administrators is the minimum group membership required to complete this procedure. Review the details in "Additional considerations" in this topic.
| ☞ | To import a certificate |
Open the Certificates snap-in for a user, computer, or service.
In the console tree, click the logical store where you want to import the certificate.
On the Action menu, point to All Tasks, and then click Import to start the Certificate Import Wizard.
Type the file name containing the certificate to be imported. (You can also click Browse and navigate to the file.)
If it is a PKCSÂ #12 file, do the following:
Do one of the following:
Additional considerations
✍: Microsoft
2016-07-20, ∼2223🔥, 0💬
Popular Posts:
Certificate summary - Owner: *.yfrog.com, Domain Control Validated, *.yfrog.com Issuer: SERIALNUMBER...
Why am I getting the "data too large for key size" error with OpenSSL "rsautl -encrypt -raw" command...
What is Certificate provider in Windows PowerShell? The Certificate provider is part of the Windows ...
Certificate summary - Owner: *.aboutads.info, Domain Control Validated - RapidSSL(R), See www.rapids...
Certificate summary - Owner: AlphaSSL CA - G2, AlphaSSL Issuer: GlobalSign Root CA, Root CA, GlobalS...