Learn / Deployment

Deployment · CERTSKOPE 0.6.15

Deploy to Windows stores or IIS

Request, approve, execute and verify the intended destination.

Updated 17 November 2026 ·

Before requesting a push

Onboard the server and enroll its agent where required. Manage the certificate and ensure its matching private key is available when the destination needs it. Destination stores and bindings must be allowed by the target configuration.

Deployment procedure

  1. Open a certificate → Push to onboarded server.
  2. Choose the target and destination: Windows certificate store or IIS binding. Select the intended LocalMachine store.
  3. Submit for approval. A different authorized approver approves, then execute the approved job.
  4. Read the deployment receipt. Verify the certificate in the selected store and, for IIS, the actual bound HTTPS endpoint.

Store boundaries

Personal (My) and WebHosting are common leaf-certificate destinations. Root/CA and other trust stores have additional restrictions; trust-store changes use public CA certificates only where applicable. Store installation does not itself bind a certificate to IIS.

If a push fails

Confirm the configured binding hostname appears in the SAN, the agent is enrolled and polling, and the local target allowlist permits the destination. Do not treat a queued job as an installed certificate.

Continue exploring

Was this guide helpful?

This guide describes CertSkope 0.6.15. A saved integration profile alone does not activate an external connector. See feature availability.