<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Remote Desktop on Margrop Blog</title>
    <link>https://blog.margrop.net/en/tag/remote-desktop/</link>
    <description>Recent content in Remote Desktop on Margrop Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Sat, 11 Jul 2026 04:00:00 +0800</lastBuildDate>
    <atom:link href="https://blog.margrop.net/en/tag/remote-desktop/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Don&#39;t Let Your Mac mini Gather Dust: Run Agents 24/7 from Windows</title>
      <link>https://blog.margrop.net/en/post/windows-remote-desktop-mac-realvnc/</link>
      <pubDate>Sat, 11 Jul 2026 04:00:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/windows-remote-desktop-mac-realvnc/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;The short answer&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;If Windows is your everyday platform but a low-power Mac mini stays on to run OpenClaw, HermesAgent, or macOS-only automation, you do not need to dedicate another monitor, keyboard, and mouse to it. Treat the Mac mini as a quiet Agent server. macOS already includes Screen Sharing, and RealVNC Viewer on Windows can take over the desktop whenever configuration, upgrades, or troubleshooting require a GUI.&lt;/p&gt;&#xA;&lt;p&gt;This is especially useful in a Windows-first home or studio where the Mac mini runs continuously at relatively low power while the Windows machines remain the daily workstations. The installation is rarely the difficult part. Most failures come from Screen Sharing, user authorization, VNC credentials, network reachability, sleep behavior, or services that do not recover after a restart.&lt;/p&gt;&#xA;&lt;p&gt;One rule matters more than every convenience tweak in this guide: &lt;strong&gt;do not expose TCP port 5900 directly to the public Internet.&lt;/strong&gt; A same-LAN connection is the simplest starting point. For access across networks, first join a self-hosted VPN or another controlled private network, and only then connect to the Mac.&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
    </item>
    <item>
      <title>Take Back Your Remote Desktop: Deploying an All-in-One RustDesk Server Safely</title>
      <link>https://blog.margrop.net/en/post/rustdesk-all-in-one-server-guide/</link>
      <pubDate>Fri, 10 Jul 2026 22:00:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/rustdesk-all-in-one-server-guide/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;The short version&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;RustDesk is an open-source remote desktop application designed with self-hosting in mind. When two clients can reach each other directly, screen and input traffic can use a peer-to-peer path. When that direct path fails, a relay server forwards the encrypted traffic. Hosting the server yourself does not eliminate servers; it puts device registration, relay routing, keys, accounts, and logs back under your control.&lt;/p&gt;&#xA;&lt;p&gt;This guide uses the community-maintained &lt;code&gt;lejianwen/rustdesk-server-s6&lt;/code&gt; image to place the RustDesk OSS &lt;code&gt;hbbs&lt;/code&gt; and &lt;code&gt;hbbr&lt;/code&gt; services together with a community API and web administration layer in one container. It is a convenient option for homes, labs, and small teams, but it is &lt;strong&gt;not an official RustDesk all-in-one distribution&lt;/strong&gt;. Evaluate the community image, pin a tested tag or digest, back up its persistent data, and rehearse upgrades and rollbacks before treating it as production infrastructure.&lt;/p&gt;&#xA;&lt;p&gt;Every address in this article uses &lt;code&gt;example.com&lt;/code&gt;. No real IP address, private domain, hostname, device ID, account, key, token, cookie, or private registry is shown. The screenshots come from public official or community project pages.&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
    </item>
    <item>
      <title>Install Frp client on Mac and use remote desktop</title>
      <link>https://blog.margrop.net/en/post/mac-frpc-install-for-remote-desktop-problem/</link>
      <pubDate>Mon, 18 Jan 2021 13:28:26 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/mac-frpc-install-for-remote-desktop-problem/</guid>
      <description>You can install it with Homebrew.&#xA;The following section shows the old manual extraction method. Keep reading if you want that approach.&#xA;brew install frpc vi /usr/local/etc/frp/frpc.ini brew services start frpc Download the Darwin package from FRP releases and unzip it omitted Copy the executable sudo mv ~/Downloads/frp_0.34.3_darwin_amd64/frpc /usr/local/bin/ Add the frpc configuration file Adjust server_addr, server_port, and remote_port as needed. Edit the auto-start configuration Commands related to auto-start sudo su cat&amp;gt;/etc/frpc.</description>
    </item>
    <item>
      <title>Install Frp client on Windows and use remote desktop</title>
      <link>https://blog.margrop.net/en/post/windows-frpc-install-for-remote-desktop/</link>
      <pubDate>Sun, 17 Jan 2021 19:36:38 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/windows-frpc-install-for-remote-desktop/</guid>
      <description>As the usage restrictions of TeamViewer become more and more strict, it will be regarded as an enterprise user from time to time. After all, there is no free lunch in the world. The following is a method to use the Frp client for intranet penetration and remote control.&#xA;Please prepare your own Frp server and consider the security risks of exposing port 3389 to the public network.&#xA;Download Frp client #Configure Frp client</description>
    </item>
  </channel>
</rss>
