Arnout’s Eclectica

How to disable Outlook:

Thanks, eh.

My company sent out an e-mail newsletter today, and I was just taking a quick peek at the bounces and out-of-office messages.

One stood out:

Microsoft Forefront Security for Exchange Server has matched a filter.
Filter name: "KEYWORD= no_go: relationship"
State: Purged

I guess "relationship" features relatively frequently in spam, but bouncing an email just because the word appears seems a bit blunt to me.

When Aphex Twin's "Nanou 2" just came up on my playlist, I decided to Google it, hoping for some "if you like X, you'll also like Y" serendipity.

No such luck, but one of the first hits read:

  Unfortunately the lyrics of Nanou 2 performed by Aphex Twin are missing.

Surprising, that. (And if that doesn't make sense to you, check it out. I'm not a big Aphex fan, but this is beautiful.)

Just came across the following line in the sources to zlib:

if (hash_head) hash_head = 0;  /* to make compiler happy */

Earlier today, I was trying to run a batch file as a scheduled task, using a non-admin service account. It didn't work, but the scheduled tasks interface didn't provide a lot of info to go on.

After double-checking file system permissions, and running Filemon to try and figure out where stuff was failing, I found out that the task scheduler actually creates a log file. By default it seems to live at %SystemRoot%\Tasks\SchedLgU.Txt, but that location can be changed in the registry by modifying the LogPath value at HKLM\SOFTWARE\Microsoft\SchedulingAgent.

That log file contained an error message (well, several...) that quickly lead me to Microsoft Knowledgebase article KB867466. Turns out that on Windows Server 2003 member servers, non-admin users running non-interactively don't have Read or Execute permissions to cmd.exe...

After fixing the permissions, the job ran fine.

That's when I discovered that the batch file was making some assumptions w.r.t. the user's regional settings, so I switched to a VBScript instead. If I'd done that in the first place, I wouldn't have had to spend 15 minutes fighting with the task scheduler, since the permissions issue doesn't apply to cscript.exe...

Oh well.