Microsoft Technology Licensing, LLC

Gordon Hardy

Robert D Donner

Karvell Li

Sanjay Garg

Gregory Akselrod

Tianyu Xie

Chad R Shurtz

Curtis Dean Anderson

Loren Merriman

Scott Kurtzebom

Michael Paul Robinson

Scott Kurtzeborn

Jared W Wilson

Dipak Boyed

Alan T B Brown

Richard Wright

Xun Zhang

Christopher Callahan

Technology is disclosed herein for licensing applications using a preferred authorization process dynamically identified based on conditions associated with an initiation of an application. Authorization is then attempted using the preferred authorization process. In some examples, the preferred authorization process is selected from at least a keyless authorization process and a key-based authorization process.

Dynamic selection of authorization processes

Systems, methods, and software are disclosed herein for licensing applications using a preferred authorization process dynamically identified based on conditions associated with an initiation of an application. Authorization is then attempted using the preferred authorization process. In some examples, the preferred authorization process is selected from at least a keyless authorization process and a key-based authorization process.

Computing environments, each executing at least one software program, are monitored for failures occurring during execution of the software program. Information associated with the failure, such as an identification of the software program and a failure type describing the failure, is recorded. The failure information is quantified to report the number of times the software program has failed or the number of times a particular failure has occurred. The quantified data may provide help in prioritizing what program or what failures merit investigation and resolution. Reports may be received from failing computing systems stopped at a state following the occurrence of the failure. In response, hold information is checked to determine whether to instruct the failing computing system to hold a state existing upon the occurrence of the failure.

Tracking down elusive intermittent failures

Break and optional hold preserves a state of a computing environment on which a software program has failed. Being able to examine the status of the environment existing upon the occurrence of the failure, including the condition of various processes and values facilitates resolution of the cause of the failure. Upon occurrence of a failure during the execution of a first software program in a first computing environment, execution of the first software program breaks. A first state of the first computing environment existing upon the breaking in execution of the first software program is then held. A failure notification is generated to signal the failure to a monitoring system. The monitoring system accesses hold information to determine whether the first computing environment should hold its current state and whether one or more other computing environments interacting with the first computing environment should also hold their states.

Break and optional hold on failure

Growing community of inventors

Seattle, WA, United States of America

Gordon Hardy