SQL Server Configuration Manager changes effected via Central Management Server When using Central Management Server (CMS), under Central Management Server Actions, SQL Server Configuration Manager (SSCM) is an option.



When launched, the GUI reflects the information of the CMS. Apart from what the GUI shows, I'm hopeful that changes made will affect all CMS managed instances.

Can anyone confirm whether changes made here will effect all the managed CMS instances? If possible, this could save much time if all the actions of SSCM can be performed against all the CMS-registered instances.
Taken from SQLServerPedia:


  Manage Your Services Remotely
  
  Another big advantage of CMS grouping all your servers together in a single place is that you can administrate the SQL Services on the
  target box easily. To do this right-click on the instance name. On the
  submenu you have a couple of service-related options. Under the
  Service Control option you can quickly Start, Stop, Pause, Resume or
  Restart your SQL Service. Of note, this action only applies to your
  SQL Engine service so if you have SQL Agent Service running (which
  relies on Engine) you may need to manually restart that service
  depending on how you have your services configured.
  
  For a little more control over the services on the target system select SQL Server Configuration Manager from the menu selection. This
  opens your typical Configuration Manager console but difference being
  that it now shows you the services on the target server you selected.
  To verify this you can see the target server's name in parenthesis
  next to SQL Server Configuration Manager in the left hand window pane.
  From here you can look at and configure your various SQL Server
  Services such as the database engine, Reporting Services, SQL Server
  Agent or SQL Server Browser. Be aware, however, this remote management
  of configuration manager only works on SQL Server 2005 editions and
  above.