Bug found in Deploy a domain controller and member using Windows Azure Virtual Machines. With fix

I have been working with the script found at http://gallery.technet.microsoft.com/scriptcenter/Deploy-a-domain-controller-2ab7d658 as a base for my azure deployments. I ran into a situation where if a VNetwork already had a DNS entry it wouldn't allow you to add another DNS entry. It would give an error similar to  

Property 'DnsServersRef' cannot be found on this object. Make sure that it exists.

This happened at line 447 of the original script.

Line 447 looks like:

$dnsServersRefElement = $foundVirtualNetworkSite.DnsServersRef 

I fixed the error by adding .node after $foundVirtualNetworkSite. Like this:

$dnsServersRefElement = $foundVirtualNetworkSite.Node.DnsServersRef 
I hope that this gets fixed in the original script or that my post helps someone in the future.
January 12th, 2014 3:18am

Please post comments and fixes to Gallery scripts by posting in the Gallery Q&A section for the referenced script.  THe owner of the script will be monitoring that but not this forum. Also other using the script will be alerted to your discovery.

Here is the Q&Apage link: http://gallery.technet.microsoft.com/scriptcenter/Deploy-a-domain-controller-2ab7d658/view/Discussions#content

Free Windows Admin Tool Kit Click here and download it now
January 12th, 2014 3:46am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics