将Windows 10 Azure VM加入Windows Server 2016 AD Azure VM

问题描述:

有两个资源组。 One Resource Group拥有Windows Server 2016,另一个Resource Group拥有两个Windows 10 VM。一个资源
组的VNet地址空间以11.0.0开始....另一个资源组的VNet地址空间以12.0.0开始....

所有三个虚拟机都可以使用RDP连接。

Windows 10 VM是否可以加入Windows Server 2016 AD VM?

我读了一些文章。这就是理论和技术上的原因,我知道,它可以完成,但实际上我不明白如何开始涉及的步骤。

我请求小组成员给我一个可以解释从开始开始的步骤的参考。

问候

InTechSys

InTechSys

InTechSys

您好,

您可以使用Vnet连接到Vnet在这种情况下,n或Vnet对等,

You can go with Vnet to Vnet connection or Vnet peering here in this scenario,

Vnet Peering:

虚拟网络对等使您可以无缝连接Azure虚拟网络。一旦对等,虚拟网络将显示为一个,以用于连接目的。对等虚拟网络中的虚拟机之间的流量通过Microsoft
骨干基础架构进行路由,就像流量在同一虚拟网络中的虚拟机之间通过专用IP地址路由一样。

Virtual network peering enables you to seamlessly connect Azure virtual networks. Once peered, the virtual networks appear as one, for connectivity purposes. The traffic between virtual machines in the peered virtual networks is routed through the Microsoft backbone infrastructure, much like traffic is routed between virtual machines in the same virtual network, through private IP addresses only.




VNet-to-VNet:

配置VNet到VNet连接是连接VNets的简单方法。当您将虚拟网络连接到具有VNet到VNet连接类型(VNet2VNet)的另一个虚拟网络时,它类似于创建到本地
位置的站点到站点IPsec连接。两种连接类型都使用VPN网关提供带有IPsec / IKE的安全隧道,并在通信时以相同的方式运行。但是,它们在配置本地网络网关的方式上有所不同。

Configuring a VNet-to-VNet connection is a simple way to connect VNets. When you connect a virtual network to another virtual network with a VNet-to-VNet connection type (VNet2VNet), it's similar to creating a Site-to-Site IPsec connection to an on-premises location. Both connection types use a VPN gateway to provide a secure tunnel with IPsec/IKE and function the same way when communicating. However, they differ in the way the local network gateway is configured.

加入DC:


确保虚拟网络你在Azure中创建的域控制器的内部IP地址已列出,请转到AZURE门户并选择CLIENT(END POINTS)所属的VNET转到DNS并将其从Microsoft DNS更改为Custom
并将其放入域控制器的IP。
Make sure that the virtual network you created in Azure has your internal IP address of the domain controller listed, please go to AZURE portal and select the VNET to which the CLIENT(END POINTS) belongs go to DNS and change it from Microsoft DNS to Custom and put the IP of the Domain Controller.