US 12,135,961 B2
Operating system update management
Varun Murthy, Atlanta, GA (US); Jason Roszak, Brookhaven, GA (US); Saransh Bhatnagar, Bangalore (IN); Kalyan Regula, Alpharetta, GA (US); Shravan Shantharam, Cumming, GA (US); Blake Ryan Watts, St. George, UT (US); and Scott Kelley, Atlanta, GA (US)
Assigned to Omnissa, LLC, Mountain View, CA (US)
Filed by VMware LLC, Palo Alto, CA (US)
Filed on Apr. 29, 2022, as Appl. No. 17/732,728.
Application 17/732,728 is a continuation of application No. 16/403,649, filed on May 6, 2019, granted, now 11,334,338.
Claims priority of application No. 201941003120 (IN), filed on Jan. 25, 2019.
Prior Publication US 2022/0253302 A1, Aug. 11, 2022
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 15/173 (2006.01); G06F 8/65 (2018.01); G06F 11/30 (2006.01); G06F 11/34 (2006.01)
CPC G06F 8/65 (2013.01) [G06F 11/302 (2013.01); G06F 11/3409 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A management computer including a processor and memory, wherein the processor executes instructions stored in the memory to update an operating system (OS) executing on each of a plurality of client devices, by performing the following steps:
generating an OS update schedule for a first deployment group of the client devices and a second deployment group of the client devices, wherein the OS update schedule specifies an order for updating to a new version of the OS;
in accordance with the generated OS update schedule, transmitting to each of the client devices in the first deployment group, a command to update to the new version of the OS;
receiving behavior data from the client devices in the first deployment group, wherein the behavior data is representative of a behavior of the new version of the OS executing on the client devices in the first deployment group;
analyzing the behavior data received from the client devices in the first deployment group to identify an update incompatibility between the new version of the OS and at least one software component executing on the client devices in the first deployment group;
preventing each of the client devices in the second deployment group from updating to the new version of the OS, in response to identifying the update incompatibility; and
prior to instructing the client devices in the second deployment group to each update to the new version of the OS, transmitting instructions that are generated based on the update incompatibility, to each of the client devices in the second deployment group to update at least one software component executing thereon corresponding to the at least one software component executing on the client devices in the first deployment group.