Anyone have experience modifying / supplanting the task scheduler service to run under another user auspice, similar to "chrooting" under win2k / XP?
If so, how are scheduled tasks affected? Can we still run jobs as other users, or are they bound to the service account?
Here's the real issue - we need a way to delegate to sys admins the ability to modify and schedule their own jobs, in their own user space, possibly invoking system binaries, all without much security dept. intervention.
Anyone have experience modifying / supplanting the task scheduler service to run under another user auspice, similar to "chrooting" under win2k / XP?
If so, how are scheduled tasks affected? Can we still run jobs as other users, or are they bound to the service account?
Here's the real issue - we need a way to delegate to sys admins the ability to modify and schedule their own jobs, in their own user space, possibly invoking system binaries, all without much security dept. intervention.
Thanks and Happy Holidays.
------------------------------------------------------------------------
---
------------------------------------------------------------------------
---
[ reply ]