Skip to content

Commit bfd1d61

Browse files
committed
clean up rdp
1 parent 4d09dfa commit bfd1d61

File tree

1 file changed

+3
-3
lines changed
  • src/content/docs/cloudflare-one/connections/connect-networks/use-cases/rdp

1 file changed

+3
-3
lines changed

src/content/docs/cloudflare-one/connections/connect-networks/use-cases/rdp/rdp-browser.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ import { Render, GlossaryTooltip } from "~/components"
1414
Browser-based RDP is currently in closed beta. To try out the feature, contact your account team.
1515
:::
1616

17-
With Cloudflare Zero Trust, you can allow users to connect to an RDP server without installing an RDP client or the WARP client on their device. This method requires installing `cloudflared` on your RDP server (or any other host machine within the private network) and routing RDP traffic over a public hostname.
17+
With Cloudflare Zero Trust, users can connect to an RDP server without installing an RDP client or the WARP client on their device. Browser-based RDP requires installing `cloudflared` on your RDP server (or any other host machine within the private network) and routing RDP traffic over a public hostname.
1818

1919
The user logs in first to the App Launcher with their Cloudflare Access credentials and then initiates an RDP connection within the browser to their Windows machine. Users will authenticate to the Windows machine using their pre-configured Windows username and password. Cloudflare does not manage any credentials on the Windows server. A user may also navigate directly to the Windows server using a public URL. The authentication flow will be unchanged; first users must log in to Cloudflare Access and then use their Windows credentials to authenticate to the Windows machine.
2020

@@ -97,11 +97,11 @@ To connect to a Windows machine over RDP:
9797
Replace `<your-team-name>` with your Zero Trust <GlossaryTooltip term="team name">team name</GlossaryTooltip>.
9898
2. Follow the prompts to log in to your identity provider.
9999

100-
Once you have authenticated, the App Launcher will display tiles showing the applications that you are authorized to use. Windows servers (targets) available through browser-based RDP will also appear as tiles. If a target is reachable through multiple application, the App Launcher will show a tile for each application.
100+
Once you have authenticated, the App Launcher will display tiles showing the applications that you are authorized to use. Windows servers (targets) available through browser-based RDP will also appear as tiles. If a target is reachable through multiple Access applications, the target will have a tile per Access application.
101101
3. Select the target you want to connect to.
102102

103103
The App Launcher tile will launch a URL of the form `https://<app-domain>/rdp/<vnet-id>/<target-ip>/<port>`. You may also navigate directly to this URL.
104-
4. Select the port that you want to connect to. You will only see this screen if the Access application allows RDP traffic on multiple ports (for example, port `3389` and port `65321`).
104+
4. Select the port that you want to connect to. The port selection screen only appears if the Access application allows RDP traffic on multiple ports (for example, port `3389` and port `65321`).
105105
5. Enter your Windows username and password.
106106

107107
You now have access to the remote Windows desktop.

0 commit comments

Comments
 (0)