Abstract: Techniques for guaranteeing that a software program is executed on a machine only during designated periods of time are provided. Service windows define time periods during which software programs targeted to execute on a machine are allowed to execute on the machine. On the machine, the service windows work in conjunction with a client process that is executing on the machine to guarantee execution of the software programs by the client process only during available service windows.

Abstract: Techniques for guaranteeing that a software program is executed on a machine only during designated periods of time are provided. Service windows define time periods during which software programs targeted to execute on a machine are allowed to execute on the machine. On the machine, the service windows work in conjunction with a client process that is executing on the machine to guarantee execution of the software programs by the client process only during available service windows.

Abstract: The validation of a product for placement in a catalog in a marketplace utilizes a distributed approval workflow. A validation engine receives product submissions for inclusion into the marketplace's catalog. The validation engine initiates the distributed approval workflow to one or more approval engines that are equipped to perform the tasks needed to validate the product. The validation engine monitors the distributed approval workflow performed by the approval engines until completion. Upon successful completion of the distributed approval workflow, the product may be placed onto the marketplace's catalog for distribution.

Abstract: Techniques for guaranteeing that a software program is executed on a machine only during designated periods of time are provided. Service windows define time periods during which software programs targeted to execute on a machine are allowed to execute on the machine. On the machine, the service windows work in conjunction with a client process that is executing on the machine to guarantee execution of the software programs by the client process only during available service windows.

Abstract: A computer health monitoring server may distribute several alerts to client devices within a network. The client devices may filter the alerts to identify alerts that apply to the client device, based on the hardware and software configuration of the device. The alerts may monitor various items and collect data defined in the alerts. A local user interface may display the alerts and any results from the alerts, and the results may be transmitted to the server. Some users having network privileges may be able to view local alerts as well as alerts from other devices in the network. Other users may be only able to view a subset of alerts. The alerts may be defined with repair processes so that a user may launch a repair activity or, in some cases, the repairs may be performed automatically as defined in the alerts.

Abstract: A management system may use a human readable script in which is defined executable statements that may gathers status information from various services. The status information may be displayed within a management user interface, which may also include various summary statistics including an overall security state. The services may be locally running services, and services provided or accessible over a local area network or wide area network. In some cases, the human readable script may include statements for starting or resuming the services, querying a running service, or querying a database related to a service. The user interface may be refreshed when the human readable script is updated and re-executed. The services may include security related services, among others.

Abstract: A computer health monitoring server may distribute several alerts to client devices within a network. The client devices may filter the alerts to identify alerts that apply to the client device, based on the hardware and software configuration of the device. The alerts may monitor various items and collect data defined in the alerts. A local user interface may display the alerts and any results from the alerts, and the results may be transmitted to the server. Some users having network privileges may be able to view local alerts as well as alerts from other devices in the network. Other users may be only able to view a subset of alerts. The alerts may be defined with repair processes so that a user may launch a repair activity or, in some cases, the repairs may be performed automatically as defined in the alerts.

Abstract: A management system may use a human readable script in which is defined executable statements that may gathers status information from various services. The status information may be displayed within a management user interface, which may also include various summary statistics including an overall security state. The services may be locally running services, and services provided or accessible over a local area network or wide area network. In some cases, the human readable script may include statements for starting or resuming the services, querying a running service, or querying a database related to a service. The user interface may be refreshed when the human readable script is updated and re-executed. The services may include security related services, among others.

Abstract: Techniques for guaranteeing that a software program is executed on a machine only during designated periods of time are provided. Service windows define time periods during which software programs targeted to execute on a machine are allowed to execute on the machine. On the machine, the service windows work in conjunction with a client process that is executing on the machine to guarantee execution of the software programs by the client process only during available service windows.

Abstract: The present application is directed to a re-use wizard. Embodiments of the re-use wizard are directed at recording data input during a wizard session into a stored “template” which may be used to re-use data when the wizard is subsequently executed. More specifically, in one aspect the re-use wizard performs a method that leverages data input during a previous wizard session. In this regard, when a relevant command is identified, the method allows the user to choose among one or more “templates” that may be used to satisfy the command. If the user selects an available template, the method causes data stored in the template to be applied to an application object that is the target of the command. As a result, the user does not need to repetitively enter data when tasks handled by the re-use wizard are scheduled to be performed.