A Windows VPS as a shared remote desktop for a cross-border team

The first thing you notice when your team spans Guangdong and Guangdong is that every service slows down the moment data crosses a border. Shared drives lag, WeChat file transfers time out on large PDFs, and someone always ends up emailing a file to themselves because the office NAS is unreachable from the other side. A Windows VPS Vietnam for China team solves this cleanly: one machine in a Vietnam datacenter that everyone on the team connects into via Remote Desktop. Your files, your tools, your apps, all on a single always-on desktop that every teammate reaches from Shenzhen, Nanning, or Ho Chi Minh City at the same speed.

越南 Windows VPS 提供稳定的远程桌面，适合跨境团队多人同时使用。

A Vietnam Windows VPS provides a stable remote desktop suitable for simultaneous use by a cross-border team.

Why a shared remote desktop instead of VPNs or file sync

Most teams start with a VPN back to an office in Vietnam or a cloud sync folder. Both break under real use. A VPN gives you network access but leaves every file transfer subject to the latency between China and Vietnam, a 50 MB design file can take minutes. File sync services like OneDrive or Dropbox work for small teams but create version conflicts when three people edit the same spreadsheet, and neither platform gives you a shared application environment where everyone runs the same CRM, the same ERP client, or the same local tools.

A Windows VPS with RDP flips the model: the data stays on the VPS, the application runs on the VPS, and the remote desktop is just a video stream of what the server renders. Your 50 MB file opens instantly because it never leaves the server. Your accountant runs the desktop QuickBooks in Shenzhen the same way it runs in the Hanoi office. The only thing crossing the link is screen updates and keystrokes, which even the modest 4 to 10 Mbps shared international bandwidth on a typical Vietnam VPS handles easily for office work.

For cross-border China Vietnam business, logistics, sourcing, manufacturing support, this is the difference between a usable workflow and constant frustration.

Choosing the right Windows VPS: RAM is the bottleneck

A shared desktop is only as good as the RAM behind it. Windows Server 2022 alone uses about 1.5 GB at idle. Add two connected users each with a browser and a Word document, and you are already above 4 GB. This is where the common mistake happens: buying a 2 GB RAM VPS and wondering why the desktop freezes the moment a second person connects.

The baseline for a shared Windows VPS for a cross-border team of three to five people is 4 GB RAM, and realistically 8 GB if the team runs any line-of-business application, accounting software, ERP client, or a browser with more than a few tabs. A Windows VPS with 4 vCPU and 8 GB RAM (the VNx2 tier or equivalent) handles four simultaneous RDP sessions comfortably for document editing, email, and light browser work. If your team runs heavier applications, Adobe Reader for large drawings, a chat app running screen share, or an in-house tool, step up to the VNx4 with 16 GB.

Storage is rarely the constraint. A VPS with 50 GB of NVMe space is plenty for shared documents, one or two desktop applications, and Windows itself. What matters is that the storage is NVMe, the difference between waiting three seconds and three dozen seconds for a file to open under load.

Multi-user RDP setup: user accounts and Remote Desktop Services

Windows Server allows multiple concurrent RDP sessions by default, but it is not unlimited. Out of the box, Windows Server permits two simultaneous remote connections. For a team of three or more, you need to enable Remote Desktop Services (RDS) in the Server Manager or acquire RDS CALs if you follow the licensed path. For evaluation and small teams, the two-session limit is frequently worked around by leaving desktops connected, but that is fragile and blocks maintenance.

The practical setup for a small cross-border team:

1. Configure the RDP port, change it from 3389 to a non-standard port to reduce automated scanning traffic. In Registry: HKLM\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\PortNumber. Set to, say, 3390. Update the Windows firewall to allow the new port.
2. Create per-user accounts, one for each team member. Local accounts are sufficient. Name them clearly: shenzhen-li, guangzhou-chen. Grant each user Remote Desktop Users group membership and nothing more. Do not grant Administrator unless necessary.
3. Set a session timeout, under Group Policy (gpedit.msc) → Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Session Time Limits. Set "Set time limit for active but idle Remote Desktop Services sessions" to 30 minutes. This prevents a disconnected session from holding memory forever. Also enable "End session when time limits are reached" so the server can reclaim resources.
4. Lock down logon hours, each user account can log on only during working hours (China Standard Time matches Vietnam time, conveniently). This is set in lusrmgr.msc → user properties → Account → Logon Hours.

# On the Windows VPS, after changing the RDP port, update the firewall:
netsh advfirewall firewall add rule name="RDP Custom Port" dir=in action=allow protocol=TCP localport=3390

# Verify the RDP service is listening on the new port:
netstat -ano | findstr :3390

File sharing on the shared desktop

