Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Keywords: Push Elevated Admin Administrator WinBatch Scripts Users SMS Desktop Authority
For scripts that need to run on a recurring basis, you can set up SMS to rerun the script on a schedule, but that is considerably more overhead than installing it once locally as a scheduled task.
You have one script that runs as an ONSTART scheduled task that checks and fixes per-machine settings every boot and another ONLOGON task that checks and fixes per-user settings every logon. In some cases, actions are deferred for 15 minutes to an hour to minimize startup and logon time. Other tasks are run on a daily or weekly basis and are often randomized to spread out impact on back-end systems (e.g. you don't want 100,000 computers to send a report to a web server at the same time).
If you don't have a deployment system, such as SMS, you could roll your own agent in WinBatch (a compiled script running as a service). There are many ways to implement a service that could then run your scripts via the System account. The trick is doing it with some reasonable level of security. Typically this is done by interfacing with a directory, such as AD, where you could set up objects that tell your service where to grab a new script and when to execute it.
Smaller systems management programs, such as Desktop Authority, are another option to consider. They give you a way to manage your environment with, presumably, lower cost and lower learning curve than a big system like SMS. Again they would employ some sort of agent (i.e. service) to provide elevation.
Article ID: W17942
Filename: Pushing Elevated WinBatch Scripts to Users.txt
File Created: 2010:04:19:11:14:36
Last Updated: 2010:04:19:11:14:36