We still us a nicely skinned UVNC SC... was looking around for updates/alternatives when I came across ChunkVNC and this fork.
I have a few questions that I could not find answers to...
Is this fork going to merge back into the ChuckVNC project? I see some progress on ChuckVNC that would be helpful, but unsure if the Fork gets the benefit or not... specially some of the 3.3 updates coming down. I just prefer the Click a Technician Option like UVNC SC... but I also want the ability to install as a service and remote into the computer at will without a user there.
My second question/feature request is that I have a hell of a time tracking remote assistance calls/remote controls. We basically leave it to the tech to enter it into their timesheet, which they ofter do not do.
Is there any way, plan to setup a track or log? Simply put, I would know which computers are on which network / client location... I want to see a technican report, which computer was connected/disconnected and for how long... Run a report on a client basis (for billing), etc... Is this something that would be a possible feature for this fork? Or is this repeater specific (maybe even the PHP repeater script side instead of the windows repeater app side)?
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Tech Logging?
Re: Tech Logging?
I just prefer the Click a Technician Option like UVNC SC...
Interesting, I've never liked this option because it involves the customer having to click more and that's never a good thing.
The other problem with choosing a tech is that you will only be choosing one ID number for that tech, if the tech wants to control multiple InstantSupports choosing a static ID won't work.
I could be way off here but I just don't see the benifits of the "choose your tech" idea, I'd much rather have ChunkViewer display the active ID numbers.
My second question/feature request is that I have a hell of a time tracking remote assistance calls/remote controls. We basically leave it to the tech to enter it into their timesheet, which they ofter do not do.
Sounds like more of an employee problem.
I'll add this to the feature requests.
Is there any way, plan to setup a track or log? Simply put, I would know which computers are on which network / client location... I want to see a technican report, which computer was connected/disconnected and for how long... Run a report on a client basis (for billing), etc... Is this something that would be a possible feature for this fork?
Really it boils down to this:
This project is a fun side thing for me to play with, I released it open source so that anyone can add the features they wish at any time. When I get a few ideas together that I think will benefit the project I do some coding. I really like the ideas that you have here but there are some other things that need to happen first for this stuff to happen.
maybe even the PHP repeater script side instead of the windows repeater app side
ChunkVNC 3.2 includes a Perl repeater in the Repeater\Linux directory.
Interesting, I've never liked this option because it involves the customer having to click more and that's never a good thing.
The other problem with choosing a tech is that you will only be choosing one ID number for that tech, if the tech wants to control multiple InstantSupports choosing a static ID won't work.
I could be way off here but I just don't see the benifits of the "choose your tech" idea, I'd much rather have ChunkViewer display the active ID numbers.
My second question/feature request is that I have a hell of a time tracking remote assistance calls/remote controls. We basically leave it to the tech to enter it into their timesheet, which they ofter do not do.
Sounds like more of an employee problem.
I'll add this to the feature requests.
Is there any way, plan to setup a track or log? Simply put, I would know which computers are on which network / client location... I want to see a technican report, which computer was connected/disconnected and for how long... Run a report on a client basis (for billing), etc... Is this something that would be a possible feature for this fork?
Really it boils down to this:
This project is a fun side thing for me to play with, I released it open source so that anyone can add the features they wish at any time. When I get a few ideas together that I think will benefit the project I do some coding. I really like the ideas that you have here but there are some other things that need to happen first for this stuff to happen.
maybe even the PHP repeater script side instead of the windows repeater app side
ChunkVNC 3.2 includes a Perl repeater in the Repeater\Linux directory.
http://www.chunkvnc.com - ChunkVNC - Free PC Remote control with the Open Source UltraVNC wrapper InstantSupport!
Re: Tech Logging?
As a stop-gap measure you (cmariotti) could write a script to parse the repeater's log files to get the information you want, after the fact. You'd have to use one of the repeater forks that includes more detailed logging.
You could also script a relatively simple batch file to send some critical logging data to a shared location (file or database) each time a tech runs the program (e.g. "echo %username% >> x:\vnclogging.txt", but obviously much more robust than that, with timestamps et al.).
As supercoe hinted, his project isn't intended to run a full time help desk organization, though it could be the start of one.
You could also script a relatively simple batch file to send some critical logging data to a shared location (file or database) each time a tech runs the program (e.g. "echo %username% >> x:\vnclogging.txt", but obviously much more robust than that, with timestamps et al.).
As supercoe hinted, his project isn't intended to run a full time help desk organization, though it could be the start of one.