{"id":9,"date":"2014-10-16T21:11:45","date_gmt":"2014-10-16T21:11:45","guid":{"rendered":"http:\/\/www.stevenhodson.com\/?p=9"},"modified":"2014-10-16T21:11:45","modified_gmt":"2014-10-16T21:11:45","slug":"configmgr-2012-r2-operating-system-deployment-failed-to-get-client-identity-80004005-surface-pro-3","status":"publish","type":"post","link":"https:\/\/www.stevenhodson.com\/?p=9","title":{"rendered":"ConfigMgr 2012 R2 Operating System Deployment \u2013 Failed to get client identity 80004005 \u2013 Surface Pro 3"},"content":{"rendered":"<p>I was on site with a customer today building some Surface Pro 3 devices using Operating System Deployment in System Center Configuration Manager 2012 R2.<\/p>\n<p>The devices were booting from USB Boot Media, however when searching for task sequences the following error message appeared \u2013 <strong>An error occurred while retrieving policy for this computer (0x80004005). For more information, please contact your system administrator or helpdesk operator.<\/strong><\/p>\n<p>Checking the SMSTS.log file, I discovered that the time and date stamps in the log seemed to be a few days old and I had come across a previous issue where if the time and date on the device were out, the task sequence would not run. I therefore decided I would have a look in the UEFI BIOS and check the time and date \u2013 only problem is on the Surface Pro 3, you cannot set the date and time in the UEFI BIOS.<\/p>\n<p>To get round this issue, I opened the command prompt by pressing F8 during Windows PE (ensure you have Command Support Testing enabled) and used the date and time commands to reset the date and time to the current values, rebooted and the task sequence ran successfully.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I was on site with a customer today building some Surface Pro 3 devices using Operating System Deployment in System Center Configuration Manager 2012 R2. The devices were booting from USB Boot Media, however when searching for task sequences the following error message appeared \u2013 An error occurred while retrieving policy for this computer (0x80004005). [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,5],"tags":[7,12],"class_list":["post-9","post","type-post","status-publish","format-standard","hentry","category-configuration-manager","category-operating-system-deployment","tag-configuration-manager","tag-operating-system-deployment"],"_links":{"self":[{"href":"https:\/\/www.stevenhodson.com\/index.php?rest_route=\/wp\/v2\/posts\/9","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.stevenhodson.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.stevenhodson.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.stevenhodson.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.stevenhodson.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=9"}],"version-history":[{"count":0,"href":"https:\/\/www.stevenhodson.com\/index.php?rest_route=\/wp\/v2\/posts\/9\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.stevenhodson.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=9"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.stevenhodson.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=9"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.stevenhodson.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=9"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}