We are having a problem with cloud hosted ScreenConnect where any names we set for new access sessions are not being saved. It will remember the name for a few minutes but then clear it and revert back to the machine name. This only seems to have started since our instance was upgraded to version 26.2.4.9600. Anyone else seeing this issue or is it just us?
I'm on the SC cloud. I have no integrations. I do have a few plugins installed.
Advanced Config Editor
Advanced SMTP
Auto Respond to Message
ChatOnConnect
Cloud Auth
Duplicate Access Session Finder
Guest Basic Installer Builder
In-Application Help
Note on Desktop
Remote Diag Toolkit
Report Generator
Report Manager
Security Toolkit
Support Session Renamer
tawk.to Chat Integration
And if I rename any older system with a custom name to something else, it too goes to machine name, so it's not limited to new installs.
I don't need to reboot any of these hosts. Simply clicking "Update Guest Info" reverts the name to machine name.
We have not been able to reproduce this issue internally using ScreenConnect standalone, do you have an integration that you are running that could be changing something on the end points?
In any case, I would recommend contacting Support since this does not appear to be a straightforward issue.
https://connectwise20.my.site.com/serviceandsupport/s/contactsupport?ref=header-sc
Nothing is changing anything on the endpoints. We deploy ScreenConnect with an integration to our RMM (Syncro), but this has always worked flawlessly until the current version of ScreenConnect. Following more testing, although we can set a friendly name for these new Access sessions, they will revert back to machine name following a reboot of the PC it is installed on, making it more difficult to identify the correct device. This is seemingly only affecting Access sessions added with this version. All our Access sessions added previously have retained their friendly names and changes to them seem to hold as well.
We have not been able to reproduce this issue internally using ScreenConnect standalone, do you have an integration that you are running that could be changing something on the end points?
In any case, I would recommend contacting Support since this does not appear to be a straightforward issue.
https://connectwise20.my.site.com/serviceandsupport/s/contactsupport?ref=header-sc
Same. Does anyone check these forums?
Steps to reproduce: Install with "computer name" as identifier. Rename system. Refresh in SC. Reverts back to computer name.
I'm seeing this issue too, and new devices are being lost in a growing list of devices named DESKTOP-xxxxxx
On install, 'Use Machine Name' is selected as default, as normal and as it's always been.
Edit the client to Use Specific Value and give it the name we want. After a while, client is renamed back to machine name.
Cloud: 26.2.4.9600
I'm on the SC cloud. I have no integrations. I do have a few plugins installed.
Advanced Config Editor
Advanced SMTP
Auto Respond to Message
ChatOnConnect
Cloud Auth
Duplicate Access Session Finder
Guest Basic Installer Builder
In-Application Help
Note on Desktop
Remote Diag Toolkit
Report Generator
Report Manager
Security Toolkit
Support Session Renamer
tawk.to Chat Integration
And if I rename any older system with a custom name to something else, it too goes to machine name, so it's not limited to new installs.
I don't need to reboot any of these hosts. Simply clicking "Update Guest Info" reverts the name to machine name.
We are also on SC Cloud and have these installed:
Advanced Config Editor
Clipboard Helper
Cloud Auth
ConnectWise View Integration
Desktop Notifications
Hudu Integration
In-Application Help
Remote Diagnostics Toolkit
Report Generator
Security Toolkit
Tiled Session View
I tested again and it definitely does not happen with older ones for us and I can happily rename any of these and have it stick.
You are correct about clicking "Update Guest Info" though. That makes it happen for us as well, so reboot not necessarily required, but as this triggers an update of the guest, also causes it.