TASK SCHEDULER

http://msdn.microsoft.com/en-us/library/windows/desktop/aa383987(v=vs.85).aspx
http://msdn.microsoft.com/en-us/library/windows/desktop/aa394582(v=vs.85).aspx
http://msdn.microsoft.com/en-us/library/windows/desktop/aa383953(v=vs.85).aspx

http://msdn.microsoft.com/en-us/library/windows/desktop/hh437524(v=vs.85).aspx
http://msdn.microsoft.com/en-us/library/windows/desktop/aa394582(v=vs.85).aspx#


Task Scheduler 2.0 Triggers

The following trigger types are defined by the TASK_TRIGGER_TYPE2 enumeration.TriggerDescriptionEvent trigger (event based trigger)For scripting development, see EventTrigger.For C++ development, see IEventTrigger.For XML development, see EventTrigger Element.Starts the task when a specific system event occurs.Time trigger (time-based trigger)For scripting development, see TimeTrigger.For C++ development, see ITimeTrigger.For XML development, see TimeTrigger Element.Starts the task at a specific date and time.Daily trigger (time-based calendar trigger)For scripting development, see DailyTrigger.For C++ development, see IDailyTrigger.For XML development, see CalendarTrigger Element.Starts the task at a specific time on a daily schedule. For example, the task starts at 8:00 AM every day or every other day.Weekly trigger (time-based calendar trigger)For scripting development, see WeeklyTrigger.For C++ development, see IWeeklyTrigger.For XML development, see CalendarTrigger Element.Starts the task at a specific time on a weekly schedule. For example, the task starts at 8:00 AM on a specific day of the week every week or on a specific day of the week every other week.Monthly trigger (time-based calendar trigger)For scripting development, see MonthlyTrigger.For C++ development, see IMonthlyTrigger.For XML development, see CalendarTrigger Element.Starts the task at a specific time on a monthly schedule. For example, the task starts at 8:00 AM on specific days of the month on specific months.Monthly day-of-week (DOW) trigger (time-based calendar trigger)For scripting development, see MonthlyDOWTrigger.For C++ development, see IMonthlyDOWTrigger.For XML development, see CalendarTrigger Element.Starts the task at a specific time on a monthly day-of-week schedule. For example, the task starts at 8:00 AM on specific days of the week, weeks of the month, and months of the year.Idle trigger (event-based trigger)For scripting development, see IdleTrigger.For C++ development, see IIdleTrigger.For XML development, see IdleTrigger Element.Starts the task when the computer enters an idle state.Registration trigger (event-based trigger)For scripting development, see RegistrationTrigger.For C++ development, see IRegistrationTrigger.For XML development, see RegistrationTrigger Element.Starts the task when the task is registered or updated.Boot trigger (event-based trigger)For scripting development, see BootTrigger.For C++ development, see IBootTrigger.For XML development, see BootTrigger Element.Starts the task when the system is booted.Logon trigger (event-based trigger)For scripting development, see LogonTrigger.For C++ development, see ILogonTrigger.For XML development, see LogonTrigger Element.Starts the task when a user logs on.Session state change trigger (event-based trigger)For scripting development, see SessionStateChangeTrigger.For C++ development, see ISessionStateChangeTrigger.For XML development, see SessionStateChangeTrigger Element.Starts the task when a Terminal Server session changes state. 

Task Scheduler 1.0 Triggers

The following trigger types are defined by the TASK_TRIGGER_TYPE enumeration. To implement any of the following triggers, see the TASK_TRIGGER structure.Once trigger: Starts the task a single time.Daily trigger: Starts the task on a daily interval.Weekly trigger: Starts the task on a weekly schedule.Monthly trigger: Starts the task on a monthly schedule.Monthly DOW trigger: Starts the task on a monthly day-of-week schedule.On Idle trigger: Starts the task when the computer is in an idle state.System Start trigger: Starts the task when the computer is booted.Logon trigger: Starts the task when a specific user logs on.

