The SQL team noted that the newer versions are defaulting Encrypt to be Yes/Mandatory. That is why the new drivers were having an issue. Setting up a certificate in the SQL endpoint would have allowed the connection to work:
Don’t you wish this were the certificates we worked with!
Man, I wish I had a few of these certificates in my PKI infrastructure (portfolio)! Ever need to identify an expired certificate, and or delete the certificate? Depending on UAC, AppLocker, and other settings, the delete portion may require server logon.
Identify an expired certificate
Few ways to identify an expired certificate on servers.
Via RDP session to server
RDP to server, open MMC > Add Plug In > Certificates > for Computer
RDP to server, MMC, Certificates Plug In, Computer, expand certificate store to find expired certificate.
Via PowerShell
GCI Cert:\LocalMachine\*
The certificate store file path will vary the above command.
NOTE the SuperUser blog post will help decipher the folder name
If only certificates were all gift certificates! The ‘ADCS Addendum packs’ disables noisy rules, adds OCSP seed, OCSP responder and OCSP group (classes). Recovery and service monitoring and nCipher event are the main highlights reducing alerts for ADCS 2012,2012R2,2016+. My thanks to Bob Williams CSA, for the assist!
The ADCS Addendum packs discover OCSP (seed class), and OCSP responder registry keys installed on monitored servers.
OCSP seed class
Group discovery tailors OCSP classes, for subscription or alert tuning.
OCSP server group can be used for subscription, or alert tuning (depending on class targets)
Monitors and service recoveries keep OCSP services monitored, and only alert when manual intervention is required.
OCSP service, certsvc monitors and service recovery automations built in
Tailoring the pack(s) to your environment
First, you must have at least ONE (1) set of ADCS Active Directory Certificate Services management packs so the ‘ADCS Addendum pack’ will load. The three versions currently supported have addendums, hopefully 2012,2012R2 are planned to be decommissioned in the short term.
Second, if you don’t have OCSP in your environment, download, and then import into your environment –
ELSE
Update the ‘OCSP Responder’ server name(s) for the group regular expressions.
Update the ‘OCSP Responder’ server name(s) for the group regular expressions.
In your favorite XML editor (mine is Notepad++), open the addendum pack(s), and find/replace for the following strings:
Ran into some customers with UNIX agent problems, including Azure Oracle Enterprise Linux servers with SCOM agents.
Basically this error means
Fully-qualified domain name cannot be determined from the UNIX or Linux host itself
The FQDN known to the UNIX/Linux host does not match the FQDN used by the management server to reach the host
Full error message text
Agent verification failed. Error detail: The server certificate on the destination computer (agentname.contoso.net:1270) has the following errors:
The SSL certificate could not be checked for revocation. The server used to check for revocation might be unreachable.
The SSL certificate is signed by an unknown certificate authority.
It is possible that:
The destination certificate is signed by another certificate authority not trusted by the management server.
The destination has an invalid certificate, e.g., its common name (CN) does not match the fully qualified domain name (FQDN) used for the connection. The FQDN used for the connection is: agentname.contoso.net.
The servers in the resource pool have not been configured to trust certificates signed by other servers in the pool.
The server certificate on the destination computer (agentname.contoso.net:1270) has the following errors:
The SSL certificate could not be checked for revocation. The server used to check for revocation might be unreachable.
The SSL certificate is signed by an unknown certificate authority.
It is possible that:
The destination certificate is signed by another certificate authority not trusted by the management server.
The destination has an invalid certificate, e.g., its common name (CN) does not match the fully qualified domain name (FQDN) used for the connection. The FQDN used for the connection is: agentname.contoso.net.
The servers in the resource pool have not been configured to trust certificates signed by other servers in the pool.
Docs site – link for 1801 – Steps haven’t changed, and IMHO, docs site is better documented
Here are some commands to help troubleshoot UNIX agent
ScxAdmin
Check UNIX Agent status
scxadmin -status
Example Output
$ scxadmin -status
scxcimserver: is running
scxcimprovagt: 2 instances running
Set Unix agent to START verbose logging
scxadmin -log-set all verbose
Restart Health Service & tail scx log
scxadmin -restart
cd /var/opt/microsoft/scx/log
tail -f scx.log
To correct a SCOM agent getting a SSL certificate error:
From the Docs site, the SCXsslConfig “tool is useful in correcting issues in which the fully-qualified domain name cannot be determined from the UNIX or Linux host itself, or the FQDN known to the UNIX/Linux host does not match the FQDN used by the management server to reach the host.”
As root:
1.Get the exact hostname of the server with the hostname command
2.Stop the SCOM agent – /opt/microsoft/scx/bin/tools/scxadmin -stop
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.