jthompson

This is why I'm always wary of anyone enthusiatically adopting some third-party web app that they've found. In this case, it's not exactly third-party, but if it's anywhere outside the core Workspace apps, then I'm wary. On the other hand, Google did just announce that Chromebooks now get 10 years of update support, which is pretty good tbf.

GAM command to clear out any internal addresses from users' Other Contacts, to avoid them appearing as conflicting recipient suggestions in Gmail. This example will clear out any "@myschool.org" addresses from the Other Contacts list of all users in or under the OU "Staff". gam ou_and_children_ns /Staff delete othercontacts emailmatchpattern ".*@myschool.org" Might be particular to gamadv-xtd3.

I'm not sure that harsh, reactionary punishment is conducive to understanding why people do shocking things. In fact, it might often be the cause. I expect the cat bin lady is breathing a sigh of relief that her time as the goto public enemy number 1 could be coming to an end.

At least it's happening nice and early in the academic year. It makes it easier to get the service turned off asap without having to wait until courses are finished.

Je suis sycamore tree.

The original non-Ultramarines chapters still have their own Index and therefore a unique detachment, but most of the others are homogenised by the looks of it, albeit with GW wanting to put plenty of flexibility in the SM Codex to allow for suitably expressive choices. I suppose it means that if your opponent is playing SM, you're less in the dark about whatever obscure rules they're throwing at you.

Google Vault is the tool to use. It's its own app, not a part of the Admin console.

Sounds like good material for an AppSheet app! At least, that's what I had fun with over the summer. You can then use AppSheet to add automations such as emial notifications for newly added records, etc.

If it's a busy Sheets file with lots of editing going on, it might run into some Apps Script quota issues since this trigger would be going off a lot.

Have a look at /forums/cloud-services/224024-google-gmail-allowing-teachers-send-year-group-distribution-lists.html. If you have your students and staff separated in the OU structure, you can use a Gmail content compliance rule.

This also works. Add an "On Edit" trigger. The function will check the event to determine which cell in which sheet was edited, and fire an email only when cell D4 in the sheet 'valuetest' is edited to a value of 5. function checkValue(event){ if ((event.source.getSheetName() == 'valuetest') && (event.range.getColumn() == 4) && (event.range.getRow() == 4)) { // Cell D4 in sheet 'valuetest' was edited. Logger.log("Target cell was edited"); var valueToCheck = event.range.getValue(); if(valueToCheck == 5) { Logger.log("Email should be sent."); MailApp.sendEmail("[email protected]", "Test", "This is a test: " + valueToCheck + "."); } else { Logger.log("Email will not be sent."); } } else { Logger.log("Target cell was NOT edited"); } }

That works for me when running directly in the editor. Try this (obvisouly with a functioning email recipient to test with). function checkValue(){ var ss = SpreadsheetApp.getActive(); var sheet = ss.getSheetByName('valuetest'); var valueToCheck = sheet.getRange('D4').getValue() ; Logger.log(valueToCheck); if(valueToCheck == 5) { MailApp.sendEmail("[email protected]", "subject", "context" + valueToCheck+ "."); Logger.log("Email should be sent."); } else { Logger.log("Email will not be sent."); } } The Logger output should indicate whether the value you're looking to test is actually being read in, and which way the if statement is then going.

When Apps Script sends an email, it does so as the user for whom the trigger was set (or as the user running the function directly in the editor). The first time it does that it needs to prompt for approval. Are you using a time-based trigger?

Going back a few years now but when I did it I used the equivalent of GWMME - https://support.google.com/a/topic/9064794?hl=en&ref_topic=13002773&fl=1&sjid=17358763373322878011-NA. I did migrations in phases (i.e. between sets of dates) rather than in one big go. Maybe do the last year first, and then back fill with progressively older items. The biggest tangles I had to sort out though were down the the folder -> label conversion. Gmail didn't (doesn't?) like it when a mailbox has too many hundreds of labels.

No SSO means it's much easier to be deployed as shadow IT, didn't you know?

See this other thread for more details regarding retirement of v1. /forums/cloud-services/227921-upgrade-azure-ad-connect-before-september-2022-a.html Have to admit that seeing that advisory in the AAD/Entra overview page hasgiven me a start more than a few times, before I remember that it's just about v1.

Similar here. We use Gmail, so I have some Apps Script which regularly checks the number of messages sent from the mailbox during the last 24 hours and posts it into a Sheets file. There's then a chart in that Sheets file which I've embedded into a Sites page for staff to check before sending any emails with ~100+ recipients.

Upgraded to v5.0.28 today at it seemed a little more fussy about certificates used for LDAPS. As per https://support.google.com/a/answer/9746852 it might also need the following lines removed from the "sync-cmd.vmoptions" and "config-manager.vmoptions" files: -Djavax.net.ssl.trustStoreProvider=SunMSCAPI -Djavax.net.ssl.trustStoreType=Windows-ROOT I was finding that the LDAPS test in the config editor app was happy, and any search rules were testing successfully in the editor, but when it came to a sync run it would error out on one of my rules (one for license assignments, which differs from all other LDAP search rules in that no base DN can be specified).

Would be worth checking whether the documented installation procedure will still work for a device once outside of support. If not, then it may mean that a device needing a reinstall has to be abandoned.

Any lag in RDP being experienced on a brand new Mac is almost certainly going to be down to the connection and not the device itself.

One imagines that WhatsApp Channels may become a bit spammy, too, with diminishing returns if not used with restraint. Like everything, I suppose.

People may not generally send text messages or emails, but pretty much everybody will be able to receive them. I wouldn't have thought any school would want to send anything of any importance via WhatsApp that they didn't also send to parents via email.

Outside of IT departments: no, I doubt many people have heard of RSS.

I've not drink the Kool-Aid. Those who haven't would be able to use whatever RCS-capable app (e.g. Android Messages) to communicate with their iPhone-owning friends in group chats, etc. without both parties having to use WhatsApp or similar in order to achieve that. With iMessage falling back to plain old SMS for non-iMessage recipients, it's a crappy situation for all.

The troll emoji was obviously required there, but it would mean that I could ditch WhatsApp and just bully people into using either Android Messages or iMessage for any and all chats with me. The day Apple relents on RCS is the day WhatsApp's value falls off a cliff.