Abstract: Described is a technology by which a user interface page outputs security status information obtained from network-wide and/or network client security components. This allows for simultaneous evaluation of the state of various network-wide and client security components, such as antimalware state, anti-spam state, firewall state, client program update state, and state data from a remote security service. Network security page logic couples to network-wide security components and client security components to obtain security state data for each. A user interface associated with the network security page logic lists the security components and the current security status for each, such as via an icon that changes its appearance to reflect the current state.

Abstract: An extensible management console may use a discovery mechanism to detect and identify security services across a network. After identification, the console may download and install an adapter so that the security service may be monitored and controlled using the extensible management console. A catalog of security services may be obtained from a catalog server and used to scan various devices, registries, file systems, and active services to detect and identify security services that may be added to the extensible management console.

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: A guided transition user interface may be used to transition from a first user interface to a second user interface. The guided transition user interface may include a representation of the second user interface as well as a description of a task to perform from the first user interface. The guided transition user interface may include a graphical image of the second user interface with annotated or highlighted areas that are related to the task. The guided transition user interface may be used for transitioning between areas of one application, transitioning between applications, and transitioning between interacting with different computing devices.

Abstract: A security manager aggregates various security components into a unified user interface. For each security component, the security manager may obtain an updated policy description that defines specific groups of settings for the component in terms of several threat conditions. Using the groups of settings, the security manager may classify a current state of a security component into a category. Some embodiments may use a standardized schema for an interface between a security component and the security manager. The schema may be implemented with an adapter that translates the specific settings of a security component into data for the security manager. In some embodiments, the adapter may also receive updated policy descriptions and perform a classification of the current settings.

Abstract: A license management system may include a license analyzer that is capable of evaluating different licensing strategies for software products or services on a single device or a group of devices. Rules for licensing options are coupled with actual usage data and forecasts to determine various licensing options. The options may be implemented by an automated system for renewing licenses or changing licenses and installing updated licenses.

Abstract: A license management system may have an adapter or interface that enables any type of licensed software or service to be managed through a common administrative view. The adapters may use a common schema that includes various parameters about a license as well as information that may enable a license management system to interact with a license vendor or license provider. The licenses may include locally operating software, software operating over a local area network, and various services that may be provided over a network including the Internet. The license management system may support many types of licenses and may be able to consolidate license management of many different devices and types of devices. The license management system may display the various licenses, as well as provide some other functions including alerting, usage monitoring, and managing licenses.

Abstract: Described is a technology by which a user interface page outputs security status information obtained from network-wide and/or network client security components. This allows for simultaneous evaluation of the state of various network-wide and client security components, such as antimalware state, anti-spam state, firewall state, client program update state, and state data from a remote security service. Network security page logic couples to network-wide security components and client security components to obtain security state data for each. A user interface associated with the network security page logic lists the security components and the current security status for each, such as via an icon that changes its appearance to reflect the current state.

Abstract: A system for testing software may include a driver, dispatcher and one or more executors. One or group of test cases may be provided to the testing system. Each test case includes one or more actions and may be in the form of an XML document. Each action may be dependent on or independent of previous or following actions. In preparation for executing the test case one or more times, system initialization is performed. One or more iterations of the test case may be executed and housekeeping tasks may be performed in preparation for executing the next test case. Executing an iteration of a test case includes initialization in preparation for executing the iteration, performing the actions that test the software and validating the results (including comparing the actual result with an expected result and making entries to a log) and performing local cleanup (i.e., cleanup relevant to the iteration).