Co-managed Device not receiving windows update from Intune (Feture and Quality)
Hi All, We have configured co-management for Windows Update. The device is showing co-managed and workload moved to Intune. However, the device is still not receiving the Windows update. Below is the current configuration and status: Disable Dual Scan value set to "0". Windows update registry for quality, feature and other updates set to "0". Device is getting synced to Intune, and status is showing co-managed. Update ring and feature update policy applied, and the respective registry value is showing there. showing "not yet scanned" on Windows update report.
Best way to redo a corrupted login | Intune
I work for an actively growing engineering firm and our domain is hybrid on-prem + AAD with a semi-recent rollout of Intune (so we are a little green with how it works) One of my user's computer login is showing signs of corruption so we wanted to backup and remove the profile from the machine without disrupting Intune enrollment or reinstalling Windows (which we will only do as a last resort with this user.) Pre-MDM, removing was fairly easy from a service account which literally renaming that user folder in the Users folder then removing the user from Advanced System Settings. Then having the user sign back in which would rebuild a new, clean user profile. But now, Intune is protecting the profile (as it was used to enroll in Intune) making this old process impossible. Even with network adapters disabled or in Safe Mode. Is there a way to do re-do a corrupted user profile without removing the computer from the domain? The delete option in Intune will remove a computer, but I noticed that re-enrolling in Intune with another account typically doesn't work in our tenant. So, I am trying to avoid using the Delete option in Intune. A little guidance as we are new to Intune.iOS DEP enrolled devices missing Enrollment Profile (breaking dynamic group and filter logic)
Starting 31/05/2022 new iOS enrollments via Apple Business Manager Device Enrollment do not have an Enrollment Profile attribute assigned under Hardware, generally we use this attribute to define dynamic groups/filters. I have seen this on at least two different customer tenants so far. Example of a filter no longer matching a device enrollment. (previous enrollments still show the correct Enrollment Profile Note: Testing 3 tenants we only see two in APAC impacted so far. Asia Pacific 0101 Asia Pacific 0201
