{"id":823,"date":"2017-08-23T06:55:14","date_gmt":"2017-08-23T04:55:14","guid":{"rendered":"https:\/\/www.em-soft.si\/myblog\/elvis\/?p=823"},"modified":"2017-08-23T06:55:14","modified_gmt":"2017-08-23T04:55:14","slug":"creating-vm-start-order-in-hyper-v-cluster-2016","status":"publish","type":"post","link":"https:\/\/em-soft.si\/myblog\/elvis\/?p=823","title":{"rendered":"Creating VM start order in Hyper-V Cluster 2016"},"content":{"rendered":"

Many times (or almost always), you have to define start order of VMs as services on one VM in an exactly defined order. We tried to solve this problem with start delays in the past \u2013 or with some additional software, but there were always situations where we are unable to control all factors.
\nNow in Windows Server 2016 edition it is better, as we can define startup groups. This means, that we define a group of servers who will start together and another group of servers who will start later when the first group is started or also with some delay after the first group is started. Additionally, we can start just a last group of servers and because this group depends on other groups, system will first start the parent server group. So, you are not able to start some servers before all infrastructure depends on it is started. We have new cmdlets in PowerShell to define and manage Cluster Groups (you can list them with Get-Command -Noun *ClusterGroup*<\/strong><\/em>).<\/p>\n

\"\"<\/a>
\nTo do these settings, you have to know some concepts that are introduced in Windows Server 2016 and we will use them.<\/p>\n