Quantcast
Channel: Azure Virtual Machines forum
Viewing all articles
Browse latest Browse all 12545

clarifying the procedure to create standalone vm with AD

$
0
0

I'd like to work through a problem in the procedure I'm using to make a virtual machine with active directory running as standalone server.

Basically, I was trying to interpret a tutorial, but I run into an error, similar to what another user experienced.

New-AzureVM : "An exception occurred when calling the ServiceManagement API. HTTP Status Code: 409. Service Management 
Error Code: ConflictError. Message: The specified DNS name is already taken.. Operation Tracking ID: 
2a29e309b6b1440e96f58d74b2c6a94a."
At line:30 char:1+ New-AzureVM -ServiceName $service -AffinityGroup $AG -VMs $MyDC -DnsSettings $my ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : CloseError: (:) [New-AzureVM], ServiceManagementClientException+ FullyQualifiedErrorId : Microsoft.WindowsAzure.Management.ServiceManagement.IaaS.PersistentVMs.NewAzureVMCommand

So I need help to clarify the order and the parts in the procedure I use:

1) I create a virtual network. In my case I created a network called jkl and a dns server called jkld.

2) then I run the script (about half way down on this tutorial)

In the script the relevant lines are

$myDNS = New-AzureDNS -Name 'jkl' -IPAddress '10.1.0.4'

$vnet = 'jkld'

So, is $vnet supposed to be the name of the dns server, as I had it?

And then, if the script runs but fails, and I run it again, and now it has the duplicate name, how would I go about clearing the slate so I can run the script without error?

Basically, how do I get rid of the pre-existing dns name, so the script can run?


Viewing all articles
Browse latest Browse all 12545

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>