Weird issues with chrome this week

[Sheridan]

We're seeing some odd behavior in Chrome browser this week - on chromebooks and windows desktops. They're version 91 so pretty up to date

 

Example 1: On a Windows desktop, in Chrome the credit card payments page doesn't work - it just keeps saying 'please try again'. This lead us to think it was a website issue, however it worked ok in Edge. The odd part is that the page rendered differently in the two browsers i.e the expiry date in Chrome showed as two fields (2 digits for Expiry Month and 4 digits for Expiry Year) as compared to Edge which showed this as one single field called Expiry Date (2/4 digits)

 

Example 2: A load of kids running a test login to Chromebooks - half of them then cannot login to the site as it says they login details didn't work (100% checked and correct!) The same kids login to a Windows desktop and use the same site and credentials and it worked absolutely fine!

 

This seems to be like the Chrome browser itself is the issue, rather than any filtering issues (chromebooks and desktops use the same filtering proxy & port)

 

Apart from telling people to use Edge I'm not sure what else I can do - as we have a very light set of policies applied to Chrome on Windows and even less on the chromebooks themselves!

[Oaktech]

Just humour me have a check and make sure you don't have conflicting policies set up between GPO and Chrome Management and between OUs in GWorkspace. We've been seeing features that should be turned on stop working and vice versa because one set of mangement is taking precedence over another with unpredictable results. Specifically we've seen the password manager cease to function because suddenly it's become disabled in cloud management and enabled in GPO, Payments stop working because the save payment details popup is disabled in GPO and enabled in Cloud Management and chromebooks have issues with wifi because the certificates for wifi and filtering were in a higher OU than the devices and inheritance doesn't appear to be trickling down like you'd expect.

[Sheridan]

Just humour me have a check and make sure you don't have conflicting policies set up between GPO and Chrome Management and between OUs in GWorkspace. We've been seeing features that should be turned on stop working and vice versa because one set of mangement is taking precedence over another with unpredictable results. Specifically we've seen the password manager cease to function because suddenly it's become disabled in cloud management and enabled in GPO, Payments stop working because the save payment details popup is disabled in GPO and enabled in Cloud Management and chromebooks have issues with wifi because the certificates for wifi and filtering were in a higher OU than the devices and inheritance doesn't appear to be trickling down like you'd expect.

 

We've only ever had Chrome settings in one policy - never mixed with others. One for staff and one for students (different proxy settings basically) and the chromebooks have their own settings. We don't have Chrome browser in Google workspace as the GPOs are in place.

 

Its odd as we've now had another example - a users searches for something on a diy store site, and gets an error saying 'something went wrong' - do exactly the same thing on Edge and it works fine (this is on Windows 10)

[Oaktech]

I've got a ticket in with Workspace so I'm interested to see what they come back with. I'll share just in case in there is a tidbit that applies to you.

[Sheridan]

I've got a ticket in with Workspace so I'm interested to see what they come back with. I'll share just in case in there is a tidbit that applies to you.

 

Cheers - its only happened this week (afaik) so maybe related to the last update perhaps