Configuring a VNet-to-VNet VPN Gateway Connection Using the Azure Portal

In the previous article, you have configured Azure VNet peering that connects Azure virtual network within the same Azure region through Azure backbone network. This time, you can use a VNet-to-VNet to connect Azure virtual networks in two different Azure regions. Using VNet-to-VNet is similar to a site-to-site VPN. In site-to-site VPN, traffic does traverse the internet but in VNet-to-VNet […]

Read more

Configuring Azure VNet Peering by using the Azure Portal

VNet peering is a mechanism that connects Azure networks (VNets) within the same Azure region through Azure backbone network. Once peered, virtual networks will work as a single network and resources can be accessed from both VNets via private IP addresses. VNet peering routes packets between virtual networks through the internal Azure backbone network. So VNet has not require Azure […]

Read more

Using the Azure Portal to Create Virtual Networks, Add Subnets and Setting up a DNS Server Address

Azure virtual network is the core component of Azure networking. It represents your own network in the cloud. Planning an IP addressing scheme within an Azure virtual network is similar to planning an on-premises IP addressing scheme. You can fully control your Azure network setting and define DHCP address blocks, DNS settings, security policies, and define routes to control network […]

Read more

Creating a Windows Virtual Machine and Availability Set at the same time using the Azure Portal

In this article, you are creating a new Windows virtual machine and Availability set at the same time using the Azure portal. An Availability sets provide redundancy to your application during downtime, such as during maintenance. We need at least two or more similarly configured virtual machines in an availability set. The primary purpose of an availability set is to […]

Read more
windowsServer2016

Remove a Node from a Windows Server 2016 Hyper-V Cluster and Destroy a Cluster Procedure

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
windowsServer2016

Best Practices on Setting up Hyper-V Cluster Networks in Windows Server 2016

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
windowsServer2016

Implementing Failover Clustering with Windows Server 2016 Hyper-V

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
windowsServer2016

Configuring iSCSI Storage and Initiator in Windows Server 2016

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
1 2 3 9