Heads-up on schedule with network shared xml

[Moopere]

This isn't a bug, its a heads-up.

I notice that on one of the many machine I have with WOL installed (for administration), the one I use for scheduled tasks, after the last update new tasks were failing to run (access denied), yet old tasks where running fine.

Interestingly, editing an old task and then saving it also rendered it inoperative.

After scratching my chin for a moment I realized that my xml file is on a network share. The network share is mapped during login via a script. When the scheduler runs the task the mapped drive to the xml file is unavailable (as no-one is logged in).

Now I'm wondering how this ever worked (!!!) - but it did. Now it doesn't.

The way to fix this problem of course is to not use the drive mapping in the path of the network-shared xml file, use the UNC path. After doing this, scheduled WOL tasks work fine.