Windows 10 Report Feature Update failures

%3CLINGO-SUB%20id%3D%22lingo-sub-2698329%22%20slang%3D%22en-US%22%3EWindows%2010%20Report%20Feature%20Update%20failures%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2698329%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20work%20in%20a%20co-managed%20enviroment%20where%20we%20have%20switched%20WUFB%20workload%20to%20Intune.%3C%2FP%3E%3CP%3EThe%20feature%20updates%20are%20working%20well%20but%20the%20reporting%20does%20not.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%2070%25%20errors%20in%20the%20Windows%2010%20and%20later%20feature%20update%20report%2C%20all%20failures%20are%3A%3CBR%20%2F%3E%3CSPAN%3E%22Device%20Registration%20Invalid%20Azure%20AD%20Device%20Id%22.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ENow%2C%20the%20devices%20are%20Hybrid-AzureAD%20Joined%20and%20as%20mentioned%20Co-Managed%20with%20WUFB%20as%20Intune-managed%20workload.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EFor%20what%20it's%20worth%2C%20I%20can%20see%20the%20Azure%20Device%20ID%20present%20in%20AzureAD.%3CBR%20%2F%3EAnyone%20have%20any%20suggestions%20regarding%20how%20to%20solve%20this%20so%20we%20get%20that%20fancy%20piechart-report%20working%3F%20%3A)%3C%2Fimg%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2698329%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ereports%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUpdate%20Compliance%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Update%20for%20Business%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ewufb%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2699231%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20Report%20Feature%20Update%20failures%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2699231%22%20slang%3D%22en-US%22%3EDo%20you%20also%20have%20duplicate%20objects%20that%20are%20Azure%20AD%20Registered%20for%20those%20machines%3F%20That%20could%20be%20your%20problem...%3C%2FLINGO-BODY%3E
Visitor

Hi

 

I work in a co-managed enviroment where we have switched WUFB workload to Intune.

The feature updates are working well but the reporting does not.

 

We have 70% errors in the Windows 10 and later feature update report, all failures are:
"Device Registration Invalid Azure AD Device Id".

 

Now, the devices are Hybrid-AzureAD Joined and as mentioned Co-Managed with WUFB as Intune-managed workload.

 

For what it's worth, I can see the Azure Device ID present in AzureAD.
Anyone have any suggestions regarding how to solve this so we get that fancy piechart-report working? :)

1 Reply
Do you also have duplicate objects that are Azure AD Registered for those machines? That could be your problem...