![]() ![]() ![]() Speaking of clusters, most businesses I speak to tend to keep the number of nodes in their clusters relatively low (six, eight, 12 and 16 nodes), even though the max number of nodes is 64, and instead have more clusters. This definitely adds flexibility around Hyper-V clusters and their domain status. Using just two PowerShell cmdlets you can remove the cluster name account from the original Active Directory domain, shut down the cluster functionality, unjoin from the source domain and add all nodes to a workgroup, then join them to the new domain and create new cluster resources in the destination AD domain. One of the biggest gripes I hear from cluster administrators is the difficulty of moving a cluster from one domain to another (mergers is a common cause of this) this is being addressed in 2019. This article is written on build 17650, released April 24, 2018. In this article I'll look at what's new in general and specifically for virtualization and containers in the next LTSC release, Windows Server 2019, due out in the second half of 2018 (a good guess is that it'll be released at Ignite in September). You need to have Software Assurance to use SAC releases, and they're only supported for 18 months, whereas the LTSC releases will have the normal five years mainstream support (new features and bug fixes), followed by five years extended support (bug fixes only). Since the release of Windows Server 2016 there are now two "tracks" of Windows Server: the Semi-Annual Channel (SAC), which puts out two releases a year (in Server Core - no GUI flavor only) and the Long-Term Servicing Channel (LTSC), which will come out every two to three years, just like Windows Server has for many years. In case you haven't kept up with the different Windows Server releases coming from Microsoft (and it is confusing), here's the TLDR:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |