ttl;
The items here will mainly help you if you are doing one (or both, as I did) of the following:
1) Merging NPM and NCM servers
2) Going from NCM operations on your Primary (Core) server that is colocated NPM/NCM server to using your polling engines to perform NCM operations.
The main drive for all this work, which is widely mentioned and IMHO a good thing: No longer using Windows Task Schedular to run your tasks. It is now part of your core system.
Note: If you use items like the canned "Config Change Report" or the "Login Failure" report AND you change to running NCM operations on your pollers - then you will get a report from each poller that performs that has nodes which the operation needs performed on. So if your Group A nodes are spread out to pollers 1, 3 and 5 and you run a report against Group A - you will get three emails.
2nd Note: -- you may experience problems with jobs that run from different pollers (see the note above) that write the results to a single file location. Right now, I am seeing the job staying in a running state, and NOT write the results from both pollers to the single file location. First poller to run the job wins. I have a case open with support on this.