An on-premises data gateway is software that you install in an on-premises network. The gateway facilitates access to data in that network.
If you have installed the gateway already and are looking forward to updating it to the current version released by Microsoft, then this section is for you. I am trying to highlight the steps that I have implemented in my organization which can help to provide the one-place reference for you to update your gateways.
I have used the November 2019 update from Microsoft while working on this blog, and Microsoft may change the steps in the future, but they can still be used as a reference, as per my understanding.
.NET Framework 4.6 (Gateway release August 2019 and earlier)
.NET Framework 4.7.2 (Gateway release September 2019 and later)
A 64-bit version of Windows 7 or a 64-bit version of Windows Server 2008 R2
An 8-core CPU
8 GB of memory
A 64-bit version of Windows Server 2012 R2 or later
Solid state drive (SSD) storage for spooling ( Optional )
Heads-up: Microsoft has planned to use .NET 4.8 framework for gateways February 2020 version or higher
Points to be considered:
Gateways aren't supported on Server Core installations.
The user installing the gateway must be the admin of the gateway.
The gateway can't be installed on a domain controller.
If you're planning to use Windows authentication, make sure you install the gateway on a computer that's a member of the same Active Directory environment as the data sources.
You shouldn't install a gateway on a computer, like a laptop, that might be turned off, asleep, or disconnected from the internet. The gateway can't run under any of those circumstances.
If a gateway uses a wireless network, its performance might suffer.
You can install up to two gateways on a single computer: one running in personal mode and the other running in standard mode. You can't have more than one gateway running in the same mode on the same computer.
Pre-Check list before install:
Ensure you have the below sites added in the IE of your Gateway Node