Jump to content

Recommended Posts

Posted

Yup received this earlier, have configured Edge Rollback in InTune to revert to the last version of Edge 129

 

Policy (Device)

Always allow updates (recommended)

------------------------------------------------------------------------

Rollback to Target version

Enabled

Target version override

Enabled

Target version (Device)

129.0.2792.89

Update policy override

Enabled

Posted (edited)
For those who may not be aware, an issue has been identified with the Cloud Filter in Edge 130. Seems like something Microsoft have broke! Smoothwall have published a KB about it: Cloud Filter issues with Microsoft Edge v130+ – Help Centre

Thank you for posting this. As mentioned, there is an issue with Edge 130. The engineers at Smoothwall are working hard to mitigate the problem while we wait for more information from Microsoft. We encourage anyone experiencing issues to review the KB article regarding this issue, and we will continue to post any new updates directly to the KB as they become available. Cloud Filter issues with Microsoft Edge v130+ – Help Centre

Edited by matt_shakespeare
Posted
Just implementing the same, just testing to make sure the settings can actually be rolled back again from Intune, rather than the usual Enabled and Not Configured, which obviously wouldn't remove the setting from endpoints at a latter date.
Posted

Rolled my clients back to 129 yesterday via GPO. Works fine now.

 

Thanks for sending out the customer emails as we'd started to get reports of weird filtering on CPOMS (When it shouldn't be blocking) & would have taken us longer to spot without the notifications so thanks.

Posted
I've gone back to 129.something and my Cloud Filter isn't loading at all now. The extension gives a Provisioning Failed message.

 

Have you got a support ticket logged for this? If you have please can you send me the ticket number and I'll look into the status of this for you.

Posted
Latest update - Microsoft Edge stable v130.0.2849.56 is starting to be rolled out. This contains a fix to this issue. Confirmation can be found here. We have done some testing with this and can confirm the extension is now working correctly on this version.
  • Thanks 2
Posted
Have you got a support ticket logged for this? If you have please can you send me the ticket number and I'll look into the status of this for you.

 

I hadn't logged it yesterday so only did it this morning. Ticket number is 556123

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...