I see you are trying to blame windows for the failed "installs" needing restarts, although i expected this, heres the thing no one of your other updates went this badley, all systems were up to date. Please advise.
How do you explain a server that was running the HOST, then had this removed and the viewer installed (i manually logged in to the server and found it, the install date was the date i did the upgrade, so why did the "upgrade" remove the host then install the viewer?)
Ive spent about 5 hours tonight trying to resolve what was supposed to be a "simple" upgrade, clearly this "major re-write" has some "major bugs", heres my findings so far..
- Some endpoints MUST have a restart, they either say online but cant connect or "logging in" and nothing more, a restart seems to fix that (it means getting to the machine locally to do the restart), so clearly the "upgrade" didnt fully complete.
- Some go offline, so far i have found it removed the "host" and installed a "viewer" only, i didnt ask it to do this, however the "upgrade" did... thats again another visit to the hose, remove the viewer then install the host (again).
= Not sure what they did to the keyboard, but i can no longer type in ANY VMWare console (vSphere client), they numbers work (top row) but the letters do not, again this was working fine in the past version, so what was changed to break VMWare vSphere client typing (which is 90% the reason i use this, its on a machien onsite that has vSphere or vCenter install to log in to 20 servers, now i cant log in to any of them as i cant type in to vSphere (even after restarts).
Getting to the point i might have to roll EVERYTHING back to an older version or look for a new RMM if its not fixed fairly fast.
To give you some ideas about what would be good on that blank screen (see image) I only spent about 5 mins making this but you get the idea.....
Including a LOGO and text (and you can see the PC name as well so if anyone calls they can tell you which PC as support happens on more than one at a time generally).
Possible fillable fields in the text could be an idea like the below, that would be used to "fill in" things like the computer name..
[[remoteutilities-user]] (this could be pulled from the login name of the viewer [[remoteutilities-contact]] (this could be pulled from the login name of the viewer, say a contact number with extension) [[remotecontrol-starttime]] (the time remote control was started) [[hostname]] (this was used in my image under identification)
There are many more fields you could use but this is a real good idea, and no other remote control i know does this...
When the option Blank the host's screen is enabled, i assume the host will just have a blank screen.
ive had the user at this host reboot there PC (while i am working on it) as they think its crashed. Can we have a way to put a customization message on the that screen (and a way of putting some LOGO as well to brand the support).?
Also it would be nice to have a status in the viewer somewhere that confirms the users screen IS BLANK, sometimes ive been told all the sensitive work i was doing everyone could see, when i thought it was being blanked when it wasnt.