| ActiveMac | Anonymous | Create a User | Reviews | News | Forums | Advertise |
|
|
|
User Controls |
|
New User |
|
Login |
|
Edit/View My Profile |
|
|
|
|
|
|
|
ActiveMac |
|
Articles |
|
Forums |
|
Links |
|
News |
|
News Search |
|
Reviews |
|
|
|
|
|
|
|
News Centers |
|
Windows/Microsoft |
|
DVD |
|
ActiveHardware |
|
Xbox |
|
MaINTosh |
|
News Search |
|
|
|
|
|
|
|
ANet Chats |
|
The Lobby |
|
Special Events Room |
|
Developer's Lounge |
|
XBox Chat |
|
|
|
|
|
|
|
FAQ's |
|
Windows 98/98 SE |
|
Windows 2000 |
|
Windows Me |
|
Windows "Whistler" XP |
|
Windows CE |
|
Internet Explorer 6 |
|
Internet Explorer 5 |
|
Xbox |
|
DirectX |
|
DVD's |
|
|
|
|
|
|
|
TopTechTips |
|
Registry Tips |
|
Windows 95/98 |
|
Windows 2000 |
|
Internet Explorer 4 |
|
Internet Explorer 5 |
|
Windows NT Tips |
|
Program Tips |
|
Easter Eggs |
|
Hardware |
|
DVD |
|
|
|
|
|
|
|
Latest Reviews |
|
Applications |
|
Microsoft Windows XP Professional |
|
Norton SystemWorks 2002 |
|
|
|
Hardware |
|
Intel Personal Audio Player 3000 |
|
Microsoft Wireless IntelliMouse Explorer |
|
|
|
|
|
|
|
Site News/Info |
|
About This Site |
|
Affiliates |
|
ANet Forums |
|
Contact Us |
|
Default Home Page |
|
Link To Us |
|
Links |
|
Member Pages |
|
Site Search |
|
Awards |
|
|
|
|
|
|
|
Credits |
 |
Task Scheduler Changes in Windows Vista and Windows Server 2008 Part Two | |
|
||
| Time: 00:26 EST/05:26 GMT | News Source: Microsoft | Posted By: Kenneth van Surksum | ||
|
In Part One, we discussed the new User Interface, Triggers and Task Conditions. Today were going to discuss Flexible Actions and Triggers, Security and Reliability. So, lets get started For flexible actions and triggers, prior to Windows Vista and Windows Server 2008, a task was launched based on a single trigger and that job could only include one action. One of the most common scenarios we encounter is a task that launches a script that launches another script and so on and somewhere inside all of these nested and linked scripts, a failure occurs. With the new changes, this scenario is mitigated. Multiple triggers can now be attached to any given task. For example, a given error condition might be indicated only if three different events occur. An administrator can easily define a task that will launch only if all three of these events occur. | ||
|
Write Comment
Return to News |
Displaying 501 through 522 of 522 Prev | First |
The time now is
5:55:29 PM
ET.
Any comment problems? E-mail us |
|
Write Comment
Return to News |
Displaying 501 through 522 of 522 Prev | First |
The time now is
5:55:29 PM
ET.
Any comment problems? E-mail us |
