What should I do for the servers in the SMC console to have an Alive status instead of unknown?

Hello,

We recently completed a JD Edwards EnterpriseOne 9.2 deployment using One-Click Provisioning (OCP). The deployment ended successfully, but during the integration step we encountered errors, and no health checks were performed.

When we opened Server Manager Console (SMC) afterward, all the managed servers (DB, HTML, AIS, etc.) appeared with status = Unknown instead of Alive. In the agent logs we consistently see errors like:

SEVERE: E1AgentUtils.handleSslHttpGetPostWithHostnameMistmatchInCertificate: SSLException <Certificate for <192.168.175.131> doesn't match common name of the certificate subject: WIN-B0BL4HLQ5JR>

On further inspection, we found that all servers are using the Provisioning Server’s security certificate/keystore. This means that every agent (DB, HTML, AIS, etc.) is presenting the PRV server’s certificate when connecting to SMC, which causes hostname mismatches and prevents them from showing as Alive.