-
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.
To use IAP Desktop, you need the Project Owner role or a combination of the following roles:
- Compute Instance Admin or Compute Admin to list and access VM instances
- IAP-secured Tunnel User to use IAP TCP forwarding
To generate Windows credentials, you also need:
- Service Account User
Roles can be grated on a per-project or per-VM instance level.
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.
Project Explorer only shows instances that are known to run Windows. Filtering is performed based on license and guest OS features metadata of the VM instance's disks.
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.
IAP Desktop is an open-source project and not an officially supported Google product.