What is a smarter way to Identify Windows Domain Controllers in Sites or Asset Groups dynamically?

The title pretty much says it all

I’m looking to find a smarter, more efficient way to dynamically identify Windows Domain Controllers in a site group or asset group.

ignoring hostnames and ip addresses

What about Servers listening on port 389 or 636?

1 Like