1. Permission granted.
2. Copy and paste the script into ISE or a PowerShell prompt.

Thanks

Webster

1. Need permission to plagarize the script.
2. How do I run the script?

This is included in my AD documentation script starting at line 10620.

Webster

Actually looking back at other comments, several people have noted that. I thought I had removed it from the article.

Webster

Actually there is a ; in the line below
$ADDomainTrusts = Get-ADObject -Filter {ObjectClass -eq “trustedDomain”;} -Server $Domain -Properties * -EA 0

I removed it and it works.

Standard copy & paste error. Replace what looks like a – with what is on the same key as the underscore character.

Webster

I get the same error

Get-ADObject : Error parsing query: ‘ObjectClass -eq “trustedDomain”;’ Error Message: ‘Operator Not supported: ‘ at position: ’32’.
At line:6 char:27
+ … ainTrusts = Get-ADObject -Filter {ObjectClass -eq “trustedDomain”;} – …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ParserError: (:) [Get-ADObject], ADFilterParsingException
+ FullyQualifiedErrorId : ActiveDirectoryCmdlet:Microsoft.ActiveDirectory.Management.ADFilterParsingException,Microsoft.ActiveDirectory.Management.Commands.GetADObject

This is usually a copy and paste issue. Make sure all the “-“s in your script are real “-“s. Copy what you see as a “-” and then do a replace with the “-” from your keyboard. That always fixes the issue for me.

Thanks

Webster

Get-ADObject : Error parsing query: ‘ObjectClass -eq “trustedDomain”;’ Error Message: ‘Operator Not supported: ‘ at
position: ’32’.
At C:\scripts\Get-ADTrusts-v2.ps1:42 char:27
+ $ADDomainTrusts = Get-ADObject -Filter {ObjectClass -eq “trustedDomain”; …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ParserError: (:) [Get-ADObject], ADFilterParsingException
+ FullyQualifiedErrorId : Error parsing query: ‘ObjectClass -eq “trustedDomain”;’ Error Message: ‘Operator Not sup
ported: ‘ at position: ’32’.,Microsoft.ActiveDirectory.Management.Commands.GetADObject

From my PowerShell mentor Michael B. Smith:

The truth is, it doesn’t matter. The way you wrote it minimizes quoting requirements and it is the way all of the examples for the parameter are written. You do have an unneeded semicolon though. 

This is just the way PowerShell works. All of the below produce equivalent results:

{ this is a test }
“ this is a test “
‘ this is a test ‘

Using a quoted string is slightly more efficient the first time it’s executed, but based on the way PowerShell caches the AST it doesn’t make any difference on subsequent executions.

Note: AST = Abstract Syntax Trees

Thanks

Webster

should be

$ADDomainTrusts = Get-ADObject -Filter ‘ObjectClass -eq “trustedDomain”‘ -Server $Domain -Properties * -EA 0

Hi Rejone,

Not sure if your question was for Webster or myself.

I would expect this to be a host (Windows) firewall issue, but we would need more information from you before concluding that this is the issue:
– Are the VMs also in the child domain?
– Can the VMs communicate with the child domain controllers on other ports, such as LDAP, browse to the SYSVOL, etc?

As this question is unrelated to Webster’s script it’s probably a question that would be better posed on a forum so that others can join in the discussion to assist you.

Cheers,
Jeremy

Great info. We have an issue with a child domain. We recently deployed Citrix VDI and all of our virtual machines are not able to ping our child domain controllers. Have you seen this issue before? Any help would be appreciated.

Rejone

You may also want to report whether or not the trust supports AES encryption by examining the value of the msDS-SupportedEncryptionTypes attribute. If enabled the value is typically 24 (8 = AES 128 bit key length, 16 = AES 256 bit key length)

If it’s a forest trust, you’ll want to to get the Name Suffix Routing from the msDS-TrustForestTrustInfo attribute, which you can only do by examining the output of the “netdom trust” command.
– http://blogs.msdn.com/b/spatdsg/archive/2008/08/21/kerberos-domain-routing.aspx
– http://xitnotes.wordpress.com/2012/03/29/kerberos-in-an-active-directory-forest-trust-vs-external-trust/

Cheers,
Jeremy