Often a simple and effective solution seen by the customer requires lots of work 'under the hood' - this is where my skill set puts me.I have been using Windows since the very first version that 4 icons on the screen and a mouse pointer you could see from 200mtrs away. Software Engineer | Microsoft MVP - Enterprise Mobility | Microsoft Certified Trainer | Microsoft 365 Certified: Enterprise Administrator Expert | Blogger/Speaker | Contributor | driven and passionate Technical Architect with 20 years experience in driving adoption and technology change within the Enterprise. The real challenge is understanding where your legacy policies were deployed from and drawing up a plan on how you will manage components with Intune.Īs with the OfficeComMgmt post above, there are many ways to remediate registry values – I personally am a big fan of Endpoint Analytics Proactive Remediations. Monitor the IntuneManagementExtension.log in C:\ProgramData\Microsoft\IntuneManagementExtension\Logs SummaryĪs we observed previously with Office Updates careful planning must be taken when moving workloads to Intune. Wait for (or force) a Policy Sync on your clientsġ1. You can adjust the Schedule if you want the remediation check to occur more or less than Once Daily.ġ0. Assign the Custom Script to your Co-Management Pilot Group for Windows Updates or another applicable Group (Remember: Proactive Remediations will only work for co-management clients that also have the workload for Client Apps moved to Intune). In the Detection Script box, copy and paste in your PowerShell code for the detection logic and in the Remediation Script box copy and paste in your code for the remediation scriptĨ. Enter a Name Enable Microsoft Edge Automatic UpdatesĦ. Under Reports, click Proactive remediationsĤ. Visit > Reports > Endpoint Analytics (Preview)Ģ. HKLM:\SOFTWARE\Policies\Microsoft\EdgeUpdate\Updateġ. When we create our remediation script, we are going to need to make a consideration that the following registry key could be any of the above Update Channels. There are 4 to choose from and they each have their respective GUID:. When we deploy Edge, we specify which Build or Update Channel we are going to deploy. The challenge we have is Update Channels. Once enabled, Microsoft Edge will periodically check-in to see if there any updates and apply them. We can change the value from 0 to 1 to re-enable automatic updates – it is as simple as that. In effect, the registry value that disables updates was “tattooed” to the registry during Edge installation. You are enabling the clients to receive apps from ConfigMgr and Intune simultaneously. It is safe to assume that the Client App co-management workload is often the first workload moved to Intune because you are not actually “moving” workloads per se. Proactive Remediation requires the Client Apps workload to be moved to Intune or Pilot for your devices. It is a feature still in Preview and it allows you to monitor and remediate clients if certain conditions are found. I have been using Proactive Remediations a lot recently. Endpoint Analytics Proactive Remediations You can create a Configuration Profile to Enable automatic updates in Microsoft Edge – but you may not have the co-management workload for Device Configuration moved to Intune yet – in which case this policy would not apply to your co-managed devices. There is not an option in the Windows 10 Update Ring policy in Intune to Enable automatic updates in Microsoft Edge You have already migrated your Windows Update workload to Intune for some of your devices but have found out that Microsoft Edge wasn’t updating. I guess you are reading this because the horse has already bolted.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |