ryanries / adreplstatus Goto Github PK

I tested it in my crashtest domain, a very small environment. One forest, one domain. The domain/forest has a name like this: wintest.name.tld. The tool finds the domain. The log shows this. But nothing else happened. I'm logged in as domain admin of course.

The DNS-servers are not part of the domain. We use bind.

The domain controllers are Server 2019, the forest level ist 2016. I tried it on W10, W11 and in the DC what is the PDC Emulator.

Maybe I don't understand how it should work, but I expect, I click on the green arrow-button and the tool starts to collect data.

It would be great if the tool could also be scheduled to run silently and mail the log filtered on Error-Warning-All messages.

The "Show Errors Only" filter only works on child items if the parent node is already expanded

This is the default behavior of ObjectTreeView, currently working on seeing if it can be changed.

Another idea is to automatically expand all parent nodes when the user hits the "Show Errors Only" button.

Installed and ran 2 days ago without issue. Then tried to run next day and it shows 0% and then disappears and never counts up or starts. Tried on different machines, rebooted, same thing.

Provide links to troubleshooting KB articles like the old tool did

I work in Gov, I really love this tool. I do have a portion of my environment where I need to meet CMMC, which requires FIPs 140 which it looks like breaks your tool. Do you know if you ever plan on making that work in environments that have to keep that off for security concerns?

When loading in VS2022, there's a namespace being referenced called "BrightIdeasSoftware" that is missing. Is this an external component, possibly an old reference in the ObjectListView NuGet?

This is an old lab and the tombstone life has been exceeded on the chlid DC, interestingly I cant see the error in ist entirety because the widnows wont stretch enough. Would be good to have a "tips" style pop up on mouseover

I'm testing the tool today in our production environment. It's DC-Patch Day, so it's a good opportunity to see how it works.

For now, it works fine.

In our environment we have sometimes problems with the name resolution where it can be helpful to ping explicitly IPv4 or IPv6, like this:

ping servername -4
ping servername -6

It would be cool to have this choice in the tool too.

Barbara

Hello,
thank you for your great work.
It would be of some help, into very large and complex environment. to be able to select only a specific
subdomain and not the entire forest.

Regards,
Red.

Great job on the release today.

Do you know if there are any plans to support 4.8.1. ? I work in a very regulated environment that involves going thru a large amount of pain for an air gapped network, and the machine I generally run on has 4.8.1.

Idea: Add right-click context menus so when you right-click a DC, it brings up commands like RDP, ping, Enter-PSSession, etc.

Is it possible to suppress errors for RODCs when they are intentionally not-reachable from a particular DC?
I'm not sure if you can do site and site-link lookups to determine which RWDCs those RODCs are actually allowed to talk to.

I honestly haven't found a great tool that shows RODCs are replicating properly. I believe even the CLI tools show errors because not all RWDCs can talk to all RODCs.

Would be a nice-to-have feature.

Thanks for updating this tool!

Discovery can be slow in environments where DCs are offline or unreachable.

In a test environment with about 150 DCs scattered around the globe, with about a dozen of those DCs being unreachable and causing connection timeouts, discovery takes around 20 minutes.

I feel this could be improved by breaking up the total number of DCs to scan into chunks and using multiple worker threads to break up the work.

But in addition, connection timeouts need to be adjusted if possible so we don't wait so long for a timeout if the DC is unreachable.

As per your request:

Hi, there is a problem with the port tester in version 1.3

when you select Kerberos it performs a test on port 53 (DNS)
when selecting DNS it performs a test on port 3268 (GC)
when GC is selected it performs a test on port 3269 (GC SSL)
when GC SSL is selected it performs a test on port 88 (Kerberos)

Can you have a look ?

Thanks,
Jonathan

Add a way to specify domain controller in cases where DCLocator chooses a DC that is unreachable

The original replication tool never supported AD LDS instances, unfortunately- it would be wonderful if this one did!