Missing directory objects

[MortenFagermoen]

When running the report creator (New-AsBuiltReport) it do find the directory objects (user, group and computer) in some of my AD's, but in some these sections just show up blank in the report. No error output when running in verbose mode. I have used the same command line and config files in all domains. (Just changed the credentials.)

I then let Claude convert the code in Get-AbrADDomainObject.ps1 to a file that could run separately and all data are found and showed nicely in the table format.

Any idea what can be wrong not getting the directory objects in the full report?

[rebelinux]

Could you run the report again in the domain where the condition occurs, and when it finishes, check the $Error variable to validate if there are any hidden errors?

$Error | more

[MortenFagermoen]

Thx for the reply. I uploaded the error output in the shown below. (This is from a member server, got the same when I tried on a domain controller to see if it changed anything.)

AsBuiltReport-$error.txt

[rebelinux]

This error appears constantly in the log:

Get-ADOrganizationalUnit: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-GPO: An operations error occurred. (Exception from HRESULT: 0x80072020)
Get-ADReplicationConnection: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADReplicationConnection: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADReplicationConnection: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADReplicationConnection: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADReplicationConnection: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-DnsClientServerAddress: No matching MSFT_DNSClientServerAddress objects found by CIM query for instances of the ROOT/StandardCimv2/MSFT_DNSClientServerAddress class on the  CIM server: SELECT * FROM MSFT_DNSClientServerAddress  WHERE ((InterfaceIndex = 5)) AND ((AddressFamily = 2)). Verify query parameters and retry.
Get-ADDomainController: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADDomainController: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADDomainController: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADDomainController: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADDomainController: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADServiceAccount: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADObject: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADFineGrainedPasswordPolicy: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Search-ADAccount: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Search-ADAccount: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADDomainController: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADDomainController: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADGroup: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADObject: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADUser: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADComputer: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADAuthenticationPolicy: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADAuthenticationPolicySilo: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
Get-ADTrust: Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.

Could you check if this cmdlet produces any errors?

Get-ADDomainController -Discover -Service ADWS 

I've seen this error when the account doesn't have the necessary permissions, or when the Domain Controller has replication or DNS problems.

[MortenFagermoen]

The command gave a valid output in the format below. I replaced the info for my server/domain/site, but it was all correct.

PS C:\Temp> Get-ADDomainController -Discover -Service ADWS

Domain : ReplacedDomainName.NET
Forest : ReplacedDomainName.NET
HostName : {ReplacedValidServerName.ReplacedDomainName.NET}
IPv4Address : 10.xxx.yyy.zzz
IPv6Address :
Name : ReplacedValidServerName
Site : ReplacedValidSiteName

[rebelinux]

I have no idea why it's not working in your environment :(

Could you send me the Get-AbrADDomainObject.ps1 that Claude modified?

[MortenFagermoen]

Get-ADDomainObjectStats.zip

Attached is the working code, works with both -DomainName and -DomainController as input.

[rebelinux]

Please validate if MokkaSchnalle recommendation fix your issue:
#169 (comment)

Looking into the Get-ADDomainObjectStats file i can't find way to duplicate or fix the issue.

[MortenFagermoen]

Thx for looking into it!
It did not solve my problem. If I find out how to solve it I will post it here.