At WWDC, Apple could be unveiling a new i Pad with a 10.5-inch display and smaller bezels.
This i Pad is going to be roughly the footprint of the existing 9.7-inch i Pad Pro so it’s going to replace the small i Pad Pro in the lineup.
You can then have CAU “connect” to any failover cluster using appropriate administration credentials, and update the cluster on demand For an overview of the scenario, check out the CAU Scenario Overview.
For this blog post, I will focus on the first mode above: Self-Updating.
It could be a brutal end with Apple removing the i Pad mini from its stores.
But I think Apple will still keep the i Pad mini for a little while — it’s just going to slowly fade away.
Cluster-Aware Updating (CAU) is an exciting new feature that we have added in Windows Server 2012 that addresses precisely this gap.
It’s clear that both the entry-level i Pad and the i Phone 7 Plus (and phablets in general) have become more popular than the i Pad mini.
So Apple is just going to get rid of the i Pad mini.
At a high level, there are three things you need to do to get the end-to-end scenario working and operating seamlessly with your existing patching infrastructure such as Windows Server Update Services (WSUS), on a Windows Server 2012 failover cluster: 1.
Install CAU tools on the Windows Server 2012 (or Windows 8 Client) computer that you want to run it from. Configure self-updating on the desired failover cluster 3. Install CAU tools Installation of CAU is very easy: CAU tools are a part of Failover Clustering Tools.