Abstract: A guided process framework includes a process engine, one or more data stores, and one or more user interfaces configured to communicate with the process engine. A user can access a given process instance through any appropriately configured user interface, which contacts the process engine, and which in turn contacts/consults definitions for one or more guided processes at a data store. If the user finishes only part of a given process instance, the process engine can save state corresponding to the progress in the data store. A user can continue work on the process instance through a different user interface (or at a different computer system) by contacting the process engine through the different user interface, and receiving rendering information configured for the different user interface. Thus, the user can stop and start work on a process however desired, and with whatever tools are available at any given time.

Abstract: Systems and methods that dynamically reset a workflow state by employing a dynamic state manager that is external to the workflow, and enables interaction of a host with a workflow instance. An event driven workflow or state machine workflow can be supplied, wherein ad hoc events are employed to reset and manipulate the workflow to states that have not been modeled as part of the workflow itself, to dynamically create relation ships at runtime.

Abstract: Computer components may be installed and configured using virtual machines, where a trusted relationship with a virtual machine is created when a virtual machine is launched on a device with an installation manager. The installation manager may provide configuration options, scripts, and other information to a configuration agent operating in the virtual machine. Additional virtual machines may be launched on other devices and trusted relationships established with the installation manager, which may also manage configuration agents on the additional virtual machines. In some embodiments, a remote controller may be used to control functions of the installation manager.

Abstract: A security management system uses several security scenarios that have rules defining the configuration of system and security components in order to meet a specific security scenario. The rules may include an evaluation of multiple components to give a summary statistic or evaluation, as well as rules that may be used to configure the various components to achieve a desired level of security. A management console may aggregate multiple security scenarios together for administration.

Abstract: A publication/subscription distribution mechanism receives alerts from an enterprise monitoring system, formats the alerts into a task capable of being managed by a task management application, categorizes the task into one or more subscription categories, and distributes the tasks to subscribers for the subscription categories. The distribution mechanism may automatically translate between an enterprise monitoring system and several different task management applications and may enable automated tracking of error conditions and their resolutions from detection to completion.

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 failure identification routine uses a two pass stack trace analysis in conjunction with a list of called types. As each method is called, a call list is generated with the called type, method, and various metadata. During the first pass stack trace analysis, each stack frame is analyzed to determine if the failed type is included in the stack frame. If so, the method associated with the frame is flagged as suspect. If the failed type is not found in the first stack trace, a second pass stack trace analysis is performed and an assembly associated with the method associated with the stack frame is analyzed to determine a set of types. The set of types are analyzed to find at least one match with the called types. If a match exists, the methods associated with the matched types are flagged as suspect.

Abstract: A monitoring and management system may use a plugin mechanism to add or update an interface to a managed service or device. The plugin may have capability to interface with the managed service or device, as well as an interface to a status database that may be populated by the managed service or device as well as other services or devices. The plugin may have rules that may be used to determine a status for the monitored service or device based on the statuses of several services or devices, and may also have rules that define a multi level query into the database to determine those services and devices.

Abstract: One or more users can execute tasks in a guided process involving dependent and independent steps modeled with parallel processing techniques. For example, a user can open one or more parent pages in a guided process through a user interface, where each of the one or more parent pages lists several items (e.g., child pages) to be completed. Each listed item (i.e., child page) may or may not depend on processing of another child page, or of another task on the parent page itself. As the user (or multiple users) completes the various items on each given parent page according to page-specific definitions, each parent page is rendered anew to show what has been completed and what remains to be completed. Thus, the parallel execution of tasks can be combined with the sequential execution of other steps to provide an integrated experience to the end user.

Abstract: A method for organizing task data used in customer relationship management systems in which task data is decomposed into a set of business activity classes including a set of business task classes, where the business task classes are combined through association or multiple inheritance to create the business activity class. Each task class can be further decomposed into a base task class and a set of task characteristic classes where task definitions may be modified by associating additional task characteristic classes to the base task class.

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 method for enabling an existing business workflow tool to extend application functionality through the use of external components and for providing a business abstraction layer that lowers a user design barrier.

Abstract: Installation of multiple servers with interdependencies is done in parallel steps, with each server advancing in sequence with other servers. When a second server is dependent on a first server during the installation process, the first server may finish a task and send a message to the second server to attempt an installation step that depends on the first server. If a problem occurs, the second server may revert to a configuration state before the attempted step and the first server may reattempt the installation step on which the second server depends.

Abstract: A traffic manager may monitor network performance, detect that the network performance has changed, and may prioritize network traffic based on which application or function is associated with the traffic. Each packet of network traffic may be analyzed to determine a source application or source function and allowed or disallowed along the network based on a set of predetermined priorities. Several sets of priorities may be established for various network performance conditions. In some embodiments, traffic may be routed along different paths using the sets of priorities and the source application or function. The traffic manager is adaptable for web-based services, applications, or other functions provided over a network connection.

Abstract: A scripting model may include links to web based services by including an interface associated with each web based service. The interface may perform various functions used to exchange information with a web based service, such as discovery, addressing, connection, configuration, authentication, and other functions. The web based service may be used in a similar manner as a local service within the scripting model, including automatic memory management, bounds checking, data translation, and other features of scripting.

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 setup workflow may be defined in a complex workflow manner that may have branching, error compensation, and relationships defined between a software product to be installed and previously installed or future products that may be installed. As a setup workflow operates, a remote device may be contacted for an updated setup step that may also include relationship definitions between the new setup step and other steps or installed components. The new step may be for a remotely provided service that may be used in lieu of a locally installed product. The setup workflow may include dependencies and coordinate setup workflows across multiple devices.

Abstract: A query for a help system includes data about a user system and a task that the user is attempting. The query may be used by a search engine to generate relevant results to aid the user. The user system data may include configuration data about hardware and software. The task data may be derived from the current state of a device, or from operational history that may be developed from a single user or a group of users. The query may have a mechanism to weight various keywords or components of the query and a feedback system may adjust the weights for future queries.

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.