I am looking at consolidating all of our scheduled tasks that run on various servers (Win 2008 R2) within our domain on to one "Task Scheduling Server". I am a developer so I'm not even sure if this is a good idea or just a maintenance headache. One of our Network guys copied some of the tasks I monitor over to the new server and asked me to test them.
A customer of mine is experiencing a very strange problem: a scheduled task is running twice from time to time, with only a few seconds between execution.
The task is scheduled using the windows scheduler. It's a very basic task that connects to a local service using TCP/IP, authenticate, gives it a command and disconnect.
I have looked everywhere for information but have not managed to find a solution.
What I need to do is be able to access the Scheduled Tasks of a Windows 2003 Server that is in domain X from a Windows 7 machine in domain Y.
If I run \\win2003server from the windows 7 machine I can access it and see the shared folders, but I cannot see the Scheduled Tasks.
I have tried to add a snap-in via MMC o
I'm running Windows Server 2003, and a scheduled task that was set to run was missed because an ms-access database window was left open over night. When we closed the window, the task scheduler started running the task.
I have three scheduled jobs that run MS-Access macros that have been stalled since Monday (it is now Weds) and reported that they were running the entire time. They reported this because they were unable to continue due to the fact that a database window was left open. I ended the tasks in task scheduler, by right clicking on them and selecting End Task.
I wrote a PowerShell script that check the executable in the < action > tag for each task in the Task directory and mark the < enabled >TRUEorFALSE< / enabled > tag as false/true depending on the validity of the digital signature of the executable.
I want Fiddler and some other programs to run on startup, so it's there and running every time I bring up an instance of my test server on EC2. There's a few questions about running scripts on Startup with Task Scheduler, but this needs to work slightly differently.
I login to a dedicated Windows 2003 server, under Administrator, with a remote desktop client, Microsoft RDC.
After 5 minutes of inactivity the server shuts me out and I have to reload RDC and login to the server again. This is good for security but I think this is causing problems for a Windows Schedule backup task I am running.
Is there a way to know the source and legitimacy of the tasks in the task scheduler in windows server 2008 and 2003? Can I check if the task was added by Microsoft (ie: from sccm) or by a 3rd party application?
For each task in the task scheduler, I want to verify that the task has not been created by a third party application.
Email this page
