When an administrator attempts to manually assign an Secure Sockets Layer (SSL) certificate to a Site Server Communication Profile within the Symantec Management Platform (SMP) Console, the UI allows the user to select the certificate and click "OK." However, after clicking "Save Changes" or navigating away, the certificate assignment disappears and does not persist. A persistent "Red Warning" remains visible in the console indicating that a required certificate is missing from the Site Server profile.
This behavior is most frequently encountered following a server migration, an infrastructure upgrade, or in environments where multiple certificates share identical or highly similar Subject Names within the configuration database.
Administrators may observe one or more of the following symptoms:
IT Management Suite (ITMS) 8.7.x, 8.8.x
The configuration failure occurs due to a strict validation mechanism enforced by the Symantec Management Platform. When an administrator updates a Site Server Communication Profile, the SMP verifies the certificate's unique cryptographic thumbprint against the actual Hypertext Transfer Protocol Secure (HTTPS) bindings deployed on the remote Site Server. If the selected certificate's thumbprint does not match the active Internet Information Services (IIS) binding on Port 443 for that specific Site Server, the configuration database rejects the assignment to prevent communication failures, and the console UI drops the selection without throwing an explicit error.
The selected certificate does not match the SSL certificate currently bound to the Site Server's IIS HTTPS binding.
Symantec Management Platform validates the certificate using the certificate thumbprint. If the selected certificate thumbprint differs from the thumbprint configured in IIS, the certificate assignment is rejected and is not saved in the Communication Profile.
This can occur when:
Note: The certificate picker may display multiple certificates with similar names. Always validate the certificate thumbprint rather than relying on the certificate subject name.
Run the following command from an elevated Command Prompt:
netsh http show sslcertExample output:
IP:port : 0.0.0.0:443
Certificate Hash : <Certificate Thumbprint>The Certificate Hash should match the thumbprint of the certificate selected in the Site Server Communication Profile.
Run the following PowerShell command:
Get-ChildItem Cert:\LocalMachine\My |
Select Subject, ThumbprintReview the output and identify certificates with similar subject names. Ensure the certificate selected in the Communication Profile matches the thumbprint configured in IIS.
To resolve this, you must ensure that the certificate selected in the SMP Console matches the thumbprint of the certificate actively used by the Site Server's IIS.
Use the following checklist to confirm the issue has been resolved:
| Validation Item | Expected Result |
| Communication Profile saves successfully | Certificate remains selected |
| Communication Profile reopened | Certificate assignment persists |
| Site Server warning removed | No SSL certificate warning displayed |
| HTTPS communication functions normally | Site Server communicates successfully |
| Certificate thumbprint matches IIS binding | Match confirmed |
The certificate picker displays certificates available to the platform. Validation occurs when the Communication Profile is saved.
If the selected certificate does not match the certificate currently configured in the IIS HTTPS binding, SMP prevents the configuration from being saved to avoid an invalid SSL communication configuration.
When multiple certificates have similar subject names, always use the certificate thumbprint as the authoritative identifier.