Providing secure, identity-based access to private apps and resources without traditional VPNs
The supported next steps are:
- Use the built-in client troubleshooting tools from the taskbar icon menu if available: Export logs and Advanced diagnostics tool.
- Since
GlobalSecureAccessClient.exeis already running but the tray UI is not visible, manually start the tray application from:C:\Program Files\Global Secure Access Client\GlobalSecureAccessClient.exe - Verify the tray icon is visible. If a sign-in notification appears, select Sign in. If it does not appear, check Notification Center and select Sign in there.
- Sign in with a user from the same Microsoft Entra tenant that the device is joined to.
- Hover over the system tray icon and verify that the client is not disabled by your organization.
- Restart the client and wait a few seconds.
- Check Event Viewer for client errors.
- If the tray application still does not appear, collect troubleshooting logs and submit a support ticket including those logs.
Supported health checks relevant to this scenario:
- The device must be Microsoft Entra joined or Microsoft Entra hybrid joined. Microsoft Entra registered devices are not supported.
- The Windows sign-in user must be a Microsoft Entra user, not a local-only account.
- The tunneling, engine, and policy retriever services must be running.
- If the client icon is missing from the tray, the documented action is to run
GlobalSecureAccessClient.exefrom the installation path above.
No documented known issue for the specific .NET Runtime error or Microsoft.NETCore.App.runtimeconfig.json corruption is provided in the available material. The documented escalation path, after self-service diagnostics and log collection, is to submit a support ticket.
References: