Dwigt

Thanks Wise, I'll give that a go this morning and see if it still works. I'll update the thread with my findings

Yeah, that's what I've been doing... it's such a pita! It seems so obviously necessary that Configurator should download the latest compatible version of an app for whichever device is connected. Apple have really disappointed me with their lack of effort in this area. edit: sorry, thanks for responding

Hi Combo Did you ever find a solution to this? ta

Here you go: https://wpsites.net/web-design/changing-background-color-specific-page-post/ Plenty of methods to choose from here

Apologies for necro'ing the thread, but I wanted to say thanks for posting this. I've just found a grabbed a copy today as I've been searching for something just like this. Much appreciated

So, I went digging through the support pages and found out that our organisation type was set to 'Higher Education', not 'Primary/Secondary Education', when it was created. G-Suite support said that changing it should result in the SMS login challenge going away. So, fingers crossed, that should be that! thanks for your help

I don't have any options in the login challenge section of the admin console: Is yours different?

Our G-Suite users and passwords are synced from our school email (atomwide) so the students can't recover their own password, for the same reason as you. I'm not sure why they're required to enter a phone number to pass the login challenge. A captcha sure would be much less hassle!

Thanks. We actually have that turned off already. The main issue with the login challenge is when students who don't have phones encounter it. The only solution I've found is to enable the 10 minute window for them as it happens. This is far from ideal. The only thing I can think of trying is to put some info in to their Employee ID field and enable that as a response for the login challenge. The tricky bit is coming up something they'll remember. If they're already forgetting their password, giving them something else to memorise isn't ideal.

We are getting login challenges every day for our students. I have contacted Google and they have been no help. I'd say we average 10 a day, sometimes a lot more. Any luck working out what's triggering them for you?

Wow, I wasn't sure I'd get a response to a year old post ever, let alone a few minutes later! That's amazing and I really appreciate it Thanks for the tip. When I launched processmon and it logged 250000 events in the few seconds before I'd even opened Office, I thought it might not be the easiest solution! Luckily you can highlight keywords and then jump between them directly. thanks again and have a nice day

Apologies for necroposting but I was wondering how you knew about this registry key? Searching for "IsRemindWelcome" returns a single result, which is this thread. thanks edit: Tried to solve it myself. I used process monitor to watch for every registry check that was performed when Office launched and spotted it checking for IsRemindWelcome. Is that how you knew about it?

I'm testing a self-hosted MRBS installation at the moment. The interface is pretty awful but as it's just php, I'm rejigging a lot of it. It was really easy to get running and was better than writing one completely from scratch! https://mrbs.sourceforge.io/

voted surprised this wasn't already in

Initially, it wasn't working at all. Re-read the thread and installed KB2506143 to put WMF3.0 on the machine. After that, it ran but produced those two error messages first. Since then, I downloaded the latest version of ps2exe and remade the RunFS.exe using your ps1 file: #Requires -Version 3.0$FS = Get-ChildItem -Path "${env:ProgramFiles}\Google\Drive File Stream" -Directory | Where-Object { $_.Name -match '\d+\.\d+\.\d+\.\d+' } | Sort-Object -Property { [Version]$_.Name } | Select-Object -Last 1 -ExpandProperty FullNameStart-Process -FilePath ('{0}\{1}' -f $FS,'GoogleDriveFS.exe') Now, when I run the .exe as a standard user the console window opens, displays the two error messages, quickly closes and then File Stream is run/the folder is opened. So, really, it's not terrible. It doesn't prevent anyone using it as intended and they aren't required to deal with any confusing error prompts. If I can work out what's causing the errors though, it would scratch that all-too-familiar itch.