Microsoft Technology Licensing, LLC

Bruce Wayne Copeland

David C James

Rajagopalan Badri Narayanan

Zhengkai Kenneth Pan

Michael Joseph Healy

Khuzaima Iqbal

Michael L Davis

Jonathan I Shuval

Or Ben-Natan

Atul Adya

Abolade Gbadegesin

William Michael Zintel

David C Steere

Dustin Michael Ingalls

Jeffrey A Sutherland

Viraj B Mody

Jeffry B Phillips

Donald Y Song

Joseph S Calabig

Thomas W Kleinpeter

Galen Clyde Hunt

Robert M Fries

Alastair Wolman

Robert Victor Welland

John David Dunagan

Bassam Tabbara

Ashvinkumar J Sanghvi

Aamer Hydrie

Rene Antonio Vega

Vinay Deo

Anders Bertil Vinberg

Raymond W McCollum

Geoffrey Hugh Outhred

John M Parchem

Vij Rajarajan

Efstathios Papaefstathiou

Jeremy Lee Dewey

Rob M Mensching

Vitaly Voloshin

Gaurav Raghu Dhawan

Rajesh Viswanathan

John H Wilson

Mazhar Naveed Mohammed

Jonathan C Hardwick

Thomas A Galvin

Eric Joseph Winner

Mel MacMahon

Kevin Andrew Chan

Alexander E Mallet

Anand Lakshminarayanan

Jeffrey A Woolsey

Shafqat U Khan

Edwin R Lassettre

Adrian Maziak

Kevin D J Grealish

Aakash Kambuj

Robert T Wickham

Adam D Welker

Andrew Ness

Jeff Young

Yasser Mufti

Bippen Bisht

Christopher Rickman

John Carleton McCullough

Paul Joseph Lyman Schottland

Martin Napier Dey

Daniel Nicholas Joseph Drew

Doyle S Cronk

Clients may subscribe to resources for the purpose of receiving notifications of changes in the resource (e.g., a file is added to a shared folder). Storing subscriptions within persistent storage provides data security in the event of a service failure, at the cost of high latency in accessing subscription data. An efficient method for tracking a resource is provided herein. A subscription service creates subscriptions and monitors resources for a client. Upon a subscribed resource change, a notification service stores a notification of the change into a queue associated with the client. Efficient resource tracking is achieved because notification and subscription data is stored in low latency soft memory. The notification service is configured to detect a failure in the notification service and/or subscription service. In the event a service fails, the client provides a recovery mechanism by resubscribing to resources with which the client has an interest.

Resource tracking

A method, system, and architecture for managing computer systems is provided. A management system employs management objects (MOs) to provide administrators the ability to intuitively express the administrative intent in an information technology (IT) environment, and to act out the administrative intent based on the information gathered by the management system. Managed elements of an IT environment, such as, by way of example, hardware components, software applications, software updates, software distribution policies, configurations, settings, etc., may be expressed as MOs. Actions, such as, by way of example, detect, install/apply, remove, remediate, enumerate, etc., may be associated with the MOs. The management system manages the computer systems by deploying the appropriate MOs and their associated actions onto the computer systems, and performing the actions on the computer systems.

Object-based computer system management

One or more techniques and/or systems are disclosed for efficiently storing metadata of partitioned data (e.g., directed to a specific individual/user). A first subset of data is identified from the set of partitioned data. The first subset of data comprises data that has a high frequency of access, and may be identified, at least in part, by frequency of access metadata that is associated with the data in the set. Metadata, such as discovery information, permissions, version info, etc., that is associated with the data in the first subset can be stored in low latency (e.g., fast) storage, proving more efficient access. Metadata associated with data from the set of partitioned data that is not in the first subset (e.g., that is not accessed frequently) can be stored in higher latency (e.g., slower, less expensive) storage.

Efficient metadata storage

One or more techniques and/or systems are disclosed for providing resource authorization to users of a distributed memory store (e.g., a distributed web-based cloud service). A session ID that identifies a location of an authorization document in a distributed memory store is used to access the authorization document, which comprises a global section with a principal ID related to a user. The user can be authorized to utilize a resource (e.g., in a distributed cloud service) if a resource section is present for the principal ID in the authorization document, and has appropriate resource data for the resource. If the resource section is not present, it can be created in the authorization document, and identified by a resource identifier. Authorization data can be loaded into the newly created resource section, and the authorization document, with the global and resource sections, is saved to a local cache for the distributed memory store.

Distributed services authorization management

One or more techniques and/or systems are disclosed herein for aggregating web-based data stored in a distributed data store so that it can be retrieved in a first-in, first-out (FIFO) manner. A unique aggregation key is generated for respective one or more data generated from a web-based event, where the one or more data are added to the distributed data store, and the aggregation key corresponds merely to the data generated from the web-based event. The one or more data from the web based event is aggregated in a FIFO queue and stored in a same partition of the distributed data store, based on the aggregation key.

