Pro version customizes client automatic update #661
Replies: 13 comments 22 replies
-
|
Is there a plan to consider it? Because we found a bug in version 1.3.0. Versions below 1.3.0 had a bug in the Intel core graphics hardware acceleration, which caused a virtual memory leak. The bug was finally fixed after the release of version 1.3.1, but we had to manually reinstall version 1.3.1 on all machines. If this serious bug occurs again, we don’t want to manually upgrade one by one again, because now our number of client installations has reached more than 400. |
Beta Was this translation helpful? Give feedback.
-
|
If the custom client does not support auto-update why do standard users with no RD Service installed get a UAC Prompt to run the update script? |
Beta Was this translation helpful? Give feedback.
-
|
It is known that all customized versions have a BUG. We have set the control end to initiate a connection only after logging in. The security audit-connection log will occasionally show the connection log of users who are not logged in. We have contacted your technical staff to solve this problem, but we have to update the controlled end, which is a nightmare for users who have installed 500 controlled ends. |
Beta Was this translation helpful? Give feedback.
-
|
This is a needed feature. We use RMM with some clients and not with others. Manual work shouldn't be required to maintain reasonable security and fix bugs. |
Beta Was this translation helpful? Give feedback.
-
|
Agree, Hoping this feature gets added pretty quickly, as you would think it would not be that hard to implement this request, and it should take top priority since it's a security concern that could have huge implications if a person's account gets compromised. |
Beta Was this translation helpful? Give feedback.
-
|
i like the idea in combination with #648 i guess the clients would need an internal (UU)ID so each customclient can find the correct package. |
Beta Was this translation helpful? Give feedback.
-
|
@fufesou it is time to address this issue now. |
Beta Was this translation helpful? Give feedback.
-
This is a good idea,and we verified it works, but the problem is many of our clients deploy clients in intranet without Internet access. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, all my clients access the Internet from the RustDesk client.
|
Beta Was this translation helpful? Give feedback.
-
|
Maybe a way to solve the problem could be to implement a downloads-page to rustdesk and also use this page to handle downloads. |
Beta Was this translation helpful? Give feedback.
-
|
You would think a paid for licensed version of RustDesk Pro would have the same features (and more) than the free version. A Internet facing RustDesk Server Pro with Internet capable clients should be able to receive auto updates for custom clients. When you update the RustDesk Server Pro container to a new version there should be an option to rebuild all the custom clients (or manually from the custom clients page) Once the rebuild to the latest version is done, all clients that are configured to myserver.example.com should then be offered new client to install. Appreciate large installations will probably download the client and deploy to devices using their preferred tools, but for those that don't use deployment tools, this option would be really useful. Maybe for each custom client you could add a field for a unique url path. Example. custom client 1 - myserver.example.com/download/some-name.msi That way the URLs can be locked in a "download" folder (also definable) and with some unique name that only you would know to prevent random downloads, but the URL would be define in the custom clients configuration so it could check for a new version and know where to download it from. Maybe even expose the "download" folder to a docker volume or docker local bind, to keep the container image growing unnecessarily. This example would work for those on Intranet's as well, as long as DNS is setup correctly and the clients were on the same LAN or VPN. This could even be extended to the Strategies where on selected strategies you could enable/disable the custom client update feature. |
Beta Was this translation helpful? Give feedback.
-
|
I agree we really need an auto update. We're coming from Splashtop and we just need a solution to keep the clients up to date. These unmonitored headless computers are all over the world (mostly US) so updating is a manual process. |
Beta Was this translation helpful? Give feedback.
-
We have implemented it rustdesk/rustdesk#13687 But I'm sorry, we cannot release it in 1.4.5. It might be in 1.4.6. I have seen many complaints in the TeamViewer subreddit about the auto-update interruption issue caused by antivirus or other unknown reasons. This makes me worry about its robustness, so I decided to do more testing before release. I still think deploying and updating with RMM or deployment/distribution tools like Intune etc. is a better solution. But I know many users do not have these tools installed. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I noticed that the latest rustdesk 1.4.0 client supports automatic updates. When will the Pro version of the customized client support automatic updates?
Beta Was this translation helpful? Give feedback.
All reactions