@EEdLoh Due to the the architectural design of the Alteryx Server there isn't a good way to centrally manage worker nodes. This is because each worker node is independent of the controller. This allows for a high degree of flexibility and stability as workers can come and go without impacting the controller. The primary drawback to this is that since the controller doesn't know anything about the worker nodes it isn't able to manage them or push configurations to them. This means each worker must be managed as an individual server.
As such the best option for ensuring identical configurations between the nodes is to make any changes via the Alteryx System Settings on one of the workers then copy the RuntimeSettings.xml file to the remaining workers. This will require a restart of the service on the workers in order to apply any changes but it should save some time as you can both push the config file and restart the service remotely. As for managing database drivers and other third party software the workers may need it should be done through whatever software management solution is deployed by your organization. Your software management solution should be able to push this software silently to the servers as needed with little or no interaction from you or any admin.
