Google Earth on Chrome - ERR_BLOCKED_BY_ADMINISTRATOR

[Norphy]

I've had an issue raised by one of my schools, where a kid has wanted to access Google Earth using Chrome. It had been working up until recently, but now they're getting a picture of a dinosaur and an error that says "ERR_BLOCKED_BY_ADMINISTRATOR".

 

We are controlling Chrome via GPO, but we haven't changed our policy so I can only assume that a recent update to Chrome has done this. They can access it in Edge but we haven't set any GPOs to speak of on that. Looking at the Chrome GPO, there's nothing that obviously shouts "BLOCK GOOGLE EARTH SUCKA!". This is our GPO.

 

 

Any suggestions?

[mavhc]

First guess is Safe Sites

[free780]

Are they using RDS or similar?

[Norphy]

No, standard desktop

[DaveTheTech]

Does going to chrome://policy give any useful information?

[rtj_20]

Same situation, fixed it by changing these GPO settings:

 

Allow access to a list of URLs: Enabled and allowed earth.google.com

"Safe Browsing settings" > Configure the list of domains on which Safe Browsing will not trigger warnings: Enabled and added earth.google.com

 

I also have SafeSites and Safe Browsing enabled, so it might specifically be one of those, but doing both of these resolved the issue for us.

[mavhc]

Well, earth is where all the terrorists live, so not suitable for children.

[NetworkSeb]

We had the same issue on Chromebooks.

Had to add 'earth.google.com' to 'URL Blocking' - 'Blocked URL exceptions' in the Google Admin Console (User & Browser Settings).

[Norphy]

A few months down the line, this has started happening with attachments in Outlook on the Web. Disabling SafeSites gets around the problem but putting attachments.office.net into the exceptions list makes no difference.

 

Very annoying.

[lyndonw]

A few months down the line, this has started happening with attachments in Outlook on the Web. Disabling SafeSites gets around the problem but putting attachments.office.net into the exceptions list makes no difference.

 

Very annoying.

 

We've just had an influx of users reporting the same issue with attachments in Chrome! I don't really want to disable SafeSites for obvious reasons and am awaiting a refresh to see if putting attachments.office.net into the exceptions list works, but now I'm not holding out much help.

 

Works fine with Edge, but don't want to just tell users to swap browsers as that opens a whole other can of worms with our userbase.

 

All other ideas very welcome...

[lyndonw]

Should anyone else be having this issue which is not resolved by disabling SafeSites, out ADMX & ADML files on our domain controllers were quite dated. Updating these and migrating depreciated policies solved this problem for us.