我有一个域控制器设置在Azure中的VM，和一对夫妇的其他服务器也设置为虚拟机。当我架设服务器的虚拟机，我配置的DNS和WINS指向DC的IP地址，并加入了他们的领域。但是，这些设置不会关闭（其中VM被释放）生存。当虚拟机启动备份，DNS和WINS是空的，而且域认证不起作用。

I have a domain controller set up in an Azure VM, and a couple of other servers also set up as VMs. When I set up the server VMs, I configured DNS and WINS to point to the IP address of the DC and joined them to the domain. However, these settings don't survive a shutdown (where the VM is deallocated). When the VM is started back up, DNS and WINS are empty, and domain authentication does not work.

我看，我应该通过PowerShell的命令行开关配置新的虚拟机，专门设置了域名加入。我试过了，也许我有一些错误，但没有奏效 - 在新设置的虚拟机并没有加入到域，并且没有DNS / WINS设置为指向域控制器

I read that I should provision new VMs via PowerShell commandlets, specifically setting up domain joining. I tried that, and maybe I got something wrong, but it didn't work -- the newly provisioned VM was not joined to the domain, and did not have DNS/WINS set to point to the domain controller.

在任何情况下，我的问题是：有没有什么办法来重新配置现有的虚拟机，通过关闭保留网络设置或者是要弄清楚如何提供一个全新的VM要结婚域我唯一的选择控制器，然后从头开始？

In any event, my question is: is there any way to re-configure an existing VM to retain network settings through a shutdown or is my only option to figure out how to provision a brand new VM to be married to the domain controller, and then to start from scratch?

谢谢！

推荐答案

安东presents一个聪明，完全可行的解决方案，但我想知道究竟我做错了，因为微软的指导建议，它应该是完美的可以建立和维护一个Active Directory域在Azure云，而不把直流电转化为自己的子网。

Anton presents a clever and perfectly workable solution, but I wanted to understand what exactly I was doing wrong, because Microsoft guidance suggests that it should be perfectly possible to set up and maintain an Active Directory domain the in the Azure cloud without putting the DC into its own subnet.

在很多的试错法（主要错误），我终于弄明白。这不是有据可查的，所以希望这将帮助别人：

After a lot of trial and error (mostly error), I finally figure it out. This is not well documented, so hopefully this will help someone:

在Windows Azure中，云服务是另一个术语的应用程序，或一组这种规模在一起的组件。 A 云服务分配单个DNS名称和一个外部IP地址。在虚拟机的情况下，你通常有一个1：云服务和虚拟机之间的一一对应。你只当你想Azure的自动负载均衡和分发请求的虚拟机之间的云服务中添加更多的虚拟机到现有的云服务，对待他们，好像他们是之一。

In Windows Azure, cloud service is another term for application, or a set of components that scale together. A cloud service is assigned a single DNS name and a single external IP address. In the context of virtual machines, you typically have a 1:1 correspondence between a cloud service and a virtual machine. You only add additional virtual machines to an existing cloud service when you want Azure to automatically load balance and distribute requests among the VMs inside that cloud service, treating them as if they were one.

这使我想起我的错误。不完全理解了上面，我试图一个新的工作虚拟机添加到其中设置我的域控制器的云服务。这是不受支持的配置。一旦我了解，并正确配置一个新的虚拟机到自己的云服务，与域控制器的DNS服务器相关的，一切都工作正常。

This brings me to my mistake. Not fully understanding the above, I was attempting to add a new worker virtual machine to the cloud service in which I set up my Domain Controller. That is not a supported configuration. Once I understood that, and properly configured a new VM into its own cloud service, associated with the domain controller as DNS server, everything worked perfectly.