Posts

Showing posts from October, 2018

Build a lab CA to generate certificates for SCOM agents

I had to test adding a gateway to SCOM that was in a workgroup. I installed a CA on my DC so I could generate certs to install on the mgmt server and gateway. I used these articles to do it. To make the DC an enterprise root CA follow this: https://gallery.technet.microsoft.com/Installing-the-Root-CA-db1c6200 You'll get an error when you hit the certsrv website coz you need to add a cert to the IIS website first. This article helped with that: https://social.technet.microsoft.com/wiki/contents/articles/12039.active-directory-certificate-services-ad-cs-error-in-order-to-complete-certificate-enrollment-the-web-site-for-the-ca-must-be-configured-to-use-https-authentication.aspx You should see event id 20053 (source= OpsMgr Connector) in Ops log to say "The OpsMgr Connector has loaded the specified authentication certificate successfully."

Weird "clr enabled" error launching SCOM 2016 console

Image
Launching the SCOM 2016 console you might get this: This event will be logged on the server you're connecting to: Log name: Operations Manager Source: DataAccessLayer Event ID: 33333 Level: Warning Message: Data Access Layer rejected retry on SqlError: Request: ManagedTypeByCriteria -- (LanguageCode1=ENA), (LanguageCode2=ENU), (Id0=16781f33-f72d-033c-1df4-65a2aff32ca3) Class: 16 Number: 6263 Message: Execution of user code in the .NET Framework is disabled. Enable "clr enabled" configuration option. To fix this, first run this query against the SQL instance for SCOM. The number 1 should be in the value column: SELECT * FROM sys.configurations WHERE name = 'clr enabled' If it isn't, run this: sp_configure @configname=clr_enabled, @configvalue=1 GO RECONFIGURE GO Update 24/01/2023 - I need to confirm the sp_configure query as it's always been a DBA that runs it.

SQL instance and port syntax during install

During the SCOM install you get to 2 screens asking for the Ops db and DW location. There's a certain syntax to use depending on the SQL instance. SQL type: Standalone with standard port (1433) Change DatabaseServerName to computer\<instance> followed by a comma, and then the SQL Server port number ie. computer\instance,portNumber SQL type: Cluster Replace computer with the virtual network name of the cluster. SQL type: AlwaysOn Availability Group Replace computer\instance with the availability group listener name ie.  AvalabilityGroupListnerName,portNumber