AddsDeployment module with the -Whatif argument shows incorrect DNS results

Symptoms

You use one of the following Windows Server 2012 cmdlets from the Windows PowerShell AddsDeployment module:
  • Install-AddsForest
  • Install-AddsDomain
  • Install-AddsDomainController
However, incorrect results are displayed for the output for a Domain Name System (DNS) server when you use the -Whatif argument with these cmdlets.

For example, the output resembles the following:
PS C:\install-addsforest -whatif -DomainName corp.contoso.com SafeModeAdministratorPassword: ********* Confirm SafeModeAdministratorPassword: ********* What if: Create a new Active Directory forest with the name 'corp.contoso.com'. Configure this server as the first Active Directory domain controller in a new forest. The new domain name is "corp.contoso.com". This is also the name of the new forest. The NetBIOS name of the domain: Automatically calculated Forest Functional Level: Default Domain Functional Level: Automatically calculated Additional Options:   Global catalog: Yes   DNS Server: No Database folder: C:\Windows\NTDS Log file folder: C:\Windows\NTDS SYSVOL folder: C:\Windows\SYSVOL 
The password of the new domain Administrator will be the same as the password of the local Administrator of this computer.
Notice in this output that the install-addsforest -whatif cmdlet is used, and the entry for DNS Server is No. Despite this output, the DNS server is installed and configured as expected when the forest is created.

Cause

The promotion process calculates a DNS server installation automatically if you do not specify the -installdns:$true or -installdns:$false arguments. For a new forest, DNS server is always configured. For a new domain or for an additional domain controller in an existing domain, the DNS server is configured if the domain or parent domain Start of Authority (SOA) records are hosted in an existing Active Directory Domain Services (AD DS) zone.

However, the -whatif output is not displayed correctly in this automatically calculated case. The output is correct only when the -installdns argument is explicitly specified.

Resolution

You can safely ignore this issue. This issue is cosmetic and does not affect promotion operations.

More Information

This behavior is expected.
Properties

Article ID: 2737797 - Last Review: Sep 7, 2012 - Revision: 1

Windows Server 2012 Datacenter, Windows Server 2012 Standard

Feedback