Just the machine running the script needs to have AdminMisc installed. The target machines need to have the scheduler/mstask service running. | [reply] |
A couple of other things worth thinking about with Scheduler is permissions:
-
It could get tricky if the target machines are on different domains\workgroups.
- Remember that by default Scheduler service runs under the Local Sytem account.
If the target machines are on different domains\workgroups you may not be able to use ScheduleAdd() remotely. You could try Win32::AdminMisc::LogonAsUser() but I am not sure how that works. In a worst case scenario, you may need to run the script once under the admin account for each domain\workgroup.
Although these points probably aren't relevant to this question, I recommend setting up a seperate account for the scheduler service and only give it the permissions that your scheduled tasks need rather than all those that LocalSystem has by default.
Error: Keyboard not attached. Press F1 to continue.
Update: Sorry joe, this was meant as a reply to Ray.
| [reply] |
