8 years ago
DFSR Replication Backlog
XKJNGZ
Uses Powershell to make WMI queries to get the current backlog file count for each outbound DFSR partner on each DFSR share. These queries can be expensive if the backlog is large, so...
and... to the most recent question posed... in order to test errors in active discovery, I'll often use a:
try { Normal Code Goes Here -erroraction stop } catch { write-output "$($error[0])##1##1" }
to force the error output to the discovered instances screen... it's also ugly, but works. $error is a stack, newest gets pushed onto the top and can always be referenced as index [0]
Why not just run the posh in the collector debug console?
FR: LM, please make a VSCode plugin for collector debug script execution.
I have had that behave differently in the past due to potential credential issues, but !POSH debug is part of my deeper troubleshooting if it doesn't work from within the DS interface.