Microsoft Technology Licensing, LLC

Travis Austin Wright

Vitaly Voloshin

Baelson B Duque

Marisol Ontaneda

Anand Lakshminarayanan

Abbot Moffat

Thomas Keane

Lorenzo Rizzi

Ferit Findik

Shawn Bice

Varsha Jayasimha

Casey McKinnon

Andrei Zenkovitch

Andrew Forget

Hakan Berk

Chandika Bhandari

Ashvinkumar J Sanghvi

Paul Adrian Oltean

Sahaj Saini

Benjamin Salim Srour

James W Truher

Alexander M Sutton

Corina Eva Feuerstein

James M Pinkerton

Brijesh D Bhatia

Stanislav A Oks

Ian C Jirka

Edhi Sarwono

Frank Zakrajsek

Mark Sterin

Vitaly V Filimonov

Jasraj Dange

Sai Gopal Kodi

Stephen O Wilson

Brett Eddy

Dale Koetke

Sandeep Phadke

Weiyun Huang

Stuart Padley

Chandika Bandari

Umachandar Jayachandran

William Maxwell Lerch

Michael Todd La Riviere

Jarupat Jisarojito

Performing a distributed query across a data pool includes receiving a database query at a master node or a compute pool within a database system. Based on receiving the database query, a data pool within the database system is identified. The data pool comprises a plurality of data nodes. Each data node includes a relational engine and relational storage. Each node in the data pool caches a different partition of data from an external data source in its relational storage. The database query is processed across the plurality of data nodes. Query processing includes requesting that data node perform a filter operation against its cached partition of the external data source stored in its relational storage and return any data from the partition that matches the filter operation.

Scale out data storage and query filtering using data pools

Techniques are described herein for customizing a form (a.k.a. a dialog) in a model-based system. For instance, the form may be customized without the need to modify the form in persistent memory, such as read-only memory (ROM), a hard disk, a magnetic disk, an optical disk, etc. A representation of a customization (e.g., an extensible markup language file, a management pack, etc.) regarding the form is captured in memory, such as a random access memory (RAM), and stored in a file or a database. For instance, the representation of the customization may be stored separately from the form. The representation of the customization is retrieved from the file or the database and applied to a rendering of the form.

Customizing a form in a model-based system

Described are systems and methods for instrumenting configuration and system settings based on targeting configuration settings at dynamically populated groups, groups with varied membership, and objects defined in a class. The systems and methods provide for attributing a configuration setting or policy to one or more objects and then targeting the object at one or more scopes.

Instrumenting configuration and system settings

One or more available command units can be represented with a computer output device. The available command units can be command units from one or more snapins, such as one or more snapins that include command units to be run with a shell application. User input can be received from an input device, the user input selecting one or more selected command units of the available command units. In response to the user input, source code can be automatically generated from the one or more command units, and the source code can be automatically compiled to generate one or more workflow activities.

Converting command units into workflow activities

Processes and techniques for tailoring operations management in a system are described. The processes and techniques allow a user to customize operations management based on the user's function within a system and the particular tasks that the user wishes to accomplish. Simplified user interfaces can be created by scoping the interfaces based on user profiles, preferences and system components.

Tailored system management interface

Described are systems and methods for instrumenting configuration and system settings based on targeting configuration settings at dynamically populated groups, groups with varied membership, and objects defined in a class. The systems and methods provide for attributing a configuration setting or policy to one or more objects and then targeting the object at one or more scope.

An authorization system determines a user's permission to access an object implicitly based on relationships in a data-driven model. The system provides the ability to mark a relationship type in the model between one object class (accessor) and another object class (accessed) as an implicit authorization relationship type. A user can define the permissions granted to the accessor object on the accessed object. When an accessor object tries to access a related accessed object over an authorization relationship type, the authorization system determines the permissions granted by inspecting the implicit authorization relationship type definition. The authorization system can also traverse containment relationship types to grant objects permissions contained by other objects. The authorization system dynamically determines authorization based on a relationship model that more naturally fits the actions that an administrator of a data-driven system is familiar with, and does not involve complex direct authorization or group membership management.

Model-based implied authorization

Management related data is provided to a user. Tags are attached to the provided management related data upon user instruction. A tag is way to identify a piece of management. The tags that correspond with the management related data are stored in a database of the management system.

Tags for management systems

One embodiment of the invention uses templates that define certain features of a given service type, wherein the features are common to all services of that service type. The template can be configured by a user to obtain a service definition for the given service. The service definition is passed to a programmability layer and provides enough information that the programmability layer can construct the various monitors, rules, classes and tasks required to monitor the given service without further customization by the user. In one embodiment, the user can also customize the service definition, a desired, in order to obtain additional monitoring.

Template based management system

In a management system, a management server authorizes users to access computing devices based on class space and instance space. The management server further determines whether users are authorized to use particular computing devices and/or applications provided by the particular computing devices. Alerts may also be provided to the users by the management server.

Authorization over a distributed and partitioned management system

A data feed is defined with a data type and criteria. Each data type corresponds to a type of management related data provided by a management system. The management system is searched for all management related data that corresponds with the data type and the criteria. An aggregator collects the management related data that corresponds with the data type and the criteria. The collected management related data is rendered for a display.

Data feeds for management systems

Systems and methods for playbook automation are described. In one aspect, a user selects operational knowledge associated with an application. The user associates one or more playbook-based tasks, playbook-based views, or playbook-based links with the operational knowledge. The playbook-based tasks, playbook-based views, and playbook-based links are for diagnosing, resolving, and/or verifying a problem associated with the application. The systems and methods generate an integrated management pack from the associated operational knowledge and at least one of the one or more playbook-based tasks, playbook-based views, or playbook-based links.

Playbook automation

Growing community of inventors

Issaquah, WA, United States of America

Travis Austin Wright