 This demonstration shows applying a patch strategy to bring 1,000 sub-clouds back in sync. In the cloud overview, we can see that the sub-clouds are out of sync. Under Software Management, we go to the Cloud Strategy Orchestration tab. Click Create Strategy to open the dialog box. The strategy we are creating is a patch strategy, applied to sub-clouds in parallel to a maximum of 500 sub-clouds at a time. The Software Management tab is where patches and strategies can be built, configured, managed, and applied. Patch strategies may also be aborted or deleted here. The system controller is stage 1. The first group of 500 sub-clouds group 2 and the second group of 500 is stage 3. We can sort sub-clouds in various ways. We will now apply the strategy. Remember, the window must be refreshed to show the current status of the sub-clouds. The system controller has updated and the patch strategy has moved on to stage 2. After refreshing, we see that the state for stage 2 has moved on to creating strategy. Some sub-clouds have the patch strategy being applied and updating patches. This demonstration is applying a simple no-reboot patch and should progress quickly. More complex patches would require more steps when building the strategy, possibly migrating VMs and or hostlocks, and would save thousands of steps when being applied to thousands of sub-clouds. The patch strategies are in process on an increasing number of sub-clouds. Again, we must refresh the page to see the current status of our sub-clouds. Sub-cloud patching is starting to show as finishing or complete. We can filter for sub-clouds by name or the state of sub-clouds. Cloud strategy orchestration has many under-the-hood features to simplify and speed up the patch strategies implementation. We have effectively made changes on thousands of sub-clouds with a click of one button. We now see that all the sub-clouds have updated, implementing the patch strategy. Next, we delete the implemented strategy. We will now return to the cloud overview. As the system audits itself, some sync status has changed to in-sync after a refresh. All the sub-clouds have been audited and now show their status as in-sync.