Device List - assign names to devices without registering as a user about rustdesk-server-pro HOT 23 CLOSED

Yes a QS option would be good on the future

from rustdesk-server-pro.

In addition, there should be a host client that cannot connect to others, but simply displays the ID and password.

This is called quick support version for TeamViewer.

from rustdesk-server-pro.

#12

from rustdesk-server-pro.

Maybe I misunderstand this.
Is this intended to have everyone/device registered, so that controls can be applied via groups and strategies?
Either way I feel a generic field to name devices with a friendly name would be beneficial.

from rustdesk-server-pro.

Renaming on client side does not require user assigned. We are adding note (#12).

I am also considering to allow rename from the web console.

from rustdesk-server-pro.

Ahhh if we can rename via client that may be enough, but I guess if the install is automated that might be where console side is beneficial.

from rustdesk-server-pro.

Yes, installation automation is quite important. We did ignore this for open source self-host. But now, we need to emphasize on it for Pro.

Any suggesions about automated installation, please propose. I am collecting feedback about this, and decide how to do it in good direction.

@it-boerner @dinger1986

from rustdesk-server-pro.

Should we start a new issue tracker for installation automation side of things?

from rustdesk-server-pro.

Ok, please

from rustdesk-server-pro.

I think you should be able to have two applications, especially in the pro area.

Once the classic client, with which you can also register.

In addition, there should be a host client that cannot connect to others, but simply displays the ID and password.

This host client should also install using a PowerShell script.

from rustdesk-server-pro.

In addition, there should be a host client that cannot connect to others, but simply displays the ID and password.

This is called quick support version for TeamViewer.

from rustdesk-server-pro.

Darüber hinaus sollte es einen Host-Client geben, der keine Verbindung zu anderen herstellen kann, sondern lediglich die ID und das Passwort anzeigt.

Dies wird als quick supportVersion für TeamViewer bezeichnet.

Yes, that's right, TeamViewer has three different clients.

There is the normal client, then the quick support and finally the host.

from rustdesk-server-pro.

Sounds great, should we yet again start a new thread, possibly a wishlist thread?

from rustdesk-server-pro.

I guess threads per suggestions etc

from rustdesk-server-pro.

adding this here rustdesk/rustdesk#5007 (reply in thread) as I think its fitting

from rustdesk-server-pro.

Commenting here but close again if I am off course ...

I was hoping to get device names (computer hostname) and user that is logged in to those machines, populating in to the RustDesk Pro Console.
I have updated our Console to 1.1.9 and have started rolling out installed versions of RustDesk Client 1.2.2
But yet again these devices just show up with ID numbers and nothing else populated in the Device Name or User columns.
Is this still to come or have I not explained properly what I wanted originally?

The only devices that have device name/user filled out are the ones where I logged in with my Console user/pass which is my own laptop and a server I tested on, all others are blank.

Thanks again

from rustdesk-server-pro.

To make it work, you need to make sure.

• running 1.2.2
• the device can access API server. #21 (comment)

from rustdesk-server-pro.

Ahh too true think I left API server blank 😆
Update: API field not left blank, just now trying to triple check everything else

from rustdesk-server-pro.

Ok device names are now populating
But I guess my bigger issue/request as my comment above, was to have the clients domain / windows / linux? user name in the "User" field
This User field is currently clearly linked to a RustDesk technician/user account.
I was unsure originally as my windows user was the same format as my RustDesk user, so I just created a "test" user and of course instantly in the console my device name now has "User" test.
Sorry to bang on about it, but can we please get a OS user populating in the web console?
The client side address book / discovered tab, shows the windows user name already.

from rustdesk-server-pro.

@DMSnz What exactly did you to to populate device names without login? im facing the same problem: I only see the name after logging in. The API should work because i can log without any problems. API website is accessible from client device (using https)

from rustdesk-server-pro.

@DMSnz What exactly did you to to populate device names without login? im facing the same problem: I only see the name after logging in. The API should work because i can log without any problems. API website is accessible from client device (using https)

I believe at the time we updated our docker version to 1.1.9 but with the docker re-creation our license bombed out, so when I initially checked I think it was unlicensed, once fixed that and verified client version was 1.2.2 minimum and API addresses, it all started working.

But to this day I still have issues where the username of the user is not showing 85% of the time, some machines run nearly 24/7 always logged in, shows these hosts online but simply refuses to show username.
For others it works fine so you get user@device showing up nicely.

from rustdesk-server-pro.

@DMSnz Your current problem sounds like this one: #174 (fixed) - Maybe you are not using the latest version?

I think i also found the reason for my problem. It seems that RustDesk absolutely do not like TLS connections below version 1.3. That means if your API Server Address is encrypted by TLS_1.2 it will not work. You can log in to your account via the client but all API requests doesnt seem work. Same for secured LDAP connections btw.

-> If this is true, you are doomed if you are running RustDesk Server Pro (for Windows) on a version older than Windows Server 2022.

from rustdesk-server-pro.

@User35123 Thanks for that info will indeed be my issue, had not looked into it let alone found that bug and fix.

Good to hear you also seem on track with your issue

from rustdesk-server-pro.