rustdesk/doc.rustdesk.com
1
0
Fork 0
mirror of https://github.com/rustdesk/doc.rustdesk.com.git synced 2026-04-17 05:39:57 +00:00
Code Issues Packages Projects Releases Wiki Activity

seo/geo

Browse Source
This commit is contained in:
rustdesk
2026-03-20 18:42:55 +08:00
parent 1736869d5f
commit 56cfd26e35
463 changed files with 6538 additions and 62 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
content/self-host/client-deployment/_index.en.md
View File

@@ -8,6 +8,29 @@ keywords: ["rustdesk client deployment", "rustdesk powershell deploy", "rustdesk
This guide covers large-scale RustDesk client deployment with scripts and automation tools such as PowerShell, batch, winget, and macOS bash. If you need the simplest experience and have RustDesk Server Pro, start with the custom client generator: https://twitter.com/rustdesk/status/1788905463678951787.
## What is the best way to deploy RustDesk clients at scale?
For RustDesk Server Pro, the easiest large-scale deployment path is usually the custom client generator because it packages your server settings into the client build. For environments managed through RMM, Intune, GPO, or custom automation, PowerShell, batch, winget, and shell scripts are more flexible.
## Which deployment method should you choose?
| Method | Best for | Why you would use it |
| --- | --- | --- |
| Custom client generator | RustDesk Server Pro teams | Simplest packaged deployment with preloaded settings |
| PowerShell | Windows fleet automation | Good fit for RMM, Intune, and scripted installs |
| Batch or cmd | Basic Windows scripting | Works in simpler Windows environments without PowerShell-heavy tooling |
| MSI | Managed Windows software deployment | Better fit when you already use MSI-based packaging workflows |
| Winget | Modern Windows package automation | Simple install path on newer Windows systems |
| macOS bash | Mac fleet deployment | Scriptable installation and config for macOS hosts |
## What inputs do deployment scripts need?
Most deployment scripts need three things:
- A RustDesk config string
- A deployment method that can run with administrator or root privileges
- A password policy, either random or explicitly set during deployment
You can deploy using a number of methods, some are covered in [Client Configuration](https://rustdesk.com/docs/en/self-host/client-configuration/).
Alternatively you can use mass deployment scripts with your RMM, Intune, etc. The ID and password are output by the script. You should collect this or split it into different scripts to collect the ID and password.