Learn / Deployment
Deployment · CERTSKOPE 0.6.15
Onboard a non-domain Windows server
Use the outbound agent model when domain authentication is unavailable.
Requirements
The target needs HTTPS reachability to CertSkope, DNS resolution for the application hostname, trust in the HTTPS issuing CA, and local administrator rights for agent installation. It does not need to join the domain for the agent protocol.
Onboarding flow
- Create the Windows server record with Agent connection and the intended Monitor/Manage mode.
- Generate its enrollment token. Keep the token private; rotation revokes the previous enrollment credential.
- Run the supplied agent installer on the target with the application URL, server ID and token.
- Verify agent enrollment, last-seen status and submitted inventory. Configure the local destination allowlist before requesting deployment.
Network boundaries
The target agent polls outbound over HTTPS. This is distinct from network TLS discovery, which originates from the application server and follows the approved discovery scope. Never bypass certificate validation to compensate for missing CA trust.
Continue exploring
Deploy to Windows stores or IIS →Request, approve, execute and verify the intended destination.Deploy to Tomcat and Java keystores →Use configured destinations and preserve unrelated key entries.Palo Alto firewall certificate deployment →Import inventory and stage a certificate change for operator review.
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.