Task sequence interface

• US 8,086,659 B2
• Filed: 06/25/2003
• Issued: 12/27/2011
• Est. Priority Date: 06/25/2003
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Steeb, Curt A., Pedrizetti, Raymond D., Prabu, Munisamy, Xu, Zeyong, Holladay, Martin L., Sutton, Paul C.
• Primary Examiner(s): Winder, Patrice
• Assistant Examiner(s): Dailey, Thomas
• Application Number:
  US10/607,411
• Publication Number:
  US 20040268292A1
• Time in Patent Office: 3,107 Days
• Field of Search: 709/201, 717/171, 717/172
• US Class Current: 709/201
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: G06F 9/54 Interprogram communication

Abstract

According to one aspect of task sequence interfaces, a method includes exposing an interface that allows task sequences to be performed on a plurality of remote devices, and receiving requests regarding the task sequences and the plurality of remote devices via the interface. The interface comprises an object model including device objects that represent physical devices in a network, and jobs objects that represent task sequences performed on one or more of the plurality of remote devices.

Claims

1. One or more computer storage devices having stored thereon a plurality of instructions that, when executed by one or more processors of a controller, causes the one or more processors to:

maintain, within an object model interface, a job tree object including a plurality of job objects that are respectively associated with a plurality of target devices of a set of target devices, wherein;

each job object represents a job, and each job is a task sequence that can be performed by the controller on the target device that is associated with that job object, and

each task sequence comprises a sequence of steps to be performed by an automated deployment service when the target devices of the set of target devices have all been booted;

automatically detect when the target devices are each being booted; and

expose a start method that, when invoked by Preboot Execution Environment (PXE) service requests from the target devices, causes the one or more processors to start performing the sequences of steps represented by the job objects on the target devices.

2. One or more computer storage devices as recited in claim 1, wherein the target devices comprise remote devices coupled to the controller via a network.

3. One or more computer storage devices as recited in claim 1, wherein the plurality of instructions further cause the one or more processors to expose a stop method that, when invoked, causes the one or more processors to stop performing one or more of the jobs currently in progress.

4. One or more computer storage devices as recited in claim 1, wherein the plurality of instructions further cause the one or more processors to expose a get output method that, when invoked, causes the one or more processors to retrieve output from a job log associated with one or more of the jobs.

5. One or more computer storage devices as recited in claim 1, wherein the plurality of instructions further cause the one or more processors to expose a clear method that, when invoked, causes the one or more processors to delete at least a portion of a history of jobs that have been performed.

6. One or more computer storage devices as recited in claim 1, wherein the plurality of instructions further cause the one or more processors to expose a validate method that, when invoked, causes the one or more processors to validate one or more of the task sequences.

7. One or more computer storage devices as recited in claim 1, wherein each job is associated with one or more control components, and each of the control components includes:

an identifier property that specifies an identifier of the job;

a type property that specifies an identifier of a type of the job; and

a state property that specifies a current status of the job.

8. One or more computer storage devices as recited in claim 1, wherein each job is associated with one or more control components, and each of the control components includes:

an exit property that specifies an exit code returned from successful completion of the job;

a start time property that specifies when the job started;

an end time property that specifies when the job completed;

a timeout property that specifies a period of time that the controller will allow for the job to be performed;

a target type property that specifies a type of the target;

a target name property that specifies a name of the target; and

a user name property that specifies a user that started the job.

9. One or more computer storage devices as recited in claim 1, wherein the plurality of instructions further cause the one or more processors to maintain a job log component that stores one or more outputs resulting from performing one or more of the jobs.

10. One or more computer storage devices as recited in claim 9, wherein the job log component includes:

an identifier property that includes an identifier of one or more of the jobs;

a type property that includes a type of the one or more outputs; and

a data property that includes the one or more outputs resulting from performing one or more of the jobs.

11. One or more computer storage devices as recited in claim 9, wherein the job log component includes:

a sequence property that includes indications of the sequence in which the one or more outputs are received; and

a time property that includes one or more times at which the one or more outputs are received.

12. A method comprising:

maintaining by a controller device, within an object model interface, a job tree object including a plurality of job objects that are respectively associated with a plurality of target devices of a set of target devices, wherein;

each job object represents a job, and each job is a task sequence that can be performed by the controller on the target device that is associated with that job object, and

each task sequence comprises a sequence of operations to be performed by an automated deployment service when the target devices of the set of target devices have all been booted;

automatically detecting, by the controller device, when the target devices are each being booted; and

exposing, by the controller device, a start method that, when invoked by Preboot Execution Environment (PXE) service requests from the target devices, causes the controller device to perform the sequences of operations represented by the job objects on the target devices.

13. A method as recited in claim 12, further comprising:

exposing a stop method that, when invoked, causes the controller device to stop performing one or more of the jobs currently in progress;

exposing a get output method that, when invoked, causes the controller device to retrieve output from a job log associated with one or more of the jobs;

exposing a clear method that, when invoked, causes the controller device to delete at least a portion of a history of jobs that have been performed;

or

exposing a validate method that, when invoked, causes the controller device to validate one or more of the task sequences.

14. A method as recited in claim 12, further comprising maintaining a job log component that stores one or more outputs resulting from performing one or more of the jobs.

15. A method as recited in claim 12, wherein the set of target devices are represented by sets objects of an object model associated with the object model interface.

16. A method as recited in claim 15, wherein the object model includes images objects that represent a captured image that is available to be deployed on one or more of the target devices.

17. A system comprising:

one or more processors; and

one or more modules configured to be operated by the one or more processors to perform actions including;

maintaining, within an object model interface, a job tree object including a plurality of job objects that are respectively associated with a plurality of target devices of a set of target devices, wherein;

each job object represents a job, and each job is a task sequence that can be performed by the controller on the target device that is associated with that job object, and

each task sequence comprises a sequence of operations to be performed by an automated deployment service when the target devices of the set of target devices have all been booted;

automatically detecting when the target devices are each being booted; and

exposing a start method that, when invoked by Preboot Execution Environment (PXE) service requests from the target devices, causes the system to perform the sequences of operations represented by the job objects on the target devices.

18. A system as recited in claim 17, wherein the actions further comprise:

exposing a stop method that, when invoked, causes the system to stop performing one or more of the jobs currently in progress;

exposing a get output method that, when invoked, causes the system to retrieve output from a job log associated with one or more of the jobs;

exposing a clear method that, when invoked, causes the system to delete at least a portion of a history of jobs that have been performed;

or

exposing a validate method that, when invoked, causes the system to validate one or more of the task sequences.

19. A system as recited in claim 17, wherein the one or more modules include a job log component that stores one or more outputs resulting from performing one or more of the jobs.

20. A system as recited in claim 17, wherein the one or more modules include one or more control components, each job associated with one or more of the control components, and each of the control components including:

an identifier property that specifies an identifier of the job;

a type property that specifies an identifier of a type of the job; and

a state property that specifies a current status of the job.