I have a 3-node, multi-instance Always On cluster is 2014 SP2 CU 10. Two local synchronous replicas, and one remote async replica. I impulsively ran SP2 CU13 executable on the primary. I expected the exe to prompt me for which of multiple instances to update, however, the exe ran and completed. At first I thought/hoped it just ran a system validation. The resulting HTML "System Configuration Check" just reports a list of "Checks" and "verifications". At this point, I'm not sure if it just did the checks, or if it applied CU13 on all the instances. Some of the AGs show critical and cautionary warnings in dashboard (but some don't). Not sure if there were sync issues prior to me running CU13 exe. When i refresh the connected instances in SSMS, they still show CU 10. I don't want to restart any instances until I know whether CU13 got applied. Assuming the worst that I indeed appplied CU13 on the primary out of order What is your guidance on next step, and how to recover if necessary. Also, should the CU13 executable have prompted me for which instance to update, or all get updated? Thanks.
Update...
The results dialogue after running the CU13 exe is as follows:
Setup administrator... Passed
Restart computer... Failed
Windows Management Instrumentation (WMI) server... Passed
Consistency validation for SQL Server registry keys... Passed
Not clustered or cluster service is up and online... Passed
Cluster group owned by local computer... Passed