Simplify on-premise data gateway software update

[Suman_Roche]

You can read below idea and up vote this Microsoft Idea

Make gateway version update simpler

The current process of updating gateway software is not effective or efficient for large enterprise with multiple gateway servers.

The process works like this.

1. Schedule installer via SCCM or PowerShell to update gateway software.
2. Log into each server and sign in to gateway software to make newer version show up in Power BI service

The above process can be fully automated by adding post install step to allow PowerShell script to run as either service principal or service account to sign into gateway software. This will streamline patching process and give better user experience.

[lbendlin · Accepted solution]

I strongly recommend against trying to automate this.  Very often the installer fails to restart the gateway service. As you probably know there is no downgrade option so you should hold back installing on production gateways until you are absolutely sure it is safe  (we usually wait two months after a release).

Yes, the gateway cluster member not reporting their updated version is a nuisance. But there is no real technical need to log in to the management interface as the service (once it is back up, that is)  will work just fine.  Mostly.

And don't forget the configuration changes you need to make to the various config files. After each upgrade you need to validate that these were not randomly overwritten.

I would rather like to see the option to clone connections across gateways. Both on the service and on the individual VMs  (ODBC, I am looking at you!)