{"id":2207,"date":"2021-09-04T15:08:24","date_gmt":"2021-09-04T20:08:24","guid":{"rendered":"https:\/\/www.ciraltos.com\/?p=2207"},"modified":"2023-03-23T05:49:18","modified_gmt":"2023-03-23T10:49:18","slug":"hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found","status":"publish","type":"post","link":"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/","title":{"rendered":"Hybrid Azure AD Join: The device object by the given ID is not found"},"content":{"rendered":"\n<figure class=\"wp-block-image alignleft size-large\"><img decoding=\"async\" loading=\"lazy\" width=\"143\" height=\"147\" src=\"https:\/\/www.ciraltos.com\/wp-content\/uploads\/2021\/09\/Azure-AD-Connect.png\" alt=\"\" class=\"wp-image-2208\"\/><\/figure>\n\n\n\n<p class=\"has-text-align-left\">I worked on an Azure Active Directory lab for Hybrid Azure AD Join today and ran into a problem.&nbsp; The lab is a new deployment, single Windows Server 2019 Domain Controller running the 2.x version of Azure AD Connect Sync.&nbsp; Express install was used, there are no OU or advanced filters in place.&nbsp; Following the directions outlined in the Microsoft documentation is straightforward.&nbsp; However, after enabling Hybrid Azure AD Join, the computers did not show in the Azure AD Portal under Devices.<\/p>\n\n\n\n<!--more-->\n\n\n\n<p>Digging through the event log and using dsregcmd \/status on the client provided the error:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">Automatic registration failed at join phase. <br>Exit code: Unknown HResult Error code: 0x801c03f3 <br>Server error: The device object by the given id (xxxxxx-xxxx-xxxx-xxxx-xxxxxxxx) is not found<\/pre>\n\n\n\n<p>The most common cause for this is a filter in AD Connect that\nexcludes OU\u2019s or computers.&nbsp; Computer devices\nneed to be included in any filter, or they will not synchronize to Azure AD.&nbsp; Azure AD Connect Sync was configured with an\nexpress installation with no filters were in place.<\/p>\n\n\n\n<p>I went to the AD Connect Synchronization Services Manager to review the settings.&nbsp; In the Active Directory Domain Services connector, under Selected Object Types, I noticed that \u201cdevice\u201d was unchecked.&nbsp; I checked this box and then initiating a synchronization (start-adsyncsynccycle).<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/www.ciraltos.com\/wp-content\/uploads\/2021\/09\/Synchronization-Service-Manager-1.png\" alt=\"Synchronization Service Manager\" class=\"wp-image-2210\"\/><figcaption class=\"wp-element-caption\">Synchronization Service Manager<\/figcaption><\/figure>\n\n\n\n<p>Once the sync finished, the devices showed in the Azure AD\nPortal with the status of Pending.&nbsp; A\nreboot of the client moved the device to a registered state and allowed the\ndevice to be Hybrid Azure AD Joined.<\/p>\n\n\n\n<p>I am curious why I had to check the device box.&nbsp; Azure AD Connect had a default installation\nwith express settings.&nbsp; If that step was\nrequired, the agent could have handled it when Hybrid Azure AD join was\nconfigured.&nbsp; I could not find any\ninformation on why checking \u201cdevice\u201d was needed when \u201ccomputer\u201d was already\nchecked.<\/p>\n\n\n\n<p>If you found this article you may be suffering the same\nissue.&nbsp; I hope this helps!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I worked on an Azure Active Directory lab for Hybrid Azure AD Join today and ran into a problem.&nbsp; The lab is a new deployment, single Windows Server 2019 Domain Controller running the 2.x version of Azure AD Connect Sync.&nbsp; Express install was used, there are no OU or advanced filters in place.&nbsp; Following the &hellip;<\/p>\n<p class=\"read-more\"> <a class=\"\" href=\"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/\"> <span class=\"screen-reader-text\">Hybrid Azure AD Join: The device object by the given ID is not found<\/span> Read More &raquo;<\/a><\/p>\n","protected":false},"author":1,"featured_media":2208,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"default","ast-global-header-display":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":""},"categories":[2,1021],"tags":[142,1010,1088],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v20.3 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Hybrid Azure AD Join: The device object by the given ID is not found - ciraltos<\/title>\n<meta name=\"description\" content=\"I worked on an Azure Active Directory lab for Hybrid Azure AD Join today and ran into a problem. After enabling Hybrid Azure AD Join, the computers did not show in the Azure AD Portal under Devices. 0x801c03f3\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Hybrid Azure AD Join: The device object by the given ID is not found - ciraltos\" \/>\n<meta property=\"og:description\" content=\"I worked on an Azure Active Directory lab for Hybrid Azure AD Join today and ran into a problem. After enabling Hybrid Azure AD Join, the computers did not show in the Azure AD Portal under Devices. 0x801c03f3\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/\" \/>\n<meta property=\"og:site_name\" content=\"ciraltos\" \/>\n<meta property=\"article:published_time\" content=\"2021-09-04T20:08:24+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-03-23T10:49:18+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.ciraltos.com\/staging2\/wp-content\/uploads\/2021\/09\/Azure-AD-Connect.png\" \/>\n\t<meta property=\"og:image:width\" content=\"143\" \/>\n\t<meta property=\"og:image:height\" content=\"147\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Travis Roberts\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@ciraltos\" \/>\n<meta name=\"twitter:site\" content=\"@ciraltos\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Travis Roberts\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"2 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/\"},\"author\":{\"name\":\"Travis Roberts\",\"@id\":\"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/25391996d6cddfecd4d257162b7e373a\"},\"headline\":\"Hybrid Azure AD Join: The device object by the given ID is not found\",\"datePublished\":\"2021-09-04T20:08:24+00:00\",\"dateModified\":\"2023-03-23T10:49:18+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/\"},\"wordCount\":328,\"commentCount\":4,\"publisher\":{\"@id\":\"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/25391996d6cddfecd4d257162b7e373a\"},\"keywords\":[\"Azure AD\",\"Azure AD Connect\",\"Hybrid Azure AD Join\"],\"articleSection\":[\"Azure\",\"Azure AD\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/\",\"url\":\"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/\",\"name\":\"Hybrid Azure AD Join: The device object by the given ID is not found - ciraltos\",\"isPartOf\":{\"@id\":\"http:\/\/www.ciraltos.com\/staging2\/#website\"},\"datePublished\":\"2021-09-04T20:08:24+00:00\",\"dateModified\":\"2023-03-23T10:49:18+00:00\",\"description\":\"I worked on an Azure Active Directory lab for Hybrid Azure AD Join today and ran into a problem. After enabling Hybrid Azure AD Join, the computers did not show in the Azure AD Portal under Devices. 0x801c03f3\",\"breadcrumb\":{\"@id\":\"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"http:\/\/www.ciraltos.com\/staging2\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Hybrid Azure AD Join: The device object by the given ID is not found\"}]},{\"@type\":\"WebSite\",\"@id\":\"http:\/\/www.ciraltos.com\/staging2\/#website\",\"url\":\"http:\/\/www.ciraltos.com\/staging2\/\",\"name\":\"ciraltos\",\"description\":\"cloud, technology and trends\",\"publisher\":{\"@id\":\"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/25391996d6cddfecd4d257162b7e373a\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"http:\/\/www.ciraltos.com\/staging2\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/25391996d6cddfecd4d257162b7e373a\",\"name\":\"Travis Roberts\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/www.ciraltos.com\/staging2\/wp-content\/uploads\/2023\/03\/Logo-1.png\",\"contentUrl\":\"https:\/\/www.ciraltos.com\/staging2\/wp-content\/uploads\/2023\/03\/Logo-1.png\",\"width\":5657,\"height\":3563,\"caption\":\"Travis Roberts\"},\"logo\":{\"@id\":\"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/image\/\"},\"sameAs\":[\"http:\/\/www.ciraltos.com\",\"https:\/\/twitter.com\/ciraltos\"],\"url\":\"https:\/\/www.ciraltos.com\/staging2\/author\/admin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Hybrid Azure AD Join: The device object by the given ID is not found - ciraltos","description":"I worked on an Azure Active Directory lab for Hybrid Azure AD Join today and ran into a problem. After enabling Hybrid Azure AD Join, the computers did not show in the Azure AD Portal under Devices. 0x801c03f3","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:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/","og_locale":"en_US","og_type":"article","og_title":"Hybrid Azure AD Join: The device object by the given ID is not found - ciraltos","og_description":"I worked on an Azure Active Directory lab for Hybrid Azure AD Join today and ran into a problem. After enabling Hybrid Azure AD Join, the computers did not show in the Azure AD Portal under Devices. 0x801c03f3","og_url":"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/","og_site_name":"ciraltos","article_published_time":"2021-09-04T20:08:24+00:00","article_modified_time":"2023-03-23T10:49:18+00:00","og_image":[{"width":143,"height":147,"url":"https:\/\/www.ciraltos.com\/staging2\/wp-content\/uploads\/2021\/09\/Azure-AD-Connect.png","type":"image\/png"}],"author":"Travis Roberts","twitter_card":"summary_large_image","twitter_creator":"@ciraltos","twitter_site":"@ciraltos","twitter_misc":{"Written by":"Travis Roberts","Est. reading time":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/#article","isPartOf":{"@id":"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/"},"author":{"name":"Travis Roberts","@id":"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/25391996d6cddfecd4d257162b7e373a"},"headline":"Hybrid Azure AD Join: The device object by the given ID is not found","datePublished":"2021-09-04T20:08:24+00:00","dateModified":"2023-03-23T10:49:18+00:00","mainEntityOfPage":{"@id":"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/"},"wordCount":328,"commentCount":4,"publisher":{"@id":"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/25391996d6cddfecd4d257162b7e373a"},"keywords":["Azure AD","Azure AD Connect","Hybrid Azure AD Join"],"articleSection":["Azure","Azure AD"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/","url":"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/","name":"Hybrid Azure AD Join: The device object by the given ID is not found - ciraltos","isPartOf":{"@id":"http:\/\/www.ciraltos.com\/staging2\/#website"},"datePublished":"2021-09-04T20:08:24+00:00","dateModified":"2023-03-23T10:49:18+00:00","description":"I worked on an Azure Active Directory lab for Hybrid Azure AD Join today and ran into a problem. After enabling Hybrid Azure AD Join, the computers did not show in the Azure AD Portal under Devices. 0x801c03f3","breadcrumb":{"@id":"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.ciraltos.com\/staging2\/hybrid-azure-ad-join-the-device-object-by-the-given-id-is-not-found\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"http:\/\/www.ciraltos.com\/staging2\/"},{"@type":"ListItem","position":2,"name":"Hybrid Azure AD Join: The device object by the given ID is not found"}]},{"@type":"WebSite","@id":"http:\/\/www.ciraltos.com\/staging2\/#website","url":"http:\/\/www.ciraltos.com\/staging2\/","name":"ciraltos","description":"cloud, technology and trends","publisher":{"@id":"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/25391996d6cddfecd4d257162b7e373a"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"http:\/\/www.ciraltos.com\/staging2\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/25391996d6cddfecd4d257162b7e373a","name":"Travis Roberts","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/image\/","url":"https:\/\/www.ciraltos.com\/staging2\/wp-content\/uploads\/2023\/03\/Logo-1.png","contentUrl":"https:\/\/www.ciraltos.com\/staging2\/wp-content\/uploads\/2023\/03\/Logo-1.png","width":5657,"height":3563,"caption":"Travis Roberts"},"logo":{"@id":"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/image\/"},"sameAs":["http:\/\/www.ciraltos.com","https:\/\/twitter.com\/ciraltos"],"url":"https:\/\/www.ciraltos.com\/staging2\/author\/admin\/"}]}},"_links":{"self":[{"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/posts\/2207"}],"collection":[{"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/comments?post=2207"}],"version-history":[{"count":2,"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/posts\/2207\/revisions"}],"predecessor-version":[{"id":3807,"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/posts\/2207\/revisions\/3807"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/media\/2208"}],"wp:attachment":[{"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/media?parent=2207"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/categories?post=2207"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/tags?post=2207"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}