none
Error on AD itself!!! 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 RRS feed

  • Question

  • I´m trying to run a simple powershell, trying to grab a list of Computers

    The weird part is: I´m running a powershell instance, with full administrative privileges and on the DC/AD itself!!!

    How can I see an error like that, running the command on AD/DC itself?

    So, the error is:

    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.
    At line:1 char:1
    + Get-ADComputer -filter {Enabled -eq $True} -properties Name,Enabled,O ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : ResourceUnavailable: (:) [Get-ADComputer], ADServerDownException
        + FullyQualifiedErrorId : ActiveDirectoryServer:0,Microsoft.ActiveDirectory.Management.Commands.GetADComputer

    The weird part is:

    When using the cmdlet, with screen outpu (no text output) it only shows a few computers at timne, let´s say, it shows 10, waits a little moment, more 10 and so on

    No matter how, exporting csv, TXT or sscreen, it´s very slow

    The cmdlet

    Get-ADComputer -filter {Enabled -eq $True} -properties Name,Enabled,OperatingSystem,OperatingSystemVersion,IPv4Address,Created,LastLogonDate,Modified,whenCreated,PasswordLastSet,lastLogonTimestamp,Description | ft Name,Enabled,OperatingSystem,OperatingSystemVersion,IPv4Address,Created,LastLogonDate,Modified,whenCreated,PasswordLastSet,@{Name="LastLogonTimeStamp"; Expression={[DateTime]::FromFileTime($_.lastLogonTimestamp).ToString('yyyy-MM-dd')}},Description

    Friday, June 5, 2020 6:10 PM

All replies

  • Hi,

    have you tried specifying the domain controller by FQDN using the -Server parameter, even if you're running the PowerShell session directly on that machine? Could be that your Sites & Subnets are broken or there's an old DC object lingering somewhere.


    Evgenij Smirnov

    http://evgenij.smirnov.de

    Friday, June 5, 2020 10:18 PM
  • Hi,
    Was your issue resolved? 
    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.
    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.
    If no, please reply and tell us the current situation in order to provide further help.
    Best Regards,
    Yang Yang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, July 3, 2020 3:30 AM