GP client doesn't populate the gateway after installing

[Maxstr]

When users download the GP client from my portal and install it, the gateway field is blank. I've configured the gateway in the Globalprotect Portal>Agent Configuration>Gateways. 

Is there a way to have the gateway information pre-filled? 

[reaper]

You could push the client through a software management tool and set the configuration in registry by means of Global Policies

If users download the client from the GP portal, they'll simply download the executable and will need to imput the portal IP manually to have the client download the configuration

[Maxstr]

---

@reaper wrote:

You could push the client through a software management tool and set the configuration in registry by means of Global Policies

If users download the client from the GP portal, they'll simply download the executable and will need to imput the portal IP manually to have the client download the configuration

---

That's what I have been doing so far. But for users that are not on our AD domain, I have to instruct them to enter the IP themselves. 

I don't understand why the GP client doesn't come with the settings automatically. It's being downloaded directly from my firewall, it seems like common sense to include an XML or something that would have the connection info. 

So what is the "Agent Configuration" tab for if it doesn't actually configure the agent?

[reaper]

it configures the agent once it's made it's first connection and downloaded the config 😉

I don't know why the agent is not pre-loaded with the config, you may want to reach out to your SE and have him/her open a feature request, this does seem like an interesting 'thing to have'