If you are managing windows devices using SCCM, you know the level of control it offers for the reboot experience through the client settings and the timely notification of impending reboots. SCCM excels at ensuring users are well-informed about scheduled tasks, with toast notifications that are hard to miss. However, when transitioning your Windows patching tasks to Intune (windows update for business) or adopting Intune for device management, you may notice a difference in the reboot experience. The controls for end-user experience are limited (especially the remainders). In this blog post, we will explore options and settings that can help…
Author: Eswar Koneti
Blog post updated on 23 Oct, 2023 Problem: Few weeks ago ,colleague of mine was trying to perform patch management on bulk number of clients (servers) as monthly patching ,as part of it he made sure the maintenance window was in place, deployment was set rightly for software updates deployment. Maintenance window started ,patches started installing and after a while ,he logged in ( browse the reports ) to check the status for deployed patches (software update groups) using reports. He found that, 30-40% was compliant and rest of them non-compliant (majority) /unknown (very few) . By the time ,he…
Troubleshooting Co-Management wufb Workloads and the WMI StateMsg Namespace #SCCM #Intune #wufb
Co-management (cloud attach) enables you to manage Windows 10 or later devices simultaneously by using both Configuration Manager and Microsoft Intune. For more information about co-management, please refer here. For a device to be co-managed, one of the pre-requisite is Windows devices must be connected to Azure AD using Hybrid Azure AD joined or Azure AD joined (cloud domain joined). Currently, co-management supports the following workloads. Co-management supports the following workloads: Compliance policies Windows Update policies Resource access policies Endpoint Protection Device configuration Office Click-to-Run apps Client apps Let’s assume, you have enabled the cloud attach (co-management) and you have…
Using KQL – Creating Custom Workbooks to Distinguish intune wufb Managed from Unmanaged Devices
Using Intune remediation – check the windows license activation is subscription or KMS based #EMS #Intune #Remediation #scripts
Wufb (windows update for business) is feature in Microsoft Intune that allows organizations to manage and control the deployment of Windows updates across their devices. With WUfB, Intune administrators can define update ring policies and settings to ensure that devices within their organization receive the necessary updates in a controlled manner. This helps organizations maintain security and compliance by ensuring that devices are up to date with the latest patches and fixes. For more information about wufb deployments, please refer https://learn.microsoft.com/en-us/mem/intune/protect/windows-update-for-business-configure After you create the wufb ring policies and deployed, devices will receive the settings and start reporting to wufb…
Introduction: In Intune world of device management, the concept of the primary user plays a crucial role, especially when it comes to application deployments. In this blog post, we will explore the significance of the primary user and how it affects the installation of applications using the company portal in Intune. We will also discuss a practical scenario and share scripts that can help you manage and correct primary user assignments efficiently. The Definition of Primary User: According to Microsoft’s article , https://learn.microsoft.com/en-us/mem/intune/remote-actions/find-primary-user#what-is-the-primary-user The primary user property is used to map a licensed Intune user to their devices in:…