Using PS for DC Repl data

Welcome Forums General PowerShell Q&A Using PS for DC Repl data

Viewing 5 reply threads
  • Author
    Posts
    • #275439
      Participant
      Topics: 141
      Replies: 298
      Points: 526
      Rank: Major Contributor

      I’m digging into PS for getting useful replication data from DC’s and have access to all DC’s WinRM ports. However, when I attempt to run something like:

      ..the help file doesn’t allude to needing this to run via Invoke-Command. Why is it bombing?

    • #275442
      Participant
      Topics: 5
      Replies: 252
      Points: 998
      Helping Hand
      Rank: Major Contributor

      Did you put something in Target or just *?  Not sure if you were redacting it for posting, but I believe it is required and wildcards are not accepted per the documentation: https://docs.microsoft.com/en-us/powershell/module/activedirectory/get-adreplicationpartnermetadata?view=winserver2012-ps

       

    • #275445
      Participant
      Topics: 9
      Replies: 706
      Points: 2,837
      Helping Hand
      Rank: Community Hero

      @Mike, * is allowed.



      @Jeff

      Are you getting output from just

      My presumption is there is one or more servers that can’t be contacted. and that is why you’re seeing the message. If you run the above command and see output from some servers, perhaps you can see if any are missing.

    • #275451
      Participant
      Topics: 141
      Replies: 298
      Points: 526
      Rank: Major Contributor

      Hi Doug,

      Yes, your one liner does work without issue in our production domain but in our test domain, about half throw that error. I don’t believe it is WinRM because if I run Invoke-Command at them (en masse) I get output from all, no errors.

      What is it about this particular set of commandlets that can only return on half across our (TEST) Forest)

      • This reply was modified 1 month, 2 weeks ago by Jeff Taylor. Reason: clarity
    • #275460
      Participant
      Topics: 9
      Replies: 706
      Points: 2,837
      Helping Hand
      Rank: Community Hero

      Well perhaps like the error says

      or it does not have the Active Directory Web Services running.

      Are these 2008/R2 servers? Is AD Web Services running on all?

    • #275469
      Participant
      Topics: 141
      Replies: 298
      Points: 526
      Rank: Major Contributor

      All good Doug…I learned those servers were decommed recently so now hunting for stale DNS records since PowerShell is thinking they are still AD objects

Viewing 5 reply threads
  • You must be logged in to reply to this topic.