Abstract: Software can be automatically distributed in stages. An administrator can specify a stage indicating software to be distributed to nodes in a network. The nodes can be organized into groups. Administration functions can be performed via an application service provider scenario. For example, a browser-based user interface can be used to configure nodes and indicate an appropriate software stage for the nodes. Agent software at a node can query a data center to discover what software is appropriate. Software of the proper stage can be provided and installed. The software can be provided via an application service provider scenario, and automatic installation can be achieved even if the nodes are behind a firewall. A versionless arrangement can be implemented.

Abstract: A technique for enhancing fault-tolerance of a distributed computing application, including applications provided via an application service provider (ASP) model, utilizes a separate monitoring program to monitor continued operation of the distributed application software (e.g., an ASP agent) on a node of the distributed application. The application software signals its continued operation by periodically generating a “heart beat” event. On failure of the application software on the node, the monitoring program takes action to restore the application on the node, such as by restarting the application, reinstalling the application software, logging failure and/or transmitting an alert to the application's administrator.

Abstract: A method and system for providing access to software is described. A network reference (e.g., a URL) comprising a key is provided to a computer in an organization. The key can be used to download software. The key can be associated with data such as identifiers for the organization or groups within the organization. Additional network references comprising other keys also may be provided for other groups within the organization. The network reference can be generated via a request over a network in an application service provider scenario. When a request for software associated with the key is received, the key can be validated by comparing against a set of valid keys stored in a data center. Keys can be individually revoked within an organization. Downloading computers can access server computers via a web browser over an Internet connection. A node requesting software via a key can be placed into the group associated with the key.

Abstract: Software can be automatically distributed in stages. An administrator can specify a stage indicating software to be distributed to nodes in a network. The nodes can be organized into groups. The administration functions can be performed via an application service provider scenario. For example, a browser-based user interface can be used to configure nodes and indicate an appropriate software stage for the nodes. Agent software at a node can query a data center to discover what software is appropriate. Software of the proper stage can be provided and installed. The software can be provided via an application service provider scenario, and automatic installation can be achieved even if the nodes are behind a firewall. A versionless arrangement can be implemented.

Abstract: Software can be acquired via a distributed server arrangement. Software designated as to be installed at a set of nodes can be acquired from a local peer node. Nodes can include agents that periodically query a data center to discover software designated as to be installed on the node. The designated software can then be acquired via one or more references to peer nodes. The nodes can periodically update the data center to accurately indicate which software is available at the nodes. Proxy server nodes can serve as liaisons between a data center and other nodes that lack direct network access to the data center. Various aspects can be performed within an application service provider scenario. If desired, any node can be designated as a sharing peer node, a proxy server node, or both.

Abstract: An executable is executed on a computer via a software component with customization data. The software component can be embedded in a document such as a web page. The software component may be, for example, an ActiveX control or a Java applet. The executable can be a remote deployment utility for installing software. To perform a remote deployment operation, such as an installation, uninstall, or update, on client computers on a network, instructions are sent from an administrator computer to plural client computers on the network. The plural client computers can be located in different domains. The remote deployment operation is then performed on the client computers. A remote deployment operation may be performed using a downloaded remote deployment utility.