The simplest reliable file share for a multi-user Windows VPS is a folder on the system drive shared as a network share from within the local network of the VPS, meaning each RDP session accesses it via \\localhost\SharedDocs. To do this:

1. Create a folder on the D: drive (or any data volume), e.g. D:\TeamShare.
2. Right-click → Properties → Sharing tab → Share. Add the Remote Desktop Users group and grant Read/Write.
3. In each user's RDP session, map the share as a network drive: run net use S: \\localhost\TeamShare /persistent:yes.

This keeps all team documents on the VPS, no downloads to local machines, no sync conflicts. Every edit is immediately visible to every other connected user.

For version conflict management on office documents, install Office on the VPS (one installation, all users access it) and rely on Office's built-in co-authoring or keep a simple convention: "whoever opens the file first owns it". For a team of three to five, this works without special tooling.

Keeping the desktop always on

A shared remote desktop that shuts down at 6 PM and disconnects everyone is worse than no VPS at all, it teaches the team to distrust the system. You need the VPS to stay running and the RDP service to stay available. On a Windows VPS, this is straightforward:

• Disable sleep and hibernation, go to Power Options → set the power plan to High Performance → set "Turn off the display" to Never → set "Put the computer to sleep" to Never. For a server OS, these are already off, but double-check.
• Enable automatic logon, optional, but if a reboot happens (Windows updates, power cycle in the datacenter), you want the desktop to be logged in so the team does not need to wait for someone to RDP in and unlock it first. Use netplwiz or the Autologon tool from Sysinternals. Be careful: this means the desktop session is always unlocked, so lock down RDP network-level authentication (NLA) to require a user/pass for any connection.
• Schedule reboots, Windows Updates will force a restart eventually. Schedule it for a low-usage window. Run taskschd.msc and create a task that reboots at 2 AM on Sunday and ensures the RDS service starts after boot.
• Monitor the RDP port, use the built-in Performance Monitor to watch the Terminal Services → Total Sessions counter. Set up a simple alert: if sessions drop to zero and stay zero for 15 minutes outside maintenance hours, the server likely rebooted and did not come back. The VPS control panel's snapshot/rebuild function lets you restore in minutes.

# Schedule a weekly reboot from PowerShell:
$action = New-ScheduledTaskAction -Execute "shutdown" -Argument "/r /t 60 /c 'Scheduled weekly reboot'"
$trigger = New-ScheduledTaskTrigger -Weekly -DaysOfWeek Sunday -At 2am
Register-ScheduledTask -TaskName "WeeklyReboot" -Action $action -Trigger $trigger

Network considerations for China to Vietnam VPS

The network path between China and Vietnam is not symmetrical in quality. Traffic from China entering Vietnam via the domestic Viettel or VNPT backbone (Vietnam's two largest telecom operators) generally shows 30 to 60 ms latency from Shenzhen or Guangzhou to a datacenter in Hanoi or Ho Chi Minh City. From Kunming or Nanning (Yunnan and Guangxi provinces, closer to the border), latency can drop to 20-30 ms, usable for real-time screen sharing and remote desktop work. Traffic routed through international transit (which happens if the VPS uses a provider without direct Viettel peering) can spike to 150-200 ms, which makes RDP laggy.

This is why the specific carrier matters. Vietnamese providers who peer directly with Viettel and VNPT give the best China route. The network facts for a properly connected Vietnam VPS are standard: unlimited traffic with no data cap, domestic bandwidth of 100 Mbps on a 1 Gbps port (the port is 1 Gbps, the speed commit is 100 Mbps), and international shared at roughly 4 to 10 Mbps. For remote desktop traffic (screen updates, keystrokes), even the international pool is sufficient, a typical RDP session uses 100 to 500 kbps. The domestic 100 Mbps is what your team hits once they connect via RDP, because the VPS processes everything locally and sends a compressed video stream.

The dedicated IPv4 from the Vietnam range also matters: services identify the connection as coming from Vietnam, which avoids geo-restrictions that some platforms place on China-based IPs.

When Windows and when Linux

This guide assumes Windows because the brief is a shared remote desktop. If your team's workflow is browser-based (a web CRM, a cloud ERP, browser tools), a Linux VPS with a remote desktop layer (XRDP, X2Go) would work and use half the RAM. But the moment you need a desktop application, an accounting package, a design tool, a thick-client ERP, Windows is the only choice. A Windows VPS with RDP gives your cross-border team the same experience as walking into the Vietnam office and sitting down at the desk.

FAQ

Related articles

• Securing RDP on a public IP: the four settings that matter
• Windows Server vs Linux for a small business VPS
• Sizing RAM for Windows Server VPS: why 2 GB is never enough
• Migrating a legacy .NET app to a Windows VPS