Has anyone had any experience with configuring an endpoint to purposely avoiding a Gateway Service PoP? I have users periodically complain about random and sudden session disconnects and every time I look at Monitor, they are going through Northern Virginia.

Without changing clients IP with a VPN the only method I could potentially think of would be to block the pop fqdn on the FW aws-us-e-rdvz.g.nssvc.net for north Virginia

There is the preferred pop setting, where you can set network locations to use particular locations. But that would only work if they are coming from an office with a set Internet NAT, if they are internet roaming users that wouldn't work.

@Jeff Riechers, where is that setting? @c4rm0, I had tried doing that with my local Windows firewall but was unsuccessful for whatever reason.

It's under Workspace Configuration -> Access -> External Connectivity -> Location Gateway Service (edit)

Oh how about that! I am familiar with that page, but that drop down must be new. There was only a choice of Traditional Gateway, Gateway Service, and Internal Only before.

Yeah I not seen that option before

It used to be easier to find when it came out of tech preview. It was a rather silent launch, and originally was just request only. I learned a lot about it when I had a client that was all Left Coast US getting sent to Right Coast pops.

And this setting is just for Citrix Cloud direct connections initiated out of that Resource Location, right? So those users in that office launching customer.cloud.com are pointed to that pop.