The new version, upKeeper 4.9 includes new functions, performance enhancements and bugfixes. The most important functions and bugfixes are listed below. For a complete list please read our detailed release notes which can be found at the ftp site.
These are the new features in Upkeeper version 4.9
System reliability history in admin web
New system reliability tab showing system reliability score for the past 30 days as well as related events.
System reliability in My upKeeper
The current reliability/health index is now shown directly in the client. A new button has been added that users can click to open Windows Reliability Monitor.
Upkeeper client now makes use of tcp communication between the client service and the My upKeeper tray client for some messages. This communication is running on port 6665 by default. If another port is preferable it can be changed by setting the registry value below to any valid port number.
Ultra VNC support
UltraVNC support function is built in to the Admin web and the My upKeeper client application. Settings for this can be found on the tab "Remote".
The recommended usage is to use the Ultra VNC repeater server. This will allow the server and client to start a session that will exit on both sides when the helping part closes down the window. No continually running server is needed. By using the repeater all sessions can be monitored and controlled in one location.
The settings that need to be configured are:
Ultra VNC Server Command: The path to the winvnc.exe executable with all parameters that will be run on the upkeeper client computer in order to start a hosting session.
Do not specify the port after the repeater address, that will cause an error.
The keyword "SESSIONID" is used as a placeholder and will be exchanged for the id generated for the session.
The command must end with "-run"
Environment variables can be used, such as %PROGRAMFILES%
"%PROGRAMFILES%\uvnc bvba\UltraVNC\winvnc.exe" -sc_prompt -sc_exit -id:SESSIONID -connect myUltraVncRepeater.com -run
Ultra VNC Server INI File: The ini-file that will be copied to the client as the upkeeper service starts up. See the Ultra VNC documentation on how to configure this.
Ultra VNC Viewer Command: The corresponding path to VncViewer.exe (with parameters) to start the viewer client on the administrators computer.
Same instructions as for the server command, but here the port to the repeater must be specified.
"%PROGRAMFILES%\uvnc bvba\UltraVNC\Vncviewer.exe" -proxy myUltraVncRepeater.com:5901 id:SESSIONID
Enabling the feature
When the client service starts up it will look for the application executable at the location provided in the settings above. If found, it will copy the INI file to the folder ("UltraVNC.ini") and report back to the client API that UltraVNC is installed. All computers with this feature enabled will carry the Ultra VNC icon on the computer page in the admin web.
Clicking the Ultra VNC icon on a computer in Admin web will create a bat-file download. This contains the command to start the viewer connnected to the repeater with a unique ID. This also signals the client to start the server immediately.
All sessions with their unique id's are then removed from the database every 15 minutes. This does not affect the current VNC session - it just removes the ability to start the session again from myUpkeeper.
Client logger: The bundled command Upkeeper.Client.Logger.exe now has support for the parameter -a or --applicationId. This will save the log connected to a specific application, in addition to the current computer.
Upkeeper.Client.Logger.exe" -m "test log message" -a "66437595-2560-4cty-ad76-d6f76798e26d"
Third-party dependencies in Upkeeper Admin Web has been updated to the latest security patches.
.Csv file export (8670) A bug that occurred in Chrome when exporting devices containing a '#' character was fixed. The text isn't chopped off after the first occurrence of '#'
Fixed bug (8576) where changing organization (in admin UI) would not reset the page and still stay on the previously selected page/object.
New info messages (8750) are shown on the screen in case there is a checksum mismatch when using upKeeper SOS.
Fixed issue with idle logout (8999). Users are no longer logged out when idle and having multiple tabs open on auto updated pages (such as edit computer or device list).
Changed target framework for a JSON package (8748) that was causing error messages when calling API from SOS.
The performance of the device listing has been improved (8854). Not an actual bug, but an improvement.