I had to deal with this about 2 years ago. my foggy recollection is that schedule jobs run as "System", and the "system" user has absolutely zero rights on other machines (but is like root on the local). You cannot get the system account priviledges set for other machines, so logging in as another user is required.

I am pretty sure I used the module mentioned by tye, but in effect, what I had to do was startup and then login/alias myself as a user that had priviledges on the target shares. I do remember it was a real pain in the ass (I recall swearing alot and damning all things windows to eternal hell), and ended up finding an alternative solution. I wish I could be more helpful, but it's been too long and I don't have any of that code.

if you can manage to get this going, I'd certainly ++ your tutorial :-)

PS: since it runs from an icon, maybe you need that rocking monkey toy that Homer Simpson used to tap his keyboard in order to keep the nuclear reactor from melting down? (oh wait, that didn't work) :-)