{"id":658,"date":"2016-03-23T09:43:18","date_gmt":"2016-03-23T09:43:18","guid":{"rendered":"https:\/\/www.lieben.nu\/liebensraum\/?p=658"},"modified":"2016-03-23T09:43:18","modified_gmt":"2016-03-23T09:43:18","slug":"intune-client-does-not-appear-in-console-and-displays-error-0x80070005-when-updating","status":"publish","type":"post","link":"https:\/\/lieben.nu\/liebensraum\/2016\/03\/intune-client-does-not-appear-in-console-and-displays-error-0x80070005-when-updating\/","title":{"rendered":"Intune Client does not appear in console and displays error 0x80070005 when updating"},"content":{"rendered":"<p>If you want to deploy the Intune Client using a (golden\/generalized) image with System Center Configuration Manager or any other tool, make sure you haven&#8217;t already installed the Intune Client\u00a0on that machine and <a href=\"https:\/\/technet.microsoft.com\/en-us\/library\/dn646969.aspx\" target=\"_blank\">follow the correct procedure<\/a>.<\/p>\n<p>The Intune Client generates a machine specific certificate in the Personal Store of the machine. This certificate is only valid for that machine. If you then base your image on this machine, all installations using that image will fail, Intune will report error 0x80070005 when trying to update. The full log of Updates.log in c:\\Program Files\\Microsoft\\OnlineManagement\\Logs will look like this below log.<\/p>\n<p>EDIT: if you want to &#8216;reset&#8217; \/ &#8216;fix&#8217; the Intune Client with a script \/ automatically, <a href=\"https:\/\/www.lieben.nu\/liebensraum\/2016\/03\/killing-and-reinstalling-the-intune-client-without-user-interaction\/\">read here<\/a><\/p>\n<p><!--more--><\/p>\n<pre>2016-03-23 09:45:59:293 4800 12b0 Agent Agent servicing time window policy is not set\n2016-03-23 09:45:59:293 4800 12b0 Agent WARNING: Unable to read agent servicing time window policy, error = 0x80070002.\n2016-03-23 09:45:59:293 4800 12b0 AgntUpd WARNING: Failed to update task triggers, error = 0x80070002\n2016-03-23 09:45:59:294 4800 12b0 AgntUpd #############\n2016-03-23 09:45:59:294 4800 12b0 AgntUpd ## START ## AgntUpd: Search for agents [Service = \"Microsoft Intune\"]\n2016-03-23 09:45:59:294 4800 12b0 AgntUpd #########\n2016-03-23 09:45:59:295 4800 12b0 AgntUpd &lt;&lt;## SUBMITTED ## AgntUpd: Search for agents [Service = \"Microsoft Intune\", CallId = {5D632D8E-3C20-4F2F-B2EB-BB67C0CBB349}]\n2016-03-23 09:45:59:296 4800 128c Agent *************\n2016-03-23 09:45:59:296 4800 128c Agent ** START ** Agent: Finding updates [CallerId = Client Agents Sync]\n2016-03-23 09:45:59:296 4800 128c Agent *********\n2016-03-23 09:45:59:296 4800 128c Agent * Online = Yes; Ignore download priority = No\n2016-03-23 09:45:59:296 4800 128c Agent * Criteria = \"CategoryIDs contains '27cd64a2-e5d7-468d-ac5d-7bd7ccae1880' and IsInstalled=0 and Type='Software'\"\n2016-03-23 09:45:59:296 4800 128c Agent * ServiceID = Microsoft Intune\n2016-03-23 09:45:59:296 4800 128c Agent * Search Scope = {Machine}\n2016-03-23 09:45:59:352 4800 128c EP Obtained plugin IUpdateEndpointProvider on CLSID 3BF1D171-8D71-44C4-B234-302390EDD390\n2016-03-23 09:45:59:352 4800 128c EP Obtained plugin IUpdateEndpointAuthProvider on CLSID 3BF1D171-8D71-44C4-B234-302390EDD390\n2016-03-23 09:45:59:352 4800 128c EP SLS: Initializing for service ID 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7\n2016-03-23 09:45:59:352 4800 128c EP SLS: Reading from cache\n2016-03-23 09:45:59:352 4800 128c EP SLS: Successfully read service endpoints from cache.\n2016-03-23 09:45:59:355 4800 128c EP Got service Microsoft Intune plugin Client\/Server preferred token types: 0x00000001\n2016-03-23 09:45:59:355 4800 128c EP Got service Microsoft Intune plugin Client\/Server URL: \"https:\/\/msub02.manage.microsoft.com\/ClientWebService\/client.asmx\/auth\"\n2016-03-23 09:45:59:454 4800 128c WS WARNING: Nws Failure: errorCode=0x80070005\n2016-03-23 09:45:59:455 4800 128c WS WARNING: Original error code: 0x80072f9a\n2016-03-23 09:45:59:455 4800 128c WS WARNING: There was an error communicating with the endpoint at 'https:\/\/msub02.manage.microsoft.com\/AgentSecurityTokenService\/IWSTrust.svc'.\n2016-03-23 09:45:59:455 4800 128c WS WARNING: There was an error sending the HTTP request.\n2016-03-23 09:45:59:455 4800 128c WS WARNING: Access is denied.\n2016-03-23 09:45:59:455 4800 128c WS WARNING: The client certificate credentials were not recognized.\n2016-03-23 09:45:59:455 4800 128c WS WARNING: Web service call failed with hr = 80070005.\n2016-03-23 09:45:59:455 4800 128c WS WARNING: Current service auth scheme='None'.\n2016-03-23 09:45:59:455 4800 128c WS WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.\n2016-03-23 09:45:59:455 4800 128c WS FATAL: OnCallFailure(hrCall, m_error) failed with hr=0x80070005\n2016-03-23 09:45:59:455 4800 128c WS FATAL: NwsCallWithRetryOnTransientError&lt;Functor&gt;(Functor(&amp;token, (propertyCount == 0) ? NULL : properties, propertyCount)) failed with hr=0x80070005\n2016-03-23 09:45:59:455 4800 128c EP FATAL: Retrieve agent token failed. Error code hr = 0x80070005\n2016-03-23 09:45:59:455 4800 128c EP WARNING: Failed to acquire Agent Token From Server, hr 0x80070005\n2016-03-23 09:45:59:455 4800 128c EP FATAL: SLS: Call to GetEndpointToken failed, error = 0x80070005\n2016-03-23 09:45:59:455 4800 128c EP FATAL: Failed to obtain service Microsoft Intune plugin Client\/Server auth token of type 0x00000001, error = 0x80070005\n2016-03-23 09:45:59:455 4800 128c EP FATAL: SLS: Failed to obtain endpoint token, error = 0x80070005\n2016-03-23 09:45:59:456 4800 128c EP FATAL: Failed to obtain service Microsoft Intune plugin Client\/Server URL, error = 0x80070005\n2016-03-23 09:45:59:456 4800 128c PT WARNING: PTError: 0x80070005\n2016-03-23 09:45:59:456 4800 128c PT WARNING: Initialization failed for Protocol Talker Context: 0x80070005\n2016-03-23 09:45:59:456 4800 128c PT WARNING: StartCategoryScan failed : 0x80070005\n2016-03-23 09:45:59:456 4800 128c Agent WARNING: Search for internal updates failed with 0x80070005\n2016-03-23 09:45:59:456 4800 128c Agent * WARNING: Exit code = 0x80070005\n2016-03-23 09:45:59:456 4800 128c Agent *********\n2016-03-23 09:45:59:456 4800 128c Agent ** END ** Agent: Finding updates [CallerId = Client Agents Sync]\n2016-03-23 09:45:59:456 4800 128c Agent *************\n2016-03-23 09:45:59:456 4800 128c Agent WARNING: Updates client failed Searching for update with error 0x80070005\n2016-03-23 09:45:59:456 4800 11d4 AgntUpd &gt;&gt;## RESUMED ## AgntUpd: Search for agents [Service = \"Microsoft Intune\", CallId = {5D632D8E-3C20-4F2F-B2EB-BB67C0CBB349}]\n2016-03-23 09:45:59:456 4800 11d4 AgntUpd # WARNING: Search callback failed, result = 0x80070005\n2016-03-23 09:45:59:456 4800 11d4 AgntUpd #########\n2016-03-23 09:45:59:456 4800 11d4 AgntUpd ## END ## AgntUpd: Search for agents [Service = \"Microsoft Intune\", CallId = {5D632D8E-3C20-4F2F-B2EB-BB67C0CBB349}]\n2016-03-23 09:45:59:456 4800 11d4 AgntUpd #############\n2016-03-23 09:45:59:456 4800 11d4 AgntUpd FATAL: Agent sync failed, error = 0x80070005\n2016-03-23 09:45:59:456 4800 11d4 Agent Agent servicing time window policy is not set\n2016-03-23 09:45:59:456 4800 11d4 Agent WARNING: Unable to read agent servicing time window policy, error = 0x80070002.\n2016-03-23 09:45:59:456 4800 11d4 AgntUpd WARNING: Failed to update task triggers, error = 0x80070002\n2016-03-23 09:45:59:456 4800 11d4 Agent WARNING: WU client fails to call back to search call {5D632D8E-3C20-4F2F-B2EB-BB67C0CBB349} with error 0x80070005\n2016-03-23 09:46:04:457 4800 128c Report REPORT EVENT: {5FE0E6F6-2B5B-4C97-932F-4CF88332C01D} 2016-03-23 09:45:59:456+0100 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80070005 Client Agents Sync Failure Software Synchronization The Client failed to detect with error 0x80070005.\n\n<\/pre>\n","protected":false},"excerpt":{"rendered":"<p>If you want to deploy the Intune Client using a (golden\/generalized) image with System Center Configuration Manager or any other tool, make sure you haven&#8217;t already installed the Intune Client\u00a0on that machine and follow the correct procedure. The Intune Client generates a machine specific certificate in the Personal Store of the machine. This certificate is &hellip; <a href=\"https:\/\/lieben.nu\/liebensraum\/2016\/03\/intune-client-does-not-appear-in-console-and-displays-error-0x80070005-when-updating\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Intune Client does not appear in console and displays error 0x80070005 when updating<\/span> <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_crdt_document":"","footnotes":""},"categories":[22],"tags":[],"class_list":["post-658","post","type-post","status-publish","format-standard","hentry","category-intune"],"_links":{"self":[{"href":"https:\/\/lieben.nu\/liebensraum\/wp-json\/wp\/v2\/posts\/658","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lieben.nu\/liebensraum\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lieben.nu\/liebensraum\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lieben.nu\/liebensraum\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lieben.nu\/liebensraum\/wp-json\/wp\/v2\/comments?post=658"}],"version-history":[{"count":0,"href":"https:\/\/lieben.nu\/liebensraum\/wp-json\/wp\/v2\/posts\/658\/revisions"}],"wp:attachment":[{"href":"https:\/\/lieben.nu\/liebensraum\/wp-json\/wp\/v2\/media?parent=658"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lieben.nu\/liebensraum\/wp-json\/wp\/v2\/categories?post=658"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lieben.nu\/liebensraum\/wp-json\/wp\/v2\/tags?post=658"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}