<div>
Yeah, I ended up retooling my whole script to run in cmd rather than Powershell.<br />
<br />
Thanks
</div>


Yeah, I ended up retooling my whole script to run in cmd rather than Powershell.

Thanks

<div>
<div class="content wysiwyg-content">
I'm using the following PS line to add conditional forwarders to hundreds of domains via:<br />
<br />

<pre><code id="code-10-28728339-1">Add-DnsServerConditionalForwarderZone -Name &quot;abc.def&quot; -ReplicationScope Forest -MasterServers 192.168.x.y</code></pre>
<br />
This works great on 2012R2, however in 2008R2 servers I get an error that the cmdlet is missing. &nbsp;If I run<br />
<br />

<pre><code id="code-10-28728339-2">Get-Command Add*</code></pre>
<br />
I can confirm that it's on 2012R2 and not 08R2 and seems to be a part of the DnsServer module. &nbsp;My question is, how can I get that module into 2008R2 so I can proceed with running this command? &nbsp;I have a centrally accessible NX server that I can store files on if needed and incorporate a mapping of a drive to copy in files if needed.<br />
<br />
Any help is appreciated.
</div>
</div>


I'm using the following PS line to add conditional forwarders to hundreds of domains via:

(CODE)

This works great on 2012R2, however in 2008R2 servers I get an error that the cmdlet is missing.  If I run

(CODE)

I can confirm that it's on 2012R2 and not 08R2 and seems to be a part of the DnsServer module.  My question is, how can I get that module into 2008R2 so I can proceed with running this command?  I have a centrally accessible NX server that I can store files on if needed and incorporate a mapping of a drive to copy in files if needed.

Any help is appreciated.

Cmdlet not in 2008R2 but in 2012R2

Windows PowerShell is a task automation and configuration management framework from Microsoft, consisting of a command-line shell and associated scripting language built on the .NET Framework. PowerShell provides full access to the Component Object Model (COM) and Windows Management Instrumentation (WMI), enabling administrators to perform administrative tasks on both local and remote Windows systems as well as WS-Management and Common Information Model (CIM) enabling management of remote Linux systems and network devices.

Powershell

A scripting language is a programming language that supports scripts, programs written for a special run-time environment that automate the execution of tasks that could alternatively be executed one-by-one by a human operator. Scripting languages are often interpreted (rather than compiled). Primitives are usually the elementary tasks or API calls, and the language allows them to be combined into more complex programs. Environments that can be automated through scripting include software applications, web pages within a web browser, the shells of operating systems (OS), embedded systems, as well as numerous games. A scripting language can be viewed as a domain-specific language for a particular environment; in the case of scripting an application, this is also known as an extension language.