|
| | | Forum Newbie
Group: Forum Members
Last Login: 12/25/2007 7:30:53 PM
Posts: 1, Visits: 8 |
| | I want to be able to deploy a task to be run by the Windows task scheduler. The task will be a script that resides on a common network share. The script needs to be able to run as a user who is a member of the domain administrators' group. Anyone got any ideas on how to set this up? |
| |
| | | 
Supreme Being
Group: Moderators
Last Login: 2 days ago @ 2:43:01 PM
Posts: 657, Visits: 797 |
| | We suggest you try using Prism Deploy to accomplish this instead of using the Task Scheduler. Create a new Command Task to run your script. Configure the properties of the Task to run as a specified account and to allow unattended installation. These settings are on the Execution tab of the Task's properties. Assign the task to your target computers, and schedule it to be a recurring Task. The choices are hourly, weekly, monthly or at startup or logon. The timing of the Task won't be as precise as with Windows scheduler, because it will depend upon when the computer polls, but it should be fairly close. Important Note: You cannot create a Prism package that will create the scheduled task, becasue Prism can't capture and distribute the username and password for the scheduled task to use. If you want to pursue using the Task Scheduler, Microsoft's TechNet site should have detailed instructions.
New Boundary Technologies Support
support@newboundary.com |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 12/3/2007 2:23:22 PM
Posts: 2, Visits: 13 |
| | We have done it several times. Here is an example of what we did We created a PTS file and installed the packaged we wanted (creates the d:\it\export folder and put the runexport.bat file in it), then use this to schedule the job. It works great /Run /Wait %COMSPEC% /c schtasks /create /tn "Nightly Export" /tr d:\it\export\runexport.bat /sc weekly /d mon,tue,wed,thu,sun /st 22:00 /ru administrator /rp password You can do a google search on schtasks to see all your options. we started using the at command, but were not able to name the scheduled job so we went with schtasks instead. |
| |
|
|