Abstract: Content can be replicated automatically to facilitate distribution of the content to one or more devices. Determinations can be made automatically regarding where to replicate data, how to replicate data, and when to replicate data based on a variety of collected data with respect to devices, content servers, content sources, and content. More particularly, one or more content servers can be identified as targets for content replication and a protocol can be determined to replicate content from at least one source to the one or more content servers identified. Subsequently, replication can be initiated to the one or more content servers with the corresponding protocol at a determined time. Further, similar mechanisms can be employed to enable automatic determination of how and when to distribute or replicate content from one or more content servers to one or more target devices.

Abstract: Content can be replicated automatically to facilitate distribution of the content to one or more devices. Determinations can be made automatically regarding where to replicate data, how to replicate data, and when to replicate data based on a variety of collected data with respect to devices, content servers, content sources, and content. More particularly, one or more content servers can be identified as targets for content replication and a protocol can be determined to replicate content from at least one source to the one or more content servers identified. Subsequently, replication can be initiated to the one or more content servers with the corresponding protocol at a determined time. Further, similar mechanisms can be employed to enable automatic determination of how and when to distribute or replicate content from one or more content servers to one or more target devices.

Abstract: Displaying a hierarchy. A method includes identifying a set of nodes representing sites in a hierarchy. The set of nodes share one or more common characteristics not shared by any other nodes in the hierarchy. The method further includes determining that the set of nodes, as a set, meet a predetermined condition. As a result of the nodes sharing the one or more common characteristics not shared by any other nodes in the hierarchy and as a result of the set meeting the predetermined condition, the method further includes aggregating at least a portion of the set of nodes. The method further includes displaying in a graphical user interface a representation of the hierarchy including displaying the aggregated portion as a single entity in the hierarchy.

Abstract: Content can be replicated automatically to facilitate distribution of the content to one or more devices. Determinations can be made automatically regarding where to replicate data, how to replicate data, and when to replicate data based on a variety of collected data with respect to devices, content servers, content sources, and content. More particularly, one or more content servers can be identified as targets for content replication and a protocol can be determined to replicate content from at least one source to the one or more content servers identified. Subsequently, replication can be initiated to the one or more content servers with the corresponding protocol at a determined time. Further, similar mechanisms can be employed to enable automatic determination of how and when to distribute or replicate content from one or more content servers to one or more target devices.

Abstract: Described are automatically generated software deployment bookmarks that maintain information regarding events and/or triggers with respect to a network software deployment operation. The bookmarks are accessible and useable for evaluating the progress and state of the deployment. For example, a bookmark may be generated when deployment to a client machine succeeds, when a software deployment package is created and/or distributed, and for network component and/or membership state changes. A set of bookmarks may be used to generate a curve indicative of the deployment progress over time, and may be compared to previous progress of deploying other network software to client computer systems that is based on maintained performance history data.

Abstract: Displaying a hierarchy. A method includes identifying a set of nodes representing sites in a hierarchy. The set of nodes share one or more common characteristics not shared by any other nodes in the hierarchy. The method further includes determining that the set of nodes, as a set, meet a predetermined condition. As a result of the nodes sharing the one or more common characteristics not shared by any other nodes in the hierarchy and as a result of the set meeting the predetermined condition, the method further includes aggregating at least a portion of the set of nodes. The method further includes displaying in a graphical user interface a representation of the hierarchy including displaying the aggregated portion as a single entity in the hierarchy.

Abstract: Migrating services and clients from a legacy topology to a new topology. A method includes receiving user input selecting a first client managed by a first configuration management system to migrate to a second configuration management system. Dependencies of the first client are determined, including determining services on which the first client depends to function in a topology. The dependencies of the first client including services and their data on which the first client depends to function in a topology are migrated to a second configuration management system or an administrator is alerted to the dependencies of the first client including services and their data on which the first client depends to function in a topology.

Abstract: Displaying a hierarchy. A method includes identifying a set of nodes representing sites in a hierarchy. The set of nodes share one or more common characteristics not shared by any other nodes in the hierarchy. The method further includes determining that the set of nodes, as a set, meet a predetermined condition. As a result of the nodes sharing the one or more common characteristics not shared by any other nodes in the hierarchy and as a result of the set meeting the predetermined condition, the method further includes aggregating at least a portion of the set of nodes. The method further includes displaying in a graphical user interface a representation of the hierarchy including displaying the aggregated portion as a single entity in the hierarchy.

Abstract: Migrating services and clients from a legacy topology to a new topology. A method includes receiving user input selecting a first client managed by a first configuration management system to migrate to a second configuration management system. Dependencies of the first client are determined, including determining services on which the first client depends to function in a topology. The dependencies of the first client including services and their data on which the first client depends to function in a topology are migrated to a second configuration management system or an administrator is alerted to the dependencies of the first client including services and their data on which the first client depends to function in a topology.

Abstract: Displaying a hierarchy. A method includes identifying a set of nodes representing sites in a hierarchy. The set of nodes share one or more common characteristics not shared by any other nodes in the hierarchy. The method further includes determining that the set of nodes, as a set, meet a predetermined condition. As a result of the nodes sharing the one or more common characteristics not shared by any other nodes in the hierarchy and as a result of the set meeting the predetermined condition, the method further includes aggregating at least a portion of the set of nodes. The method further includes displaying in a graphical user interface a representation of the hierarchy including displaying the aggregated portion as a single entity in the hierarchy.

Abstract: Described are automatically generated software deployment bookmarks that maintain information regarding events and/or triggers with respect to a network software deployment operation. The bookmarks are accessible and useable for evaluating the progress and state of the deployment. For example, a bookmark may be generated when deployment to a client machine succeeds, when a software deployment package is created and/or distributed, and for network component and/or membership state changes. A set of bookmarks may be used to generate a curve indicative of the deployment progress over time, and may be compared to previous progress of deploying other network software to client computer systems that is based on maintained performance history data.