It has over complicated things.
- It is complex to use
- Lacks scalability
- It is difficult to set up jobs to run
- We need to be able to elevate privileges like Task Scheduler
With Windows Server 2012, there is a setting for User Access Control. UAC is a security feature that prompts the user, and even administrators, when running a job that requires a higher elevation because of its interaction with the Operating System.
When you’re trying to automate tasks and run them in the background, this prompt still comes up and asks if it’s OK to raise the privilege level. That hangs the job.
When running the solution, there’s no way to get around that prompt. Any job that requires that elevated privilege sits and waits for the user to answer it.
With Windows Task Scheduler, there is a check box in the Scheduled Task that says “Run with Highest Privilege”. If that’s checked, then it automatically bypasses the UAC prompt, and completes successfully.
The only other way to get around that is to lower the UAC restriction on the server, making it more vulnerable to malicious code.
I have been using this solution since November, 2010.
We have not have issues with stability.
We had to write a scripted solution to be able to change jobs behind the scenes. The solution runs with a specific command fed into it. We fed it this script: “CSCRIPT
Our company has our own internal support.
We used Windows Task Scheduler. We switched because the new SSIS servers were going to be managed servers.
The setup was very complex. Our environment is very large. Setting up Workload Automation on our set of servers required the following:
- Setting up the agent
- Setting up the notification lists
- Filling out various forms for job stream scheduling. (It just goes on from there.)
This was the new corporate standard and we were not given a choice.
Look into ALL options. Verify that you can run your application servers with UAC turned to "do not prompt when using an admin account".