Powershell v3.0 pipe issue

Question

I'm having trouble with this command:

gc .\domains.txt | Get-ADDomain

As the name implies, domains.txt contains a list of Active Directory to query (all domains are in the same forest).

If I run it on my Windows 8 machine everything works fine and I get the expected results, instead on a Windows 2008 R2 SP1 member server (not a DC) with WMF 3.0 I get result only from the first domain in the list and for the others:

Get-ADDomain : A referral was returned from the server

If I query a domain in the list with:

Get-ADDomain <Domain name here>

it works fine.

My Workstation

Microsoft Windows 8 Enterprise (6.2.9200) x64

PS D:\Tools\Powershell> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      3.0
WSManStackVersion              3.0
SerializationVersion           1.1.0.1
CLRVersion                     4.0.30319.18010
BuildVersion                   6.2.9200.16384
PSCompatibleVersions           {1.0, 2.0, 3.0}
PSRemotingProtocolVersion      2.2

Server

Microsoft Windows Server 2008 R2 Standard SP1 (6.1.7601) x64

PS C:\Tools\Powershell> $PSVersionTable

Name                           Value
----                           -----
WSManStackVersion              3.0
PSCompatibleVersions           {1.0, 2.0, 3.0}
SerializationVersion           1.1.0.1
BuildVersion                   6.2.9200.16398
PSVersion                      3.0
CLRVersion                     4.0.30319.269
PSRemotingProtocolVersion      2.2

Update

If i run on the server:

gc .\domains.txt | %{ Get-ADDomain $_ }

it runs fine

TRACE

trace-command -Name ParameterBinding { "DOMAIN_1","DOMAIN_2" | Get-ADDomain } -PSHost

Server: http://pastebin.com/sRVJHaCU

Workstation: http://pastebin.com/kj3JV6nV

Thanks in advance

Is the first domain (on which it's working in Server 2008 R2) the domain this server belongs to ? — JPBlanc
no, the server belongs to a domain which return the error (using the pipe) — EsOsO
Do you double check the text file (no special characters at the end of the lines, unicode/ansi misfit) ? — JPBlanc
Try using Trace-Command to see how the parameter binding is failing e.g. trace-command -Name ParameterBinding { gc .\domains.txt | Get-ADDomain } -PSHost — Keith Hill
Trace from server: pastebin.com/sRVJHaCU Trace from workstation: pastebin.com/kj3JV6nV It seems like ActiveDirectory module is misbehaving on server. Actually the two machines point to different DNS; i'll try with same DNS servers. — EsOsO

MunkeyWrench MunkeyWrench · Accepted Answer · 2013-04-05T00:28:43

I found an article that may help.

http://technet.microsoft.com/en-us/library/ee617224.aspx

From the look of your script you are providing the server using the text file. Is it possible the problem is the Windows 2008 server you are running the PowerShell script on is not in the same domain or the user you are logged in as does not have access to the domains where the other servers are members?

snippet from the above article:

-If the Server parameter is specified and the Credential parameter is not specified: --The domain is set to the domain of the specified server and the cmdlet checks to make sure that the server is in the domain of the LocalComputer or LoggedOnUser. Then the credentials of the current logged on user are used to get the domain. An error is returned when the server is not in the domain of the LocalComputer or LoggedOnUser.

You might try adding the additional parameters for the Get-ADDomain commandlet such as -Identity, -AuthType, and -Credential

Get-ADDomain [-Identity] [-AuthType { | }] [-Credential ] [-Server ] []