Tag Info

New answers tagged

3

Go into Task Scheduler (taskschd.msc). While there, there's a button on the right menu for Display All Running Tasks. I think this is what you want. While you're there, you should turn on Enable All Tasks History, so you could track something like this better in the future.


0

I had a similar problem - changed to /COPY:DATS and no more error Copy was from Server 2003 to a Hitachi HDI.


0

Using the Task Scheduler Event IDs on MSDN as your reference, run a Powershell query to list the relevant Task Scheduler events that have occurred. For instance, this will list all the tasks that correspond to event id 107 (executed by a time trigger). Get-WinEvent -LogName Microsoft-Windows-TaskScheduler/Operational | ? { $_.Id -eq 107 } You could then ...


1

If it's something running through the task scheduler, you can look at the Event Logs to see what ran during that time. It will be fairly verbose, so you will need to filter out regular occuring events, but it might help you drill down on the issue. Event Viewer -> Application and Security Logs -> Microsoft -> Windows -> Task Scheduler -> Operational should ...


0

Connecting with WSMan you can connect to the iDRAC of the server(s) and get their powerstate. This then can then determine if you need to poweron the box or leave it as is. PowerShell can help with making this connection but you need to know the commands. The WOL dosn't apply being that it is an Out-of-Band Management device the iDRAC as it is always on as ...


1

I have setup WOL on the R410 / IDRAC6 servers for similar reasons. The WOL is activated via a powershell script which wakes the servers in a very specific order as we have clusters and servers which depend on other systems being available first. While unable to schedule a power up on individual servers I accomplish this by having a Locally connected ...


2

The task runs in user session 0 by default and does not interact with the desktop. See windows-7-task-scheduler-to-start-application-in-user-session You can confirm if this is your issue but running the Task Scheduler task manually while logged into the domain admin account it runs under. The telnet window, etc. should run at that point in the interactive ...


-1

Yes it's possible ! Just export the task (right click on the task / Export...) as an XML file (on the Desktop for instance). Then, delete the task in the Tasks Scheduler and right click / Import a task. Choose the previously saved XML file, rename the task and save it. Voila.


4

The default working directory for a scheduled task running as the Local System account is %Windir%\System32\ Source: I just tested it by making a scheduled task, running as SYSTEM, that executed a batch file. The batch file contained the line ipconfig > test123.txt. When the scheduled task is run, the test123.txt file appears in the Windows\System32 ...


1

Put your scheduled task on the disk shared between the cluster nodes. Then put identical scheduled tasks on both nodes running the task from the shared drive. The drive will not exist on the inactive node, so you should get what you want and the task will run only on the active node.


2

Since you said "msdb", I'll just assume you're using Microsoft SQL. Knowing the version would be somewhat helpful. Do this with either a Windows Scheduled Task or a SQL Maintenance Plan. The latter will be simple and graphical. A SQL Maintenance Plan will be easier because you can simply specify "all user databases", which excludes the system databases. ...



Top 50 recent answers are included