{"id":2089,"date":"2025-03-04T08:30:00","date_gmt":"2025-03-04T07:30:00","guid":{"rendered":"https:\/\/kasperjohansen.net\/?p=2089"},"modified":"2025-03-02T06:58:22","modified_gmt":"2025-03-02T05:58:22","slug":"quickpost-global-secure-access-client-network-detection-script","status":"publish","type":"post","link":"https:\/\/kasperjohansen.net\/index.php\/2025\/03\/04\/quickpost-global-secure-access-client-network-detection-script\/","title":{"rendered":"Quickpost – Global Secure Access client network detection script"},"content":{"rendered":"\n

I have previously sung my praises about Global Secure Access Private in a another article<\/a> here on my blog and I do think that Global Secure Access (GSA) is a great product with a lot of potential. However, there are still features that needs additional development one of these features are the automatic network detection feature.<\/p>\n\n\n\n

In short, the Global Secure Access client does not detect if your Windows device is connected to the corporate network. This means that Global Secure Access is always active and even though the resources published in Global Secure Access are on the same network as the Windows device, communication to these resources still go through Global Secure Access.<\/p>\n\n\n\n

I have written about how to deploy, configure and lock down the Global Secure Access client<\/a> adding to this article, I have created a script as a workaround to disable GSA Private Access if the Windows device is on a corporate network.<\/p>\n\n\n\n

\n
\n

Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n