Related topics

Task TriggersTrigger InterfacesTrigger Structures  


rigger Interfaces (Windows)

Windows Desktop App DevelopmentDesktop app development documentationSystem AdministrationTask SchedulerAbout the Task SchedulerTask TriggersTrigger TypesTrigger InterfacesTask Scheduler 1.0 TriggersThis topic has not yet been rated - Rate this topicThe APIs that are used to manage triggers vary depending on the version of the Task Scheduler. However, in both cases these APIs enable you to create new triggers, retrieve and update existing triggers, and delete triggers that are no longer required.

Applications that are developed using Task Scheduler 2.0 can use objects and interfaces to create, retrieve, modify, and delete the triggers for a task.In the following illustration, a task specifies a collection of triggers using its Triggers property. This collection contains one or more individual trigger APIs with each API specifying a specific trigger type. For example, in the illustration below the trigger collection contains a boot trigger, logon trigger, and a daily trigger.

Object APIs for Scripting Development

For more information about the methods and properties of the objects that are used to specify triggers, see:TaskDefinitionTriggerCollectionTriggerBootTriggerDailyTriggerEventTriggerIdleTriggerLogonTriggerMonthlyDOWTriggerMonthlyTriggerRegistrationTriggerTimeTriggerWeeklyTrigger

Interfaces APIs for C++ Development

For more information about the methods and properties of the interfaces that are used to specify triggers, see:ITaskDefinitionITriggerCollectionITriggerIBootTriggerIDailyTriggerIEventTriggerIIdleTriggerILogonTriggerIMonthlyDOWTriggerIMonthlyTriggerIRegistrationTriggerITimeTriggerIWeeklyTrigger

Task Scheduler 1.0 Trigger Interfaces

Existing applications that are developed using Task Scheduler 1.0 can use the methods that are available from the Task Scheduler 1.0 interfaces to create, retrieve, modify, and delete the triggers for a work item. However, note that all Task Scheduler 1.0 interfaces, enumerations, and structures are obsolete and should not be used for the development of new applications.The two interfaces that are used to do this are shown in the following illustration. The IScheduledWorkItem interface is used to manage all the triggers that are associated with a work item (such management includes creating a new trigger for the work item). The ITaskTrigger interface is used to manage a specific trigger.The IScheduledWorkItem interface provides methods for creating a new trigger for a work item, retrieving the number of triggers that are associated with a work item, retrieving the trigger structures that are associated with the work item, retrieving trigger strings that are associated with the work item, and for deleting triggers.Once the trigger object is available, you can use the ITaskTrigger interface to retrieve the trigger structure and the string of the trigger and to set the criteria that is used to fire the trigger. This interface is used only when you are working with a task trigger object.

Related topics

Task TriggersTrigger TypesTrigger Structures  Send comments about this topic to MicrosoftBuild date: 10/30/2012Did you find this helpful? Yes 


User Access Logging MOF classes (Windows)

Windows Desktop App DevelopmentDesktop app development documentationSystem AdministrationUser Access LoggingUser Access Logging referenceUser Access Logging MOF classesMsftUal_AdminMsftUal_DailyAccessMsftUal_DailyDeviceAccessMsftUal_DailyUserAccessMsftUal_DeviceAccessMsftUal_DnsMsftUal_HyperVMsftUal_OverviewMsftUal_ServerDeviceMsftUal_ServerUserMsftUal_SystemIdMsftUal_UserAccess0 out of 1 rated this helpful - Rate this topicUser Access Logging defines the following MOF classes.

In this section

