{"id":4045,"date":"2018-03-02T11:44:58","date_gmt":"2018-03-02T17:44:58","guid":{"rendered":"https:\/\/kevinjustin.com\/blog\/?p=4045"},"modified":"2018-03-02T11:44:58","modified_gmt":"2018-03-02T17:44:58","slug":"2016-sql-sp1-patch-issue","status":"publish","type":"post","link":"https:\/\/kevinjustin.com\/blog\/2018\/03\/02\/2016-sql-sp1-patch-issue\/","title":{"rendered":"2016 SQL SP1 patch issue"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" width=\"201\" height=\"199\" class=\"alignnone size-full wp-image-4065\" alt=\"\" src=\"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2018\/03\/got-you.jpg\" \/><\/p>\n<p>False alert?<\/p>\n<p>&nbsp;<\/p>\n<p>If you have SQL2016 SP1 monitored in SCOM, you most likely have\u00a0Compliance monitor warnings<\/p>\n<p>&nbsp;<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" width=\"754\" height=\"158\" class=\"alignnone size-full wp-image-4085\" alt=\"\" src=\"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2018\/03\/SCOM-Compliance-Alert.png\" \/><\/p>\n<p>This is actually a problem with SP1 where SQL did not update the registry key.<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p><strong>Two options to remedy:<\/strong><\/p>\n<ol>\n<li>Disable SCOM monitor per instance (or class if SP1 is NOT in your environment)<\/li>\n<li>Fix the offending SQL Servers that are patched to SP1<\/li>\n<\/ol>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h2>Steps to fix the offending SQL Servers patched to SP1<\/h2>\n<p>Update Registry Key<\/p>\n<p>&nbsp;<\/p>\n<h3>Via PowerShell<\/h3>\n<p>&nbsp;<\/p>\n<p>TechNet forum is nice as well, but had to tweak it\u00a0(blog listed <a target=\"_blank\" href=\"https:\/\/social.technet.microsoft.com\/Forums\/windows\/en-US\/cf04ec56-737d-4998-973d-fe8493a19c29\/sql-2016-mp-service-pack-compliance?forum=operationsmanagermgmtpacks\" rel=\"noopener noreferrer\">here<\/a>\u00a0)<\/p>\n<p>&nbsp;<\/p>\n<p><span style=\"color: #3366ff\"># Get Instance<\/span><\/p>\n<p><span style=\"color: #3366ff\">$Instance = (Get-ItemProperty &#8220;HKLM:\\SOFTWARE\\Microsoft\\Microsoft SQL Server&#8221;).InstalledInstance )<\/span><\/p>\n<p><span style=\"color: #ff0000\">NOTE: If you have multiple instances, you will need a foreach loop<\/span><\/p>\n<p><span style=\"color: #3366ff\"># Get Version<\/span><\/p>\n<p><span style=\"color: #3366ff\">$Version = (Get-ItemProperty &#8220;HKLM:\\SOFTWARE\\Microsoft\\Microsoft SQL Server\\$((Get-ItemProperty &#8216;HKLM:\\SOFTWARE\\Microsoft\\Microsoft SQL Server\\Instance Names\\SQL&#8217;).$Instance)\\Setup&#8221;).Version<\/span><\/p>\n<p><span style=\"color: #3366ff\"># Match Version and set Registry Key<br \/>\nif ($Version -match &#8216;13.1.4&#8217;) <\/span><\/p>\n<p><span style=\"color: #3366ff\">{<\/span><\/p>\n<p><span style=\"color: #3366ff\">Set-ItemProperty -Path &#8220;HKLM:\\SOFTWARE\\Microsoft\\Microsoft SQL Server\\$((Get-ItemProperty &#8216;HKLM:\\SOFTWARE\\Microsoft\\Microsoft SQL Server\\Instance Names\\SQL&#8217;).$Instance)\\Setup&#8221; -Name &#8216;SP&#8217; -Value 1<\/span><\/p>\n<p><span style=\"color: #3366ff\">}<\/span><\/p>\n<p><span style=\"color: #3366ff\"># Verify<\/span><\/p>\n<p><span style=\"color: #3366ff\">Get-ItemProperty -path &#8220;HKLM:\\Software\\Microsoft\\Microsoft SQL Server\\MSSQL13.MSSQLSERVER\\Setup&#8221; | ft SP<\/span><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p><strong>Steps broken out<\/strong><\/p>\n<p>&nbsp;<\/p>\n<p>Get Registry Key value via PowerShell<\/p>\n<p>&nbsp;<\/p>\n<p><span style=\"color: #3366ff\">Get-ItemProperty -path &#8220;HKLM:\\Software\\Microsoft\\Microsoft SQL Server\\MSSQL13.MSSQLSERVER\\Setup&#8221; | ft SP<\/span><\/p>\n<p>&nbsp;<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" width=\"845\" height=\"95\" class=\"alignnone size-full wp-image-4055\" alt=\"\" src=\"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2018\/03\/Get-Registry-Key.png\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>Set Registry Key<\/p>\n<p>&nbsp;<\/p>\n<p><span style=\"color: #3366ff\">Set-ItemProperty -path &#8220;HKLM:\\Software\\Microsoft\\Microsoft SQL Server\\MSSQL13.MSSQLSERVER\\Setup&#8221; -name &#8220;SP&#8221; -value 1<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" width=\"843\" height=\"27\" class=\"alignnone size-full wp-image-4105\" alt=\"\" src=\"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2018\/03\/Set-Registry-Key.png\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h4>Verification<\/h4>\n<p>Verify via PowerShell<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" width=\"845\" height=\"95\" class=\"alignnone size-full wp-image-4055\" alt=\"\" src=\"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2018\/03\/Get-Registry-Key.png\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>Verify via RegEdit<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" width=\"1012\" height=\"519\" class=\"alignnone size-full wp-image-4075\" alt=\"\" src=\"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2018\/03\/Registry-Key-via-RegEdit.png\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>Reset SCOM Monitor<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" width=\"768\" height=\"462\" class=\"alignnone size-full wp-image-4095\" alt=\"\" src=\"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2018\/03\/SCOM-Reset-Monitor.png\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>And the false alert is gone!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>False alert? &nbsp; If you have SQL2016 SP1 monitored in SCOM, you most likely have\u00a0Compliance monitor warnings &nbsp; This is actually a problem with SP1 where SQL did not update the registry key. &nbsp; &nbsp; Two options to remedy: Disable SCOM monitor per instance (or class if SP1 is NOT in your environment) Fix the &hellip; <a href=\"https:\/\/kevinjustin.com\/blog\/2018\/03\/02\/2016-sql-sp1-patch-issue\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;2016 SQL SP1 patch issue&#8221;<\/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,7,11],"tags":[128,327,342,405,410,413,421],"class_list":["post-4045","post","type-post","status-publish","format-standard","hentry","category-administration","category-mp-management-pack","category-troubleshooting","tag-disable","tag-registry","tag-scom","tag-sp1","tag-sql","tag-sql-compliance-monitor","tag-sql2016"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.5 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>2016 SQL SP1 patch issue - Kevin Justin&#039;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\/2018\/03\/02\/2016-sql-sp1-patch-issue\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"2016 SQL SP1 patch issue - Kevin Justin&#039;s Blog\" \/>\n<meta property=\"og:description\" content=\"False alert? &nbsp; If you have SQL2016 SP1 monitored in SCOM, you most likely have\u00a0Compliance monitor warnings &nbsp; This is actually a problem with SP1 where SQL did not update the registry key. &nbsp; &nbsp; Two options to remedy: Disable SCOM monitor per instance (or class if SP1 is NOT in your environment) Fix the &hellip; Continue reading &quot;2016 SQL SP1 patch issue&quot;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/kevinjustin.com\/blog\/2018\/03\/02\/2016-sql-sp1-patch-issue\/\" \/>\n<meta property=\"og:site_name\" content=\"Kevin Justin&#039;s Blog\" \/>\n<meta property=\"article:published_time\" content=\"2018-03-02T17:44:58+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2018\/03\/got-you.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=\"1 minute\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2018\\\/03\\\/02\\\/2016-sql-sp1-patch-issue\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2018\\\/03\\\/02\\\/2016-sql-sp1-patch-issue\\\/\"},\"author\":{\"name\":\"Kevin Justin\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/#\\\/schema\\\/person\\\/213cdc5c6c3f2a1d9e8417c07440972d\"},\"headline\":\"2016 SQL SP1 patch issue\",\"datePublished\":\"2018-03-02T17:44:58+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2018\\\/03\\\/02\\\/2016-sql-sp1-patch-issue\\\/\"},\"wordCount\":264,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2018\\\/03\\\/02\\\/2016-sql-sp1-patch-issue\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/wp-content\\\/uploads\\\/2018\\\/03\\\/got-you.jpg\",\"keywords\":[\"disable\",\"registry\",\"SCOM\",\"sp1\",\"sql\",\"sql compliance monitor\",\"sql2016\"],\"articleSection\":[\"Administration\",\"MP Management Pack\",\"Troubleshooting\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2018\\\/03\\\/02\\\/2016-sql-sp1-patch-issue\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2018\\\/03\\\/02\\\/2016-sql-sp1-patch-issue\\\/\",\"url\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2018\\\/03\\\/02\\\/2016-sql-sp1-patch-issue\\\/\",\"name\":\"2016 SQL SP1 patch issue - Kevin Justin&#039;s Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2018\\\/03\\\/02\\\/2016-sql-sp1-patch-issue\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2018\\\/03\\\/02\\\/2016-sql-sp1-patch-issue\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/wp-content\\\/uploads\\\/2018\\\/03\\\/got-you.jpg\",\"datePublished\":\"2018-03-02T17:44:58+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/#\\\/schema\\\/person\\\/213cdc5c6c3f2a1d9e8417c07440972d\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2018\\\/03\\\/02\\\/2016-sql-sp1-patch-issue\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2018\\\/03\\\/02\\\/2016-sql-sp1-patch-issue\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2018\\\/03\\\/02\\\/2016-sql-sp1-patch-issue\\\/#primaryimage\",\"url\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/wp-content\\\/uploads\\\/2018\\\/03\\\/got-you.jpg\",\"contentUrl\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/wp-content\\\/uploads\\\/2018\\\/03\\\/got-you.jpg\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/2018\\\/03\\\/02\\\/2016-sql-sp1-patch-issue\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"2016 SQL SP1 patch issue\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/kevinjustin.com\\\/blog\\\/\",\"name\":\"Kevin Justin&#039;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":"2016 SQL SP1 patch issue - Kevin Justin&#039;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\/2018\/03\/02\/2016-sql-sp1-patch-issue\/","og_locale":"en_US","og_type":"article","og_title":"2016 SQL SP1 patch issue - Kevin Justin&#039;s Blog","og_description":"False alert? &nbsp; If you have SQL2016 SP1 monitored in SCOM, you most likely have\u00a0Compliance monitor warnings &nbsp; This is actually a problem with SP1 where SQL did not update the registry key. &nbsp; &nbsp; Two options to remedy: Disable SCOM monitor per instance (or class if SP1 is NOT in your environment) Fix the &hellip; Continue reading \"2016 SQL SP1 patch issue\"","og_url":"https:\/\/kevinjustin.com\/blog\/2018\/03\/02\/2016-sql-sp1-patch-issue\/","og_site_name":"Kevin Justin&#039;s Blog","article_published_time":"2018-03-02T17:44:58+00:00","og_image":[{"url":"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2018\/03\/got-you.jpg","type":"","width":"","height":""}],"author":"Kevin Justin","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Kevin Justin","Est. reading time":"1 minute"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/kevinjustin.com\/blog\/2018\/03\/02\/2016-sql-sp1-patch-issue\/#article","isPartOf":{"@id":"https:\/\/kevinjustin.com\/blog\/2018\/03\/02\/2016-sql-sp1-patch-issue\/"},"author":{"name":"Kevin Justin","@id":"https:\/\/kevinjustin.com\/blog\/#\/schema\/person\/213cdc5c6c3f2a1d9e8417c07440972d"},"headline":"2016 SQL SP1 patch issue","datePublished":"2018-03-02T17:44:58+00:00","mainEntityOfPage":{"@id":"https:\/\/kevinjustin.com\/blog\/2018\/03\/02\/2016-sql-sp1-patch-issue\/"},"wordCount":264,"commentCount":0,"image":{"@id":"https:\/\/kevinjustin.com\/blog\/2018\/03\/02\/2016-sql-sp1-patch-issue\/#primaryimage"},"thumbnailUrl":"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2018\/03\/got-you.jpg","keywords":["disable","registry","SCOM","sp1","sql","sql compliance monitor","sql2016"],"articleSection":["Administration","MP Management Pack","Troubleshooting"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/kevinjustin.com\/blog\/2018\/03\/02\/2016-sql-sp1-patch-issue\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/kevinjustin.com\/blog\/2018\/03\/02\/2016-sql-sp1-patch-issue\/","url":"https:\/\/kevinjustin.com\/blog\/2018\/03\/02\/2016-sql-sp1-patch-issue\/","name":"2016 SQL SP1 patch issue - Kevin Justin&#039;s Blog","isPartOf":{"@id":"https:\/\/kevinjustin.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/kevinjustin.com\/blog\/2018\/03\/02\/2016-sql-sp1-patch-issue\/#primaryimage"},"image":{"@id":"https:\/\/kevinjustin.com\/blog\/2018\/03\/02\/2016-sql-sp1-patch-issue\/#primaryimage"},"thumbnailUrl":"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2018\/03\/got-you.jpg","datePublished":"2018-03-02T17:44:58+00:00","author":{"@id":"https:\/\/kevinjustin.com\/blog\/#\/schema\/person\/213cdc5c6c3f2a1d9e8417c07440972d"},"breadcrumb":{"@id":"https:\/\/kevinjustin.com\/blog\/2018\/03\/02\/2016-sql-sp1-patch-issue\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/kevinjustin.com\/blog\/2018\/03\/02\/2016-sql-sp1-patch-issue\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/kevinjustin.com\/blog\/2018\/03\/02\/2016-sql-sp1-patch-issue\/#primaryimage","url":"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2018\/03\/got-you.jpg","contentUrl":"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2018\/03\/got-you.jpg"},{"@type":"BreadcrumbList","@id":"https:\/\/kevinjustin.com\/blog\/2018\/03\/02\/2016-sql-sp1-patch-issue\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/kevinjustin.com\/blog\/"},{"@type":"ListItem","position":2,"name":"2016 SQL SP1 patch issue"}]},{"@type":"WebSite","@id":"https:\/\/kevinjustin.com\/blog\/#website","url":"https:\/\/kevinjustin.com\/blog\/","name":"Kevin Justin&#039;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\/4045","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=4045"}],"version-history":[{"count":0,"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/posts\/4045\/revisions"}],"wp:attachment":[{"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/media?parent=4045"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/categories?post=4045"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kevinjustin.com\/blog\/wp-json\/wp\/v2\/tags?post=4045"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}