concept multiserver job in category sql server

This is an excerpt from Manning's book Learn Windows SQL Server Administration in a Month of Lunches.
Multiserver management is a feature of SQL Server Agent, which means every SQL Server instance that you want to participate needs to have its SQL Server Agent service running. You’ll designate one SQL Server instance as your master server, and enroll one or more other instances as targets. When you run multiserver jobs, Agent will coordinate their execution on each target, and even track job progress for you, all in one central location.
I use multiserver jobs in a couple of different ways. One way is when I need to make a one-time configuration change across a large number of SQL Server instances. For that reason, I tend to have one instance of SQL Server that’s my “personal” instance; I’ll use it to host small databases that I use to track computer inventory information and other operational tasks. That instance becomes my master for multiserver jobs, and I enroll all of my “real” SQL Server instances as targets. That way, when I need to make some configuration change, I can write the necessary T-SQL statements into a job and then assign that job to all of the targets. Bam! Mission accomplished.
Another way to use multiserver jobs is for routine maintenance, such as updating index statistics, reorganizing indexes, and so on. I’ll admit that, although I’ve seen some administrators use a centralized multiserver job for those tasks, I don’t do it much myself. I tend to want those kinds of things customized on a per-instance or per-database basis, which eliminates multiserver jobs as a good option. But, they’re certainly an option for some kinds of routine maintenance, and you should keep them in mind as a possibility.