TopicDescriptionMsftUal_AdminThis is a class of methods for enabling and disabling the User Access Logging feature.MsftUal_DailyAccessThis is a class of property qualifiers that provides client device access data on a given day of the year, or range.MsftUal_DailyDeviceAccessThis is a class of property qualifiers that provides client device access data on a given day of the year, or range.MsftUal_DailyUserAccessThis is a class of property qualifiers that provides client user access data on a given day of the year, or range.MsftUal_DeviceAccessThis is a class of property qualifiers that provides client device access details for roles and products installed on the local server.MsftUal_DnsThis is a class of property qualifiers that provides client host and device data for the DNS role on the local server, if applicable.MsftUal_HyperVThis is a class of property qualifiers that provides virtual machine details for the Hyper-V role on the local server, if applicable.MsftUal_OverviewThis is a class of property qualifiers that provides an overview of roles and products installed and registered with the User Access Logging feature.MsftUal_ServerDeviceThis is a class of property qualifiers that provides client access detail by device, for the local server as a whole.MsftUal_ServerUserThis is a class of property qualifiers that provides client access detail by user, for the local server as a whole.MsftUal_SystemIdThis is a class of property qualifiers that provides profile details of the local server and reflects changes if they are made.MsftUal_UserAccessThis is a class of property qualifiers that provides client user access details for roles and products installed on the local server.   Windows Management Instrumentation (Windows)

