Abstract: A setup or installation operation is divided into discrete task components, each of which has a data input. The data input may be in the form of an information file that is populated by user input, discovery routines, or from predefined data. When an installation is successfully completed, the information file may be saved and be used to track a configuration history. The same information file may be used for a silent setup where an installation operation may be executed without any user input. The setup system may be extensible by adding additional discrete task components and extending the information file to include data used by the additional components.

Abstract: A setup workflow may be defined in a complex workflow manner that may have branching, error compensation, and relationships defined between a software product to be installed and previously installed or future products that may be installed. As a setup workflow operates, a remote device may be contacted for an updated setup step that may also include relationship definitions between the new setup step and other steps or installed components. The new step may be for a remotely provided service that may be used in lieu of a locally installed product. The setup workflow may include dependencies and coordinate setup workflows across multiple devices.

Abstract: The usefulness of task templates can be maintained in a number of ways. Task templates can be updated on a client server from a remote task update server by initiating communication with the remote task update server, selecting a task template from a list of available task templates presented by the remote task update server, and downloading the selected task template to the client server in a format defined by a schema. Task templates can be updated on a client server by receiving a request from the client server, presenting a task template based on the request, receiving a selection of the task template, and transmitting the task template to the client server in a format defined by a schema. Task templates can also be managed by downloading task templates, assigning group names, and storing the downloaded task templates in a database.