Abstract: An installation and configuration system consolidates workloads of multiple applications and services, including applications or services that may be installed or configured on multiple server devices or remotely hosted services. The system gathers environmental information, analyzes dependencies among the workloads, and populates the input data used by the workloads from a common database. The system then executes the workloads, allowing branching within the workloads or the sequence of workloads. An example of branching may include detecting an error condition, pausing the sequence, and presenting alternative fixes to a user.

Abstract: A monitoring and management system for distributed and interacting systems stores configuration settings after a successful installation or modification and compares values to the stored configuration settings. When a discrepancy is found, a messaging system may relay the information to a console where the issue may be dispositioned. In some cases, the configuration settings may be updated, while in other cases, the monitored setting may be restored to the stored configuration setting. A set of wizards or other user interface mechanisms may be used to restore the system to order.

Abstract: Extensibility computer servers and extensibility applications can be managed. Extensibility computer servers and extensibility applications can be discovered using a management application on a management computer server. An extensibility agent can be installed on an extensibility computer server, and used to provide status information. Tasks can be created for managing extensibility computer servers and extensibility applications. Entity groups representing extensibility computer servers and extensibility applications can be displayed and selected. Extensibility computer servers and extensibility applications can be displayed based on the selection of an entity group. Task templates associated with a selected entity group can be displayed.

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.

Abstract: A user interface displays multiple steps in sequential relationship to each other, and may group various steps together and provide completion indicators for each step as well as an overall completion indicator. Error conditions, status information, queries, and details about a particular step or group of steps may be displayed inline with the steps in a task detail portion of the user interface. The task detail portion may be collapsible and expandable by the user. Progress and completion indicators may be updated for each step, groups of steps, and the overall sequence. In a typical use, a software installation sequence may comprise installation steps from multiple software components. The user interface may illustrate the status of individual tasks, groups of task, and the overall sequence as the tasks are performed, and enable errors to be resolved by displaying queries and other information inline with the steps.

Abstract: An installation and configuration system consolidates workloads of multiple applications and services, including applications or services that may be installed or configured on multiple server devices or remotely hosted services. The system gathers environmental information, analyzes dependencies among the workloads, and populates the input data used by the workloads from a common database. The system then executes the workloads, allowing branching within the workloads or the sequence of workloads. An example of branching may include detecting an error condition, pausing the sequence, and presenting alternative fixes to a user.

Abstract: A backup system stores configuration data for several interdependent systems in a single backup store. As the systems are being configured and when changes are made to the systems, the backup store is updated with the change. The systems may be configured with each system having a designated role. During a restore operation, an otherwise unallocated system may assume a particular role and use the configuration logic defined for the role that may be taken from the backup store. The system may perform the restore in conjunction with the other systems and the interdependencies with the systems.

Abstract: Aspects of the subject matter described herein relate to setting up nodes. In aspects, a setup process is started to install software components to provide services to other nodes. The setup process asks for a product key and maps the product key to a product definition that indicates a number of nodes upon which the software is allowed to be installed. The product definition may also indicate what services are allowed to be installed by the setup process. The user indicates the number of nodes on which he wishes to install the software. The user may then indicate which nodes the user wishes to provide which services. This setup data is stored and may be used to determine what services to install when the setup process is executed on each of the nodes.

Abstract: Aspects of the subject matter described herein relate to setting up nodes. In aspects, a setup process is started on a node to install software components to provide services to other nodes. The setup process may also install software components on other nodes to provide additional services. A management component displays a graphical representation of the setup state of the nodes. As the setup state changes, the management component changes the representation to correspond to the new setup state of the nodes. In addition, a user may hover a cursor over an icon representing a node to obtain information about the setup state of the node or other information about the node.

Abstract: Extensibility computer servers and extensibility applications can be managed. Extensibility computer servers and extensibility applications can be discovered using a management application on a management computer server. An extensibility agent can be installed on an extensibility computer server, and used to provide status information. Tasks can be created for managing extensibility computer servers and extensibility applications. Entity groups representing extensibility computer servers and extensibility applications can be displayed and selected. Extensibility computer servers and extensibility applications can be displayed based on the selection of an entity group. Task templates associated with a selected entity group can be displayed.