Windows Desktop App DevelopmentDesktop app development documentationSystem AdministrationBoot Configuration Data WMI ProviderWhat's New in the BCD WMI ProviderAbout the BCD WMI ProviderMapping Boot Options to ElementsBCD WMI Provider ReferenceBCD WMI Provider ClassesBCD WMI Provider EnumerationsBCD WMI Provider StructuresGroup PolicyGroup Policy APIAbout Group Policy APINew for Group PolicyGroup Policy ArchitectureGroup Policy ObjectsLinking GPOs to Active Directory ContainersGroup Policy StorageGroup Policy HierarchyFiltering the Scope of a GPOApplying Group PolicyGroup Policy Object EditorAbout the MMC Extension Snap-in ModelGroup Policy Object Editor NamespaceExtensions to the Group Policy Object EditorClient-side Extensions to Group PolicyPolicy ProcessingInitial Processing of Group PolicyBackground Refresh of Group PolicyReading Policy Data from the RegistryClient-side Processing of Group PolicyLogon OptimizationReporting Group PolicyRSoP ArchitectureAbout the RSoP Snap-inAbout the RSoP WMI Method ProviderRSoP DelegationProviding Policy for Your ApplicationsPolicy EventsOptions for Providing PolicyAdhering to System Policy SettingsExtending Registry-based PolicyUser Interface for Registry-based PolicyData Storage for Registry-based PolicyEvent Processing for Registry-based PolicyWriting a Group Policy ExtensionUser Interface for Third-Party Group Policy ExtensionsData Storage for Third-Party Group Policy ExtensionsEvent Processing for Third-Party Group Policy ExtensionsSupporting and Extending RSoPCreating an RSoP User InterfaceAdding RSoP to your Extension Snap-inDeveloping an RSoP Management ToolAbout Group Policy PreferencesExtending the Applications Snap-inRegister the Extension to the Property Sheet of the Applications Snap-inImplement Support for Applications Snap-in Menu IntegrationDefine All Required GUID ValuesDefine All Required NamesObtain the IXMLDOMDocument* from the Primary Snap-in's IDataObjectFilter Display of Property Pages Using the extid AttributeImplement the IExtendPropertySheet2::CreatePropertyPages Method to Display Property PagesImplement a Dialog Box Procedure for Each Property PageImplement an Apply Handler for Each PageWrite Default DataWrite Property DataRead Property DataImplement Help SupportRelease the IXMLDOMDocument* ObjectBasic MSXML Utility FunctionsApplications Snap-in Extension Sample CodeHeader FilesSource FilesUsing Group Policy APIGroup Policy API ReferenceGroup Policy Management ConsoleAbout the Group Policy Management ConsoleGPMC Features and FunctionalityGPO Operations Supported by the GPMCSystem Requirements for the Group Policy Management ConsoleUsing the Group Policy Management ConsoleCopying and Importing GPOs Across DomainsImporting GPOs from a Test to a Production ForestImporting GPOs from one Production Forest to AnotherUsing Migration TablesGroup Policy Management Console Scripting Samples OverviewGroup Policy Management Console ReferenceGPMC Class LibraryAbout the GPMC Class LibraryInstalling the GPMC Class LibraryAdding the GPMC Assembly to a Visual Studio ProjectUsing the GPMC Class Library from Windows PowerShellUsing the GPMC Class LibraryHow to Back Up All GPOs in a DomainHow to Restore a Domain's GPOsHow to Import GPOs from a BackupHow to List Unlinked GPOs in a DomainGPMC Class Library ReferenceMicrosoft.GroupPolicyMicrosoft.GroupPolicy.CommandsMicrosoft Management Console (MMC)Welcome to the MMC 3.0 GuidelinesLegal InformationHow to Use This GuideArchitecting Management ToolsConstructing Snap-insCommon UI Controls and Text GuidelinesAbbreviations/AcronymsAccess KeysAccessibilityAnimationBorder StyleCapitalizationCheck BoxesColumn HeadingsCommand ButtonsCommands, standardControls, referring toCross-ReferencesDialog BoxesDrop-Down MenusEvent Log MessagesFontsGroup BoxesGroup Policy Explain TextIcons and Other GraphicsLabelsLayoutLayout Specifications: Win32Layout Specifications: Windows FormsList BoxesList View ControlsMenusMessagesOpen AppearanceOption ButtonsProgress IndicatorsPunctuationSelection AppearanceShortcut KeysShortcut MenusSlidersSpin BoxesStatus BarsSubordinationTablesText BoxesText FieldsTipsTitle BarsToolbarsTransfer AppearanceTree View ControlsUsability ConsiderationsVisual Index: ControlsVisual Index: SurfacesBest Practices: Monitoring and ReportingMonitoring: Best PracticesReporting: Best PracticesChecklist of Architecting GuidelinesGlossary of MMC TerminologyGlossary of UI TerminologyMicrosoft Management Console 3.0Microsoft Management Console 3.0MMC Class LibraryMicrosoft.ManagementConsoleMicrosoft.ManagementConsole.AdvancedMicrosoft Management Console 2.0NetShellOverview of NetShellComponents of NetShellCreating a NetShell HelperNetShell ReferenceSettings Management Infrastructure (SMI)Software Licensing APISystem RestoreSystem ShutdownTask SchedulerWhat's new in Task SchedulerAbout the Task SchedulerUsing the Task SchedulerTask Scheduler ReferenceTask Scheduler GlossaryUser Access LoggingHow to report user access to a server.User Access Logging referenceWindows Deployment ServicesWindows Genuine Advantage APIWindows Management InstrumentationAbout WMIUsing WMIWMI ReferenceWMI GlossaryWindows Management InfrastructureWindows PowerShellInstalling the Windows PowerShell SDKWriting a Windows PowerShell ModuleWriting a Windows PowerShell CmdletWriting a Windows PowerShell ProviderWriting a Windows PowerShell Host ApplicationWriting a Windows PowerShell Formatting FileWriting a Windows PowerShell WorkflowScheduling Jobs with the Windows PowerShell APIWindows PowerShell ReferenceCreating a Management OData IIS Extension Web ServiceWindows Remote ManagementAbout Windows Remote ManagementUsing Windows Remote ManagementWindows Remote Management ReferenceWindows Remote Management GlossaryWindows Resource ProtectionWindows Server Update ServicesWindows System Assessment Tool172 out of 404 rated this helpful - Rate this topic

Purpose

Windows Management Instrumentation (WMI) is the infrastructure for management data and operations on Windows-based operating systems. You can write WMI scripts or applications to automate administrative tasks on remote computers but WMI also supplies management data to other parts of the operating system and products, for example System Center Operations Manager, formerly Microsoft Operations Manager (MOM), or Windows Remote Management (WinRM).

