{"id":2615,"date":"2017-10-31T15:50:08","date_gmt":"2017-10-31T21:50:08","guid":{"rendered":"https:\/\/kevinjustin.com\/blog\/?p=2615"},"modified":"2019-12-20T13:11:39","modified_gmt":"2019-12-20T17:11:39","slug":"set-up-scom-2016-for-tls1-2","status":"publish","type":"post","link":"https:\/\/kevinjustin.com\/blog\/2017\/10\/31\/set-up-scom-2016-for-tls1-2\/","title":{"rendered":"Set up SCOM 2016 for TLS1.2"},"content":{"rendered":"

\"\"<\/p>\n

Security bugging you about SCOM using TLS1.0 ?<\/p>\n

 <\/p>\n

Have questions on the TLS1.2 Protocol Support Deployment guide link<\/a>?<\/p>\n

If using ACS, please review\u00a0ACS steps to configure from the\u00a0guide above<\/p>\n

 <\/p>\n

It’s time to update SCOM 2016 to TLS1.2!<\/p>\n

 <\/p>\n

Pre-requisites<\/strong><\/p>\n

.Net and SQL native client, ODBC\u00a0must be updated to TLS1.2 compliant version<\/p>\n

HTTPS Endpoints must be CA signed certificates using SHA1 or SHA2<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

Ensure .Net version 4.6 is installed on all SC components<\/h2>\n

Determine which .Net is installed https:\/\/docs.microsoft.com\/en-us\/dotnet\/framework\/migrationguide\/how-to-determine-which-versions-are-installed<\/a><\/p>\n

From PowerShell (run as admin is NOT required)<\/p>\n

Get-ChildItem ‘HKLM:\\SOFTWARE\\Microsoft\\NET Framework Setup\\NDP’ -recurse | Get-ItemProperty -name Version,Release -EA 0 | Where { $_.PSChildName -match ‘^(?!S)\\p{L}’} | Select PSChildName, Version, Release<\/span><\/span><\/p>\n

 <\/p>\n

Above commands from StackOverFlow article<\/a><\/p>\n

Guide to .Net versions and dependencies https:\/\/docs.microsoft.com\/enus\/dotnet\/framework\/migration-guide\/versions-and-dependencies<\/a><\/p>\n

 <\/p>\n

Sample output from win2k8R2 sp1 server (and same from 2016 server)<\/p>\n

\"\"<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

SQL Server updates<\/h2>\n

Install the required SQL server update supporting TLS1.2<\/p>\n

From PowerShell as Administrator
\nInvoke-Sqlcmd -Query “SELECT @@VERSION;” -QueryTimeout 3<\/span><\/p>\n

Example Output
\nPS C:\\Windows\\system32> Invoke-Sqlcmd -Query “SELECT @@VERSION;” -QueryTimeout 3
\nColumn1<\/p>\n

——<\/p>\n

Microsoft SQL Server 2016 (RTM-GDR) (KB3210111) – 13.0.1728.2 (X64) …<\/p>\n

OR<\/p>\n

Microsoft SQL Server 2008 R2 (SP2) – 10.50.4000.0 (X64)<\/p>\n

 <\/p>\n

Compare to SQL matrix to\u00a0download and install appropriate version<\/strong>
\nTLS 1.2 SQL Support https:\/\/support.microsoft.com\/en-in\/help\/3135244\/tls-1.2-support-for-microsoft-sql-server<\/a>
\nNOTE Verify you are running a compliant cumulative update (CU), you will need the patch (SQL2016 natively supports TLS1.2)<\/span>
\nSQL Server 2008R2 SP2 is NOT supported for TLS1.2\u00a0 https:\/\/blogs.msdn.microsoft.com\/sqlreleaseservices\/tls-1-2-support-for-sql-server-2008-2008-r2-2012and-2014\/<\/a><\/p>\n

 <\/p>\n

Install the required SQL Native Client<\/strong>
\nFYI – SQL 2016 uses the SQL 2012 Native client
\nDownload link https:\/\/www.microsoft.com\/en-us\/download\/details.aspx?id=50402<\/a><\/p>\n

 <\/p>\n

SQL Native client 11.0 should be installed on\u00a0ALL MS and SQL servers (SQL 2008-2016)<\/span><\/p>\n

From PowerShell as Administrator
\nget-odbcdriver -name “SQL Server Native Client*”<\/span><\/p>\n

 <\/p>\n

Example Output<\/p>\n

\"\"<\/p>\n

 <\/p>\n

 <\/p>\n

From Control Panel, Programs and Features, Installed Programs<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Stop SQL Server and SQL Server agent services<\/strong>
\nStop-service SQLSERVERAGENT <\/span><\/p>\n

Stop-service MSSQLSERVER<\/span><\/p>\n

 <\/p>\n

Install SQL Native Client MSI<\/strong><\/p>\n

Double click on SQL Native Client MSI file to begin installation<\/p>\n

Click on Yes to begin installation<\/p>\n

\"\"<\/p>\n

Click Next on the Installer window<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Click I accept radio button<\/p>\n

Click Next<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Click Next on Feature Selection<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Click Install<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Click Yes on User Account Control (UAC) prompt<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Stop SQL Server and SQL Server agent (if they restarted)<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Watch installer status<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Click Finish when complete<\/p>\n

\"\"<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

Verify SQL Native Client Verification<\/h2>\n

Verify SQL services are running<\/strong>
\nStop SQL Server and SQL Server agent services From PowerShell as Admin
\nGet-service SQLSERVERAGENT <\/span><\/p>\n

Get-service MSSQLSERVER <\/span><\/p>\n

From PowerShell as Admin If necessary, start SQL Server and SQL Server agent services
\nStart-service SQLSERVERAGENT <\/span><\/p>\n

Start-service MSSQLSERVER <\/span>
\nVerify Installer completed<\/strong>
\nIn Event Viewer, Windows Logs, Application look for event 11728<\/p>\n

\"\"<\/p>\n

 <\/p>\n

From PowerShell<\/p>\n

Get-EventLog -LogName Application | ? { $_.InstanceId -eq 11728 }<\/span><\/p>\n

\"\"<\/p>\n

Rinse and Repeat for other MS and SQL servers in environment
\n<\/strong><\/p>\n

 <\/p>\n

 <\/p>\n

Install ODBC on all Management Servers<\/h2>\n

 <\/p>\n

For SCOM & SM, ODBC 11.0 or ODBC 13.0 should be installed on all MS and SQL\u00a0servers<\/p>\n

 <\/p>\n

Verify ODBC v11 for server win2k8R2<\/strong><\/p>\n

From Control Panel<\/p>\n

Click on Programs<\/p>\n

Click on Programs and Features<\/p>\n

Search for ODBC<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Verify ODBC v13 for Server 2016<\/strong><\/p>\n

Verify version from PowerShell\u00a0(run as administrator NOT required)
\nget-odbcdriver -name “ODBC Driver * SQL Server”<\/span><\/p>\n

 <\/p>\n

Output<\/p>\n

\"\"<\/p>\n

Download and install appropriate version<\/p>\n

11.0: https:\/\/www.microsoft.com\/en-us\/download\/details.aspx?id=36434<\/a> (Version 2.0.5543.11)
\n13.0: https:\/\/www.microsoft.com\/en-us\/download\/details.aspx?id=50420<\/a>
\nVerify Installer completed<\/strong>
\nIn Event Viewer, Windows Logs, Application look for event 11728<\/p>\n

 <\/p>\n

From PowerShell<\/p>\n

Get-EventLog -LogName Application | ? { $_.InstanceId -eq 11728 } | ? { $_.Message -like “*Microsoft ODBC*”<\/span><\/p>\n

 <\/p>\n

Output<\/p>\n

\"\"<\/p>\n

 <\/p>\n

<\/h2>\n

NOTE Please make sure servers are patched with latest Monthly Rollup Updates<\/span><\/p>\n

Had issue where KB3080079 was NOT installed on server.\u00a0 Patch applied to\u00a0Win7, Server 2008,2008R2<\/p>\n

From Powershell<\/p>\n

get-hotfix -id KB3080079<\/span><\/p>\n

 <\/p>\n

Output<\/p>\n

\"\"<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

Install SCOM 2016 UR4 update<\/h2>\n

See Kevin Holman’s UR4 install blog https:\/\/blogs.technet.microsoft.com\/kevinholman\/2017\/10\/28\/ur4-for-scom-2016-step-by-step\/<\/a><\/p>\n

 <\/p>\n

Time to enable TLS1.2 Secure Channel messages on MS and SQL server (gateway if installed in your environment)<\/p>\n

See Gallery for add\/query\/remove registry keys<\/p>\n

 <\/p>\n

Add SCHANNEL path for TLS<\/strong><\/p>\n

$ProtocolList\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = @(“SSL 2.0″,”SSL 3.0″,”TLS 1.0”, “TLS 1.1”, “TLS 1.2”)<\/span>
\n$ProtocolSubKeyList = @(“Client”, “Server”)<\/span>
\n$DisabledByDefault = “DisabledByDefault”<\/span>
\n$Enabled = “Enabled”<\/span>
\n$registryPath = “HKLM:\\\\SYSTEM\\CurrentControlSet\\Control\\SecurityProviders\\SCHANNEL\\Protocols\\”<\/span><\/span><\/p>\n

foreach($Protocol in $ProtocolList)<\/span>
\n{<\/span>
\n\u00a0\u00a0\u00a0 Write-Host ” In 1st For loop”<\/span>
\n foreach($key in $ProtocolSubKeyList)<\/span>
\n { <\/span>
\n $currentRegPath = $registryPath + $Protocol + “\\” + $key<\/span>
\n Write-Host ” Current Registry Path $currentRegPath”<\/span><\/p>\n

if(!(Test-Path $currentRegPath))<\/span>
\n {<\/span>
\n \u00a0\u00a0\u00a0 Write-Host “creating the registry”<\/span>
\n New-Item -Path $currentRegPath -Force | out-Null <\/span>
\n }<\/span>
\n if($Protocol -eq “TLS 1.2”)<\/span>
\n {<\/span>
\n \u00a0\u00a0\u00a0 Write-Host “Working for TLS 1.2”<\/span>
\n New-ItemProperty -Path $currentRegPath -Name $DisabledByDefault -Value “0” -PropertyType DWORD -Force | Out-Null<\/span>
\n New-ItemProperty -Path $currentRegPath -Name $Enabled -Value “1” -PropertyType DWORD -Force | Out-Null<\/span><\/p>\n

}<\/span>
\n else<\/span>
\n {<\/span>
\n \u00a0\u00a0\u00a0 Write-Host “Working for other protocol”<\/span>
\n New-ItemProperty -Path $currentRegPath -Name $DisabledByDefault -Value “1” -PropertyType DWORD -Force | Out-Null<\/span>
\n New-ItemProperty -Path $currentRegPath -Name $Enabled -Value “0” -PropertyType DWORD -Force | Out-Null<\/span>
\n } <\/span>
\n }<\/span>
\n}<\/span><\/p>\n

\u00a0<\/span><\/p>\n

# Tighten up the .NET Framework
\n$NetRegistryPath = “HKLM:\\SOFTWARE\\Microsoft\\.NETFramework\\v4.0.30319”<\/span>
\n\u00a0New-ItemProperty -Path $NetRegistryPath -Name “SchUseStrongCrypto” -Value “1” -PropertyType DWORD -Force | Out-Null<\/span><\/p>\n

$NetRegistryPath = “HKLM:\\SOFTWARE\\WOW6432Node\\Microsoft\\.NETFramework\\v4.0.30319”<\/span>
\n\u00a0New-ItemProperty -Path $NetRegistryPath -Name “SchUseStrongCrypto” -Value “1” -PropertyType DWORD -Force | Out-Null<\/span><\/p>\n

 <\/p>\n

Restart servers<\/p>\n

 <\/p>\n

 <\/p>\n

Verify SCOM Console for alerts and connectivity<\/strong><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Security bugging you about SCOM using TLS1.0 ?   Have questions on the TLS1.2 Protocol Support Deployment guide link? If using ACS, please review\u00a0ACS steps to configure from the\u00a0guide above   It’s time to update SCOM 2016 to TLS1.2!   Pre-requisites .Net and SQL native client, ODBC\u00a0must be updated to TLS1.2 compliant version HTTPS Endpoints … Continue reading “Set up SCOM 2016 for TLS1.2”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,5],"tags":[14,15,327,342,349,410,445,446,466],"class_list":["post-2615","post","type-post","status-publish","format-standard","hentry","category-administration","category-best-practice","tag-net","tag-net-framework","tag-registry","tag-scom","tag-scom-2016","tag-sql","tag-tls","tag-tls1-2","tag-upgrade"],"yoast_head":"\nSet up SCOM 2016 for TLS1.2 - Kevin Justin's Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/kevinjustin.com\/blog\/2017\/10\/31\/set-up-scom-2016-for-tls1-2\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Set up SCOM 2016 for TLS1.2 - Kevin Justin's Blog\" \/>\n<meta property=\"og:description\" content=\"Security bugging you about SCOM using TLS1.0 ?   Have questions on the TLS1.2 Protocol Support Deployment guide link? If using ACS, please review\u00a0ACS steps to configure from the\u00a0guide above   It’s time to update SCOM 2016 to TLS1.2!   Pre-requisites .Net and SQL native client, ODBC\u00a0must be updated to TLS1.2 compliant version HTTPS Endpoints … Continue reading "Set up SCOM 2016 for TLS1.2"\" \/>\n<meta property=\"og:url\" content=\"https:\/\/kevinjustin.com\/blog\/2017\/10\/31\/set-up-scom-2016-for-tls1-2\/\" \/>\n<meta property=\"og:site_name\" content=\"Kevin Justin's Blog\" \/>\n<meta property=\"article:published_time\" content=\"2017-10-31T21:50:08+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2019-12-20T17:11:39+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2017\/10\/Safety.jpg\" \/>\n<meta name=\"author\" content=\"Kevin Justin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Kevin Justin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2017\\\/10\\\/31\\\/set-up-scom-2016-for-tls1-2\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2017\\\/10\\\/31\\\/set-up-scom-2016-for-tls1-2\\\/\"},\"author\":{\"name\":\"Kevin Justin\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/#\\\/schema\\\/person\\\/213cdc5c6c3f2a1d9e8417c07440972d\"},\"headline\":\"Set up SCOM 2016 for TLS1.2\",\"datePublished\":\"2017-10-31T21:50:08+00:00\",\"dateModified\":\"2019-12-20T17:11:39+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2017\\\/10\\\/31\\\/set-up-scom-2016-for-tls1-2\\\/\"},\"wordCount\":882,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2017\\\/10\\\/31\\\/set-up-scom-2016-for-tls1-2\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/wp-content\\\/uploads\\\/2017\\\/10\\\/Safety.jpg\",\"keywords\":[\".net\",\".net framework\",\"registry\",\"SCOM\",\"scom 2016\",\"sql\",\"tls\",\"tls1.2\",\"upgrade\"],\"articleSection\":[\"Administration\",\"Best Practice\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2017\\\/10\\\/31\\\/set-up-scom-2016-for-tls1-2\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2017\\\/10\\\/31\\\/set-up-scom-2016-for-tls1-2\\\/\",\"url\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2017\\\/10\\\/31\\\/set-up-scom-2016-for-tls1-2\\\/\",\"name\":\"Set up SCOM 2016 for TLS1.2 - Kevin Justin's Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2017\\\/10\\\/31\\\/set-up-scom-2016-for-tls1-2\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2017\\\/10\\\/31\\\/set-up-scom-2016-for-tls1-2\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/wp-content\\\/uploads\\\/2017\\\/10\\\/Safety.jpg\",\"datePublished\":\"2017-10-31T21:50:08+00:00\",\"dateModified\":\"2019-12-20T17:11:39+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/#\\\/schema\\\/person\\\/213cdc5c6c3f2a1d9e8417c07440972d\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2017\\\/10\\\/31\\\/set-up-scom-2016-for-tls1-2\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2017\\\/10\\\/31\\\/set-up-scom-2016-for-tls1-2\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2017\\\/10\\\/31\\\/set-up-scom-2016-for-tls1-2\\\/#primaryimage\",\"url\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/wp-content\\\/uploads\\\/2017\\\/10\\\/Safety.jpg\",\"contentUrl\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/wp-content\\\/uploads\\\/2017\\\/10\\\/Safety.jpg\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2017\\\/10\\\/31\\\/set-up-scom-2016-for-tls1-2\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Set up SCOM 2016 for TLS1.2\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/\",\"name\":\"Kevin Justin's Blog\",\"description\":\"Operational monitoring tools including System Center, Azure Monitor\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/#\\\/schema\\\/person\\\/213cdc5c6c3f2a1d9e8417c07440972d\",\"name\":\"Kevin Justin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/4c2a0d1189dd1ad7f305cf08aa9c5e2d4cc8fc26fde7ca573d3fd7e75520334e?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/4c2a0d1189dd1ad7f305cf08aa9c5e2d4cc8fc26fde7ca573d3fd7e75520334e?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/4c2a0d1189dd1ad7f305cf08aa9c5e2d4cc8fc26fde7ca573d3fd7e75520334e?s=96&d=mm&r=g\",\"caption\":\"Kevin Justin\"},\"url\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/author\\\/kejustin\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Set up SCOM 2016 for TLS1.2 - Kevin Justin's Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/kevinjustin.com\/blog\/2017\/10\/31\/set-up-scom-2016-for-tls1-2\/","og_locale":"en_US","og_type":"article","og_title":"Set up SCOM 2016 for TLS1.2 - Kevin Justin's Blog","og_description":"Security bugging you about SCOM using TLS1.0 ?   Have questions on the TLS1.2 Protocol Support Deployment guide link? If using ACS, please review\u00a0ACS steps to configure from the\u00a0guide above   It’s time to update SCOM 2016 to TLS1.2!   Pre-requisites .Net and SQL native client, ODBC\u00a0must be updated to TLS1.2 compliant version HTTPS Endpoints … Continue reading \"Set up SCOM 2016 for TLS1.2\"","og_url":"https:\/\/kevinjustin.com\/blog\/2017\/10\/31\/set-up-scom-2016-for-tls1-2\/","og_site_name":"Kevin Justin's Blog","article_published_time":"2017-10-31T21:50:08+00:00","article_modified_time":"2019-12-20T17:11:39+00:00","og_image":[{"url":"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2017\/10\/Safety.jpg","type":"","width":"","height":""}],"author":"Kevin Justin","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Kevin Justin","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/kevinjustin.com\/blog\/2017\/10\/31\/set-up-scom-2016-for-tls1-2\/#article","isPartOf":{"@id":"https:\/\/kevinjustin.com\/blog\/2017\/10\/31\/set-up-scom-2016-for-tls1-2\/"},"author":{"name":"Kevin Justin","@id":"https:\/\/kevinjustin.com\/blog\/#\/schema\/person\/213cdc5c6c3f2a1d9e8417c07440972d"},"headline":"Set up SCOM 2016 for TLS1.2","datePublished":"2017-10-31T21:50:08+00:00","dateModified":"2019-12-20T17:11:39+00:00","mainEntityOfPage":{"@id":"https:\/\/kevinjustin.com\/blog\/2017\/10\/31\/set-up-scom-2016-for-tls1-2\/"},"wordCount":882,"commentCount":0,"image":{"@id":"https:\/\/kevinjustin.com\/blog\/2017\/10\/31\/set-up-scom-2016-for-tls1-2\/#primaryimage"},"thumbnailUrl":"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2017\/10\/Safety.jpg","keywords":[".net",".net framework","registry","SCOM","scom 2016","sql","tls","tls1.2","upgrade"],"articleSection":["Administration","Best Practice"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/kevinjustin.com\/blog\/2017\/10\/31\/set-up-scom-2016-for-tls1-2\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/kevinjustin.com\/blog\/2017\/10\/31\/set-up-scom-2016-for-tls1-2\/","url":"https:\/\/kevinjustin.com\/blog\/2017\/10\/31\/set-up-scom-2016-for-tls1-2\/","name":"Set up SCOM 2016 for TLS1.2 - Kevin Justin's Blog","isPartOf":{"@id":"https:\/\/kevinjustin.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/kevinjustin.com\/blog\/2017\/10\/31\/set-up-scom-2016-for-tls1-2\/#primaryimage"},"image":{"@id":"https:\/\/kevinjustin.com\/blog\/2017\/10\/31\/set-up-scom-2016-for-tls1-2\/#primaryimage"},"thumbnailUrl":"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2017\/10\/Safety.jpg","datePublished":"2017-10-31T21:50:08+00:00","dateModified":"2019-12-20T17:11:39+00:00","author":{"@id":"https:\/\/kevinjustin.com\/blog\/#\/schema\/person\/213cdc5c6c3f2a1d9e8417c07440972d"},"breadcrumb":{"@id":"https:\/\/kevinjustin.com\/blog\/2017\/10\/31\/set-up-scom-2016-for-tls1-2\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/kevinjustin.com\/blog\/2017\/10\/31\/set-up-scom-2016-for-tls1-2\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/kevinjustin.com\/blog\/2017\/10\/31\/set-up-scom-2016-for-tls1-2\/#primaryimage","url":"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2017\/10\/Safety.jpg","contentUrl":"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2017\/10\/Safety.jpg"},{"@type":"BreadcrumbList","@id":"https:\/\/kevinjustin.com\/blog\/2017\/10\/31\/set-up-scom-2016-for-tls1-2\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/kevinjustin.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Set up SCOM 2016 for TLS1.2"}]},{"@type":"WebSite","@id":"https:\/\/kevinjustin.com\/blog\/#website","url":"https:\/\/kevinjustin.com\/blog\/","name":"Kevin Justin's Blog","description":"Operational monitoring tools including System Center, Azure Monitor","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/kevinjustin.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/kevinjustin.com\/blog\/#\/schema\/person\/213cdc5c6c3f2a1d9e8417c07440972d","name":"Kevin Justin","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/4c2a0d1189dd1ad7f305cf08aa9c5e2d4cc8fc26fde7ca573d3fd7e75520334e?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/4c2a0d1189dd1ad7f305cf08aa9c5e2d4cc8fc26fde7ca573d3fd7e75520334e?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/4c2a0d1189dd1ad7f305cf08aa9c5e2d4cc8fc26fde7ca573d3fd7e75520334e?s=96&d=mm&r=g","caption":"Kevin Justin"},"url":"https:\/\/kevinjustin.com\/blog\/author\/kejustin\/"}]}},"_links":{"self":[{"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/posts\/2615","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/comments?post=2615"}],"version-history":[{"count":3,"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/posts\/2615\/revisions"}],"predecessor-version":[{"id":6617,"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/posts\/2615\/revisions\/6617"}],"wp:attachment":[{"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/media?parent=2615"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/categories?post=2615"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/tags?post=2615"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}