-
Notifications
You must be signed in to change notification settings - Fork 177
Frequently Asked Questions
IAP Desktop does not require any special configuration on VM instances other than that Remote Desktop is enabled. All VM instances created using the Google public images have Remote Desktop enabled by default.
No, IAP Desktop does not depend on the Cloud SDK or gcloud.
The IAM roles required to use IAP Desktop depend on the feature set that you use. See Roles for details on which roles are required by individual features.
No, IAP Destop can be installed without admin rights unless you are installing on a Windows Server system.
On Windows Server, the default group policy is configured to disallow per-user installations of MSI packages. To install IAP Desktop on Windows Server, open an elevated command prompt, enter the path to the MSI file, and hit Enter.
To reset the location of tool windows, do the following:
- Close IAP Desktop
- Open a command prompt and run
reg delete HKCU\Software\Google\IapDesktop\1.0\ToolWindows
IAP Desktop heavily relies on Google Cloud APIs. Therefore, it is not possible to use IAP Desktop to access machines that are deployed elsewhere.
Typically, you do not need CALs if you use IAP Desktop for server administration only. If you use IAP Desktop for other purposes, or if need to support more than two concurrent connections, you might need to purchase RDS CALs.
Yes.
Currently not, but this feature might be added soon.
No, IAP Desktop maintains its own RSA key pair.
Google Cloud lets you use multiple SSH private keys, so you can continue to use your existing private key for other SSH clients.
IAP Desktop is an open-source project and not an officially supported Google product.