Where applicable

WMI can be used in all Windows-based applications, and is most useful in enterprise applications and administrative scripts.System administrators can find information about using WMI at the TechNet ScriptCenter, and in various books about WMI. For more information, see Further Information.

Developer audience

WMI is designed for programmers who use C/C++, the Microsoft Visual Basic application, or a scripting language that has an engine on Windows and handles Microsoft ActiveX objects. While some familiarity with COM programming is helpful, C++ developers who are writing applications can find good examples for getting started at Creating a WMI Application Using C++.To develop managed code providers or applications in C# or Visual Basic .NET using the .NET Framework, see WMI in .NET Framework.The WMI Software Developer Kit (SDK) is available as a download that includes documentation at the Download Center. The WMI Redistributable Components version 1.0 file, is required only for Windows 2000 and is available to download at the same location.WMI functionality introduced in the Windows 2000 Professional with Service Pack 2 (SP2) operating system is also available to earlier operating systems by downloading the .NET Framework SDK, and the .NET Framework Redistributable. These can be obtained at http://msdn2.microsoft.com/en-us/netframework/aa731542.aspx.

Run-time requirements

For more information about which operating system is required to use a specific API element or WMI class, see the Requirements section of each topic in the WMI documentation.If an expected component appears to be missing, see Operating System Availability of WMI Components.

In this section

TopicDescriptionAbout WMIGeneral information about WMI.Using WMIInformation about how to develop applications to use WMI, which includes information about tools.WMI ReferenceDocumentation about the WMI classes, WMI C++ classes, WMI COM API, Scripting API, and other WMI reference material.   Send comments about this topic to MicrosoftBuild date: 11/19/2012Did you find this helpful? Yes No

Community Additions

ADD

kenneth

none yetbogusb7/15/2012

Problems ...

Where direct link for download Windows Management Instrumentation SDK?[tfl - 07 06 09] Hi - and thanks for your post. You should post questions like this to the MSDN Forums at http://forums.microsoft.com/msdn or the MSDN Newsgroups at http://www.microsoft.com/communities/newsgroups/en-us/. You are much more likely get a quicker response using the forums than through the Community Content. For specific help about:Visual Studio : http://groups.google.com/groups/dir?sel=usenet%3Dmicrosoft.public.vstudio%2C&.NET Framework : http://groups.google.com/groups/dir?sel=usenet%3Dmicrosoft.public.dotnet.frameworkAll Public : http://groups.google.com/groups/dir?sel=usenet%3Dmicrosoft.public%2C&awlva kumar11/2/2011

Malware Alert

Alert user to malware threats as they are occurring.BarrettAlan9/22/2011

PowerShell, WMI and Administrators

As noted earlier on this page, WMI is primarily a developer tool although in many cases (eg SCCM and OCS) it can be used as an admin tool. With PowerShell, it is much easier to access WMI as a useful tool for the IT administrator. PowerShell's Get-WMI cmdlet enables you to retreive information for a local or remote WMI repository.To illustrate this use of WMI, a number of the WMI classes have PowerShell samples - search for the tags "PowerShell WMI Code" to find them.I'm not sure why the previous author considers WMI as a "developer tool". What I will say is that its the most un-intrusive and powerful way to manage systems running 24/7. Its like hot-wiring a car without laying a hand on the car.Having WMI classes in Powershell as far as I'm concerned is the only reason to bother with Powershell. The rest of the Powershell functionality can be operated with GUIs and MMC aplets.بريق ألالماس8/4/2011

mk:@MSITStore:C:\Program%20Files\Debugging%20Tools%20for%20Windows%20(x86)\debugger.chm::/hh/Debugge

https://www.microsoftelearning.com/security/developer/xchungdungx1/25/2011