What you need to do is install the Desktop Experience Go to the server manager and add new feature Find the Desktop Experience and add this you will need a reboot.
Get-Windows Feature *desk* install-Windows Feature -Name Desktop-Experience –Include All Sub Feature Now that we installed the Desktop Experience there is a new option if you do properties on the C drive.
If you are using SCVMM 2016, see Upgrading Windows Server 2012 R2 clusters to Windows Server 2016 in VMM for guidance on upgrading the clusters and automating the steps that are described in this document.
Complete the following requirements before you begin the Cluster OS Rolling Upgrade process: This section describes the various transition states of the Windows Server 2012 R2 cluster that is being upgraded to Windows Server 2016 using Cluster OS Rolling Upgrade.
In order for this cmdlet to succeed, all nodes must be Windows Server 2016, and all nodes must be online.
This section illustrates and describes the four different stages of a cluster with shared storage whose nodes are upgraded from Windows Server 2012 R2 to Windows Server 2016.
There are many optimizations in Windows Server 2016.
We have successfully upgraded Hyper-V and Scale-out File Server clusters with zero downtime in less than four hours total.
Figure 1: Cluster operating system state transitions A Windows Server 2012 R2 cluster enters mixed-OS mode when a Windows Server 2016 node is added to the cluster.Yes, before starting the Cluster OS Rolling Upgrade process, verify that all cluster nodes are updated with the latest software updates. Does Cluster OS Rolling Upgrade work for any cluster workload? Yes, Cluster OS Rolling Upgrade works for any cluster workload.However, it is only zero-downtime for Hyper-V and Scale-out File Server clusters.Figure 5: Final State: Windows Server 2016 Failover Cluster (Stage 4) This section describes the workflow for performing Cluster OS Rolling Upgrade.Figure 6: Cluster OS Rolling Upgrade Process Workflow Cluster OS Rolling upgrade includes the following steps: Although we are targeting Private Cloud scenarios, specifically Hyper-V and Scale-out File Server clusters, which can be upgraded without downtime, the Cluster OS Rolling Upgrade process can be used for any cluster role.
How long can the failover cluster run in mixed-OS mode?