Okta Advanced Server Access and Okta Privileged Access Remote Desktop Protocol Fails With an Executable File Not Found Error

Okta Advanced Server Access (ASA) and Okta Privileged Access (OPA) generate an error when attempting a Remote Desktop Protocol (RDP) connection. This occurs because the Remote Desktop Client executable file is missing or malfunctioning. Resolve this issue by verifying the executable file exists in the system path and reinstalling the client if necessary. Users experience a failure to connect via RDP and receive the following error message:

unable to locate mstsc.exe client on $PATH: exec: "mstsc.exe": executable file not found in %PATH%

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Advanced Server Access (ASA)
• Okta Privileged Access (OPA)

The Remote Desktop Client executable file mstsc.exe is missing or malfunctioning.

What resolves the Remote Desktop Protocol connection error?

Verify the existence of the executable file in the system path and reinstall the Remote Desktop Connection client if necessary.

1. Open a Command Prompt on the Windows client.
2. Verify that the mstsc.exe file exists in one of the %PATH% directories (typically C:\Windows\System32\) by entering the following commands:

   where mstsc
   echo %PATH%

3. Launch the Remote Desktop client by entering the following command:

   mstsc

NOTE: If the executable is missing or malfunctioning, reinstall the client by reviewing the Microsoft documentation to Uninstall and reinstall Remote Desktop Connection.