If you are scheduling tasks, no doubt you run across the issue that if you need a task run as a different user, said user needs the right to logon as a batch job. Doing this is fairly easy:

  1. Start secpol.msc
  2. Expand Local Policies -> User Right Assignment
  3. Find “Logon as a batch job”
  4. Add the user / service account as needed

This can of course also be set up via GPO.

Office 2016 and 2013 users who use run-a-script rules are discovering their scripts are currently disabled (as is Start Application), thanks to a security update. When the update is installed, any existing run-a-script and run application rules will be disabled.

 

 

 

^ that option, ‘start application’ is missing.

The fix is easy, as usual, just a registry key.  :o)

Credit: https://www.slipstick.com/outlook/rules/outlook-2016-run-a-script-rules

 

So you are in a hybrid environment and moved your Public Folders to o365 but suddenly 3rd party people can no longer send you emails?

Yeah… try this:

 

Trying to block zip files with O365 seems a little painful, as the default GUI does not really give you the option (anymore?) If you Google, you might find screenshots with options to select the attachment but when I checked our GUI, that was all that I saw:

Clearly, there is no option to look for attachments, other than what the attachments CONTAIN.

So, trying PowerShell, something interesting happened.

Executing this PowerShell command, it created a new rule, that now had more/different options than the rule you could create from the GUI!

Look at this:

And now you can block file extensions and stuff to your heart’s content.

Oddities ¯\_(ツ)_/¯