Today I ran into a problem which is not new to SCOM cross-platform monitoring but since this problem will hit you sooner or later it makes sense to write about it. This issue applies to all SCOM versions.
It could well be that when you are deploying SCOM agents to your UNIX/Linux server you will hit this error dialog…
SCOM uses SSL Certificates to communicate via WS-Management between the SCOM management server and the monitored server. The problem here is, that the server01 just has a “flat” common name (CN) “server01”. In order to authenticate successfully the CN name MUST match the FQDN (fully qualified domain name) of the name that is resolved by SCOM for this server e.g. server01.domain.com.
If you are facing this scenario and your UNIX/Linux server has a flat name like server01 you have two choices. Either you change the hostname on your server, which is not always an option, or you create a new certificate with the FQDN hostname and private key without touching the server name at all. I decided to create a new certificate. Just open the a shell and run…
/opt/microsoft/scx/bin/tools/scxsslconfig –h server01 –d domain.com -f –v
After you executed the command restart the agent…
/opt/microsoft/scx/bin/tools/scxadmin –restart
And your deployment will succeed…
Source and more details see TechNet.
I was also facing this issue with my Suse servers and it was really an easy fix and life saver.
Hi,
I can explain my environment. Deploy linux agent on Red Hat 6.4 but during installation error:”the agent is responded to the request but the WSMan connection failed:Access is denied
How to solve this issue. Pls give me advice.