Microsoft Technology Licensing, LLC

Bjorn Benjamin Levidow

Eric Benjamin Watson

Eugene Seichi Lin

Santosh Sharad Jodh

Lonny Dean McMichael

George Evangelos Roussos

Jason T Cobb

Mark Derbecker

Neil Scott Fishman

Yi Meng

Lingan Satkunanathan

Vadim Bluvshteyn

Vadim Bluvshtevn

Described is a technology by which a remote network (or local) service is monitored for failure, e.g., by determining whether data corresponding to operation of the service achieves a threshold. When a threshold is achieved that indicates that the service has failed, the service is automatically deactivated for use with a local workload, and the workload switched to use a second service or system having functionality similar to that of the failed service. The second service may be monitored for failure, as may the failed service to determine when it is again operational. In this manner, a remote primary service may have another local or remote secondary service/system automatically substituted for it when it fails, and be restored for use when it returns to acceptable operation.

Service resiliency within on-premise products

Provided is a system to automatically recover a computer system after a failed attempt, or failed attempts, to boot a target operating system on the computer system.

Automated recovery of unbootable systems

Aspects of the subject matter described herein relate to system state changes. In aspects, a state change monitor detects a state change, determines whether the state change is within a set of state changes that are monitored, and, if so, logs data regarding the state change. The data and any other data needed to rollback the state change is exported to other nodes. The other nodes may store the data for rollback or migration purposes and/or adjust their operation so that they may operate correctly in view of the state change.

Configuration replication for system recovery and migration

Systems and methods are provided that prevent faulty drivers from being loaded and/or can prevent faulty drivers from being installed. Thus, instability of a computer system can be mitigated. Additionally, the occurrence of data corruption, system halting and the like can be reduced. A requested driver is compared to a list of faulty drivers from a faulty driver database. If the requested driver is in the list of faulty drivers, the requested driver is deemed faulty or defective, and is prevented from being loaded. Additionally, if the requested driver is in the list of faulty drivers, the requested driver can be prevented from being installed. Otherwise, the requested driver is operable and can be installed and/or loaded.

Faulty driver protection comparing list of driver faults

Driver protection

Growing community of inventors

Bellevue, WA, United States of America

Bjorn Benjamin Levidow