GSA Windows client health check
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit 040d433 · +21 −10 lines · also on GitHub
⋯ 2 unchanged lines
33
description: Troubleshoot the Global Secure Access client using the Health check tab in the Advanced diagnostics utility.
44
ms.service: global-secure-access
55
ms.topic: troubleshooting
6
−ms.date: 10/08/2024
6
+ms.date: 11/12/2024
77
ms.author: jayrusso
88
author: HULKsmashGithub
99
manager: amycolannino
⋯ 47 unchanged lines
5757
1. If the Global Secure Access Tunneling service isn't running, start it from the `services.msc`.
5858
1. If the service fails to start, look for errors in the Event Viewer.
5959
60
−### Management service running
61
−Global Secure Access Management service must be running.
62
−1. To verify that this service running, enter the following command in the Command Prompt:
63
−`sc query GlobalSecureAccessManagementService`
64
−1. If the Global Secure Access Management Service isn't running, start it from the `services.msc`.
60
+### Engine service running
61
+The Global Secure Access Engine service must be running.
62
+1. To verify that this service is running, enter the following command in the Command Prompt:
63
+`sc query GlobalSecureAccessEngineService`
64
+1. If the Global Secure Access Engine Service isn't running, start it from the `services.msc`.
6565
1. If the service fails to start, look for errors in the Event Viewer.
6666
6767
### Policy Retriever service running
68
−Global Secure Access Policy Retriever service must be running.
68
+The Global Secure Access Policy Retriever service must be running.
6969
1. To verify that this service running, enter the following command in the Command Prompt:
7070
`sc query GlobalSecureAccessPolicyRetrieverService`
7171
1. If the Global Secure Access Policy Retriever service isn't running, start it from the `services.msc`.
⋯ 69 unchanged lines
141141
:::image type="content" source="media/troubleshoot-global-secure-access-client-diagnostics-health-check/troubleshoot-health-check-certificates-registry-key.png" alt-text="Screenshot of the list of certificates with the gsa.client certificate highlighted.":::
142142
1. Delete the following registry key:
143143
`Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Global Secure Access Client\CertCommonName`
144
−1. Restart the Global Secure Access Management Service in the services MMC.
144
+1. Restart the Global Secure Access Engine Service in the services MMC.
145145
1. Refresh the certificates MMC to verify that a new certificate was created.
146146
*Provisioning a new certificate might take a few minutes.*
147147
1. Check the Global Secure Access client event log for errors.
⋯ 11 unchanged lines
159159
:::image type="content" source="media/troubleshoot-global-secure-access-client-diagnostics-health-check/troubleshoot-health-check-certificates-registry-key.png" alt-text="Screenshot of the list of certificates with the gsa.client certificate highlighted.":::
160160
1. Delete the following registry key:
161161
`Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Global Secure Access Client\CertCommonName`
162
−1. Restart the Global Secure Access Management Service in the services MMC.
162
+1. Restart the Global Secure Access Engine Service in the services MMC.
163163
1. Refresh the certificates MMC to verify that a new certificate was created.
164164
*Provisioning a new certificate might take a few minutes.*
165165
1. Check the Global Secure Access client event log for errors.
⋯ 57 unchanged lines
223223
1. Verify that the system tray icon is visible.
224224
1. If the sign-in notification appears, select **Sign in**.
225225
1. If the sign-in notification doesn't appear, check if it is in the Notification Center and select **Sign in**.
226
−1. Sign in with a user that is a member of the same Entra tenant that the device is joined to.
226
+1. Sign in with a user that is a member of the same Microsoft Entra tenant that the device is joined to.
227227
1. Verify the network connection.
228228
1. Hover over the system tray icon and verify that the client is **not** disabled by your organization.
229229
1. Restart the client and wait for a few seconds.
⋯ 62 unchanged lines
292292
Configuring the Global Secure Access client to route Global Secure Access traffic through a proxy:
293293
1. Set a system environment variable in Windows named `grpc_proxy` to the value of the proxy address. For example, `http://10.1.0.10:8080`.
294294
1. Restart the Global Secure Access client.
295
+
296
+### No Hyper-V external virtual switch detected
297
+Hyper-V support:
298
+1. External virtual switch: The Global Secure Access Windows client doesn't currently support host machines that have a Hyper-V external virtual switch. However, the client can be installed on the virtual machines to tunnel traffic to Global Secure Access.
299
+1. Internal virtual switch: The Global Secure Access Windows client can be installed on host and guest machines. The client tunnels only the network traffic of the machine it's installed on. In other words, a client installed on a host machine doesn’t tunnel the network traffic of the guest machines.
300
+
301
+The Global Secure Access Windows client supports Azure Virtual Machines.
302
+
303
+The Global Secure Access Windows client supports Azure Virtual Desktop (AVD).
304
+> [!NOTE]
305
+> AVD multi-session is not supported.
295306
296307
### Tunneling succeeded
297308
This test checks each active traffic profile in the forwarding profile (**Microsoft 365**, **Private Access**, and **Internet Access**) to verify that connections to the health service of the corresponding channel are tunneled successfully.
⋯ 45 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/entra-docs, © Microsoft Corporation, under MIT. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 03:46 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.