Netherlands: Software

Introductie Windows Server 2016

Issue link:

Contents of this Issue


Page 31 of 173

24 C H A P T E R 2 | Compute Troubleshooting an event such as this took time because you had to look at it in broad terms before you could focus on a specific area and narrow down the problem. In Windows Server 2016 Technical Preview, events are updated to include the specific error. So, if the error is due to one of the reasons mentioned in the list, you are notified of the error and can immediately focus on that one cause. This makes for quicker resolutions because you do not need to troubleshoot a problem that does not exist. Also, additional checks have been added for the network name to help prevent a problem that might not occur for days or weeks. During every online/offline of the resource and every one hour that the name is online, Windows Server 2016 Technical Preview checks for the following: A searchable domain controller A synchronized Cluster Name Object (CNO) password A CNO in Active Directory that is turned on An existing CNO and Virtual Computer Object (VCO) in Active Directory Windows Server 2016 Technical Preview also includes several additional tests in cluster validation for network names to do the following: Check that the CNO and VCO are greater than 15 characters Verify that the CNO has Create Computer Object permissions in the Organizational Unit (OU) in the Active Directory of which it is a member Ensure that it is possible to sign in to the CNO and corresponding VCO Confirm that the local Users group on the nodes has the members CLISUR and NT AUTHORITY\Authenticated Users The previous items are commonly the cause of issues with network names, which is why these new diagnostics were added. Cluster Operating System Rolling Upgrade Windows Server 2016 Technical Preview introduces a wonderful new method for upgrading the operating system of your server clusters with no downtime and dramatically reduced effort. This feature is called the Cluster Operating System Rolling Upgrade. Cluster operating system rolling upgrades initially will be limited to Hyper-V clusters and scale-out file servers (SOFS) clusters for Windows Server 2016 Technical Preview. Until now, the cluster administrator was tasked with developing a detailed migration plan to update clusters with a new operating system. Often, administrators waited to move a cluster until new hardware was brought in as part of a system refresh. This often meant several years without any new capabilities for the cluster and some planned downtime for moving services between the old and new cluster. Cluster Operating System Rolling Upgrade does not require the purchase of any additional hardware; the upgrades are done in place to each of the nodes. The cluster itself never needs to be stopped or restarted; the work takes place at the cluster node level, and all services remain online during the rolling upgrade process. Unlike typical cluster migration strategies, you do not need to make a new cluster. The existing cluster objects, including cluster name and cluster IPs, remain the same and online during the upgrade. Even better news is that you can fully reverse the process until the Cluster Functional Level attribute is changed. (More on that later.)

Articles in this issue

Archives of this issue

view archives of Netherlands: Software - Introductie Windows Server 2016