Aggregating data from a work queue

Clients may subscribe to resources for the purpose of receiving notifications of changes in the resource (e.g., a file is added to a shared folder). Storing subscriptions within persistent storage provides data security in the event of a service failure, at the cost of high latency in accessing subscription data. An efficient method for tracking a resource is provided herein. A subscription service creates subscriptions and monitors resources for a client. Upon a subscribed resource change, a notification service stores a notification of the change into a queue associated with the client. Efficient resource tracking is achieved because notification and subscription data is stored in low latency soft memory. The notification service is configured to detect a failure in the notification service and/or subscription service. In the event a service fails, the client provides a recovery mechanism by resubscribing to resources the client is interested in.

Consistency is managed among data operations by coalescing commit operations, adjusting a commit rate to optimize latency, and converging to fairness across servers. Write operations representing a change to data stored by one or more of a plurality of computing devices are received in succession by, for example, a cloud computing service. A state of a plurality of tracking objects is adjusted to indicate whether the change in data has been provided to the computing devices and whether the change in data has been acknowledged by the computing devices. Changes to the same data are coalesced such that only the most recent change is provided to the computing devices for storage. In some embodiments, the commit rate is adjustable such that the commit rate decreases quickly but increases slowly based on measured latencies.

Commit rate management with decoupled commit operations

In accordance with certain aspects of the model-based policy application, each of a plurality of policies is associated with appropriate parts of a model of a heterogeneous system. A deployment agent is invoked to apply each of the plurality of policies to components associated with the parts of the model. An identification of a change to one of the plurality of policies is received, and the deployment agent is also invoked to apply the changed policy to selected ones of the components associated with the parts of the model.

Model-based policy application

The disclosed arrangements and procedures replicate source files across networked resources. Specifically, a server receives a package update notification corresponding to a difference between a previous set of source files and one or more new sets of source files. Responsive to receiving the package update notification, a delta set of source files that correspond to the difference are identified. A set of source and/or distribution servers in an enterprise network that are configured for delta replication is determined. The identified delta set of source files is communicated to the determined source and/or distribution servers.

Delta replication of source files and packages across networked resources

The present invention provides a system and method of installing software updates to computing devices connected to an enterprise network. More specifically, the present invention provides a system and method of installing software updates based on input received from a system administrator or similar entity. When a command to install a software update is received, the present invention obtains the requested software update from a download center and causes the software update to be transmitted to client computing devices that need the functionality provided by the software update. Then the software update is installed in accordance with the input previously obtained from the system administrator.

System and method of installing software updates in a computer networking environment

A method and system to remotely install management software on client machines of a network without requiring user-intervention such as a logon. A data discovery manager determines which discovered machines in a network should be configured for client installation, and queues a client configuration request (CCR) for each such machine. A client configuration manager dequeues each CCR, and attempts to establish a connection with the remote machine corresponding to the CCR. If successful, a bootstrap install service is downloaded to the client machine from a server having administrative rights, after which the bootstrap service is run to install the remainder of the management software on the client machine from a client access point server. If unsuccessful, retries may be attempted. Client machines having users with sufficient security rights may install the management software via a logon or other process at the client machine.

Method and system for remote client installation

A computer-based uniform data interface (UDI) system for accessing in a uniform manner data from a data source with an arbitrary organization. The UDI system provides a UDI application programming interface (API) with functions for creating and accessing data organized into containers that contain one or more folders. Each folder optionally contains sub-folders and scalars. The UDI system also provides a UDI registry for registering types of containers and folders supported by a data source, for enumerating the types of containers and folders supported by the data source, and for instantiating container and folder objects corresponding to the data of the data source. A UDI mapper is provided for registering with the UDI registry types of containers and folders that represents the data of the data source, for instantiating in memory container and folder objects of the registered types, and for populating an instantiated container object with folders representing the data from the data source that is within the container. An application program invokes the UDI API functions to access data of data sources with arbitrary organizations.

Method and system for filtering in a uniform data interface

Computer-based uniform data interface (UDI) method and system using an

A method and system for consolidating related error reports is provided. In a preferred embodiment, an facility preferably implemented in software ('the facility') receives error reports and success reports generated by programs. When the facility receives a novel error report specifying an error source for which no error state is set, it sets an error state corresponding to the error report. The facility also preferably generates a consolidated error report at this point, which is delivered to a error state reporting subsystem. The error state reporting subsystem may add the consolidated error report to an error log and/or display it to a user. When the facility receives a redundant error report specifying an error source for which an error state is already set, the facility preferably does not set a new error state, nor does it generate a consolidated error report. When the facility receives a success report specifying an error source, it clears any error states that are set for the specified error source, and preferably generates a consolidated success report. The performance of the facility is preferably optimized by processing success reports asynchronously.

Method and system for consolidating related error reports in a computer

Growing community of inventors

Redmond, WA, United States of America

Bruce Wayne Copeland