MS Server Pro - Always a Step Ahead.
Failover clustering supports up to 64 nodes and 8000 virtual machines per cluster with 1024 virtual machines per node. In production environment you need to Add a Node to an Active cluster and sometimes remove a Node from the cluster. Even some scenario you need to destroy a cluster as well. Normally, when a node is damaged or no longer […]
Read more
There is no single best recommendation on how many networks a Hyper-V host should have, and different factors such as storage type, Hyper-V features used and virtualization load. Networks and network adapters are important parts of each Hyper-V Cluster implementation. You cannot configure a cluster without configuring the networks that the cluster will use. A Hyper-V Cluster needs multiple types […]
Read more
In the previous article, you have configured Configuring iSCSI Storage and Initiator in Windows Server 2016. Here you can configure Implementing Failover Clustering with Windows Server 2016 Hyper-V. A failover cluster is a group of two or more computers working together to increase the availability of a clustered services or applications. To make virtual machines highly available in Hyper-V environment, […]
Read more
In this article, you are configuring Windows Server 2016 Server as an iSCSI (Internet Small Computer System Interface) target server for the purpose of centralized storage for the Hyper-V Failover Cluster test environment. In the production environment, organizations are using NAS or SAN devices for the centralized storage for the Hyper-V Failover Cluster. Some small organizations, they are using Windows […]
Read more
In the earlier versions of Hyper-V host, after you have upgraded your Hyper-V host to a new operating system, VMs configuration version will be upgraded automatically as the Hyper-V host as soon as you moved the virtual machine. With Windows Server 2016, Hyper-V host will not automatically upgrade VMs configuration version. Instead, upgrading is now a manual process. With rolling […]
Read more
VM Load Balancing is a new built-in feature in Windows Server 2016 that identifies idle nodes in a cluster and distribute VMs to utilize them. This is achieved by analyzing the VM memory and CPU pressure of each node, and then VMs are Live Migrated to idle nodes with no downtime.
Read more
Cluster OS Rolling upgrade is a new feature in Windows Server 2016 failover clustering. If a Windows server 2012 failover clusters running the Hyper-V or Scale-Out File Server roles, you can add Windows Server 2016 nodes without taking the failover cluster offline. In earlier Windows Server versions, you had to create a new cluster with the new operating system on […]
Read more
Staring with Windows Server 2012, Microsoft discontinues Active Directory Domain Services Installation Wizard (dcpromo.exe) to install Active Directory Domain Controller. We can using Server Manager to install the Active Directory Domain Service (AD DS) role and run the Active Directory Domain Services Configuration Wizard to install Active Directory Domain Controller on Windows Server 2016. In this article, we are Installing […]
Read more
In the previous Exchange Server 2016 article, you have created a trusted certificate by creating a certificate request and submitting it to a CA. If you have multiple Exchange Servers 2016 in your environment, you need to export the same certificate and import it to the new Exchange Server 2016.Exchange Server 2016 consolidates all roles on the Mailbox Server, except […]
Read more
This is my third article on Migrating Active Directory Domain Controller. In the first article, I have written how you would migrating Active Directory Domain Controller from Windows Server 2003 SP2 to Windows Server 2008 R2. In the second article, I have written how you could migrating Active Directory Domain Controller from Windows Server 2008 R2 to Windows Server 2012 […]
Read more