Ultravnc Viewer
Iris Lopez
UltraVNC Server and Viewer are a powerful, easy to use, free software that can display the screen of one computer (Server) on the screen of another (Viewer).
The program allows the viewer to use their mouse and keyboard to control the Server Computer remotely.
UltraVNC is a VNC application that is tailored towards Windows PCs, with several features not found in other VNC products.
Not sure if the UltraVNC viewer supports it but the RealVNC Viewer has an option called Monitor, which allows you to specify the monitor you want to open the viewer on. In my case if I wanted to open the Viewer on my second display I would set the monitor option to \\.\DISPLAY2
You need to find out what how your displays are enumerated though. You may only have 2 monitors, but Windows might refer to them as \\.\DISPLAY3 and \\.\DISPLAY5. I don't know why that happens but it can.
Create a .VNC file for the connection (you can do this while remoted in, it's easier than making one from scratch). Edit the .VNC file in any text editor application and look for/add a line that says:
I agree with the PowerShell idea. I would also look into triggering a scheduled task. Does UVNC leave a log entry in event viewer? If it does you can trigger your scheduled task based on the event ID and run your PowerShell script to email you as it happens.
In line with your quest. A simple powershell/vbs script should do what you need. Both have facilities to send emails. Just setup a scheduled task to detect a change in last modified date and then have the script kick out an email and either the entire log file, or if are using powershell something like this to tail the log file.
The bit that is missing is the file change date code. First you will need to store the last time the file was changed in some text file. Then read it in each time the script is run. Then compare the saved date/time to the log file last modified date. If they are different then kick out an email. The risk is that the log file is updated for some other reasons you will get spurious email messages when unexpected. You may need to parse the last few lines (like with tail) to ensure the last entries were a connect or disconnected. This will clean up the email to only value added notifications.
When I try using the get-content command with the tail and -wait option, the log details never get emailed (until I terminate the command). So that option defeats the purpose of the goal (to have the log updates sent the moment a change is detected).
I have two monitors on my computer and the computer I am connecting to has two monitors. Are there any other settings that I would have to configure? Do they both have to be configured with the same VNC viewer? I am able to connect to that computer which already has TightVNC
I installed the same version of UVNC on both machines. What do I have to do with UltraVNC Server. Do I have to assign ports or something or can I continue to connect to type in the computer name? When you use the UltraVNC Viewer what settings do you use?
zachivie asked about UVNC to a VM using two screens. I am using VMware so if you are using another hypervisor, YMMV. These are the VMware setting, UVNC settings and a screen shot of my UVNC session to the VM.
I had been thinking of making a launcher for this for some time. Then, just this past weekend, it finally sunk in - uvnc is GPL! So, I modified the source to the vncviewer app, so it is now portable (I originally implemented a "-portable" parameter, which is still available below).
What it does thus far:
- bypasses the code that associates itself with .vnc files
- bypasses the code that registers various vnc sound events
- disables the mru (finally decided "who needs a MRU w/o the registry when files work just as well")
- removed the "save as default" option - you can create the .vnc file from the system menu when you connect to the VNC server.
Disabling the MRU is wise. If you're using the app across computers and the drive letter of your device changes between those systems, the absolute paths stored in the MRU lists will be useless. MRU lists, by their very nature, are not very portable.
An expession here, ;). Just my 2 cents: Some people do have permanent machines they log in from, so I think having an MRU, etc. is a good thing (that is, if you can lock people out like I do :D). IMHO a seperate project sounds good. On the other hand, if you do decide to make the MRU otional in your current build, and maybe a few of the other settings, it would be a good idea to offer it as patch.
He added a switch called "-portable," of which one of things it does is disables the MRU. Chances are, if you only intend to use the application from one computer, you're not going to use the -portable switch if the application runs just fine off the USB key already. His -portable switch is just to make it portable-friendly. By their nature, MRUs aren't very portable-friendly.
I put an un hidden email up on a message board a couple of times- and got a bunch nigerian 419 scams. Suggestion: camoflague your email- like myemailloginemailhostercom
Panic, Mayhem, and Destruction- My work here is done.
by default, it loads the MRU into the registry, which is something I'd like to avoid. I was toying with the idea of a separate "vncviewer.mru" file just for the MRU, it is kinda catch-22: the MRU file is nice, but working out the relative paths in it could get tricky; but the options.vnc file is just a normal .vnc file with the last saved settings, including vnc server address, you could just load separate .vnc files, as well.
If you want, I could create a switch to enable JUST the registry MRU, maybe call it "-MRU_ONLY" or "-semi-portable", and have it just disable the file association and the sound event, but leave the MRU in registry?
I've been thinking of creating a .ini-type file, with a similar structure to the .vnc files (since that's what actually gets stored), to implement the MRU. However, this would occupy just as much space on the disk as having separate .vnc files for each connection, with the only benefit of it being in just one file instead of many.
As I said earlier, though, I'm still open to suggestions on this topic, as I'm not totally against it. I've just been creating .vnc files for the connections I commonly use, myself. If I can find a better way to do this, I'll definitely add it to the next release.
Thanks heaps.
Is UltraVNC licensed under the GPL, cause you will need to release the source.
I can host it on my site if you want, send me an email at cubegames[at]gmail.com (I don't care about spam anymore. They all already have me )
----
R McCue
PortaBlog Home and My Website
And before anyone complains about the grammar, I'm so jetlagged that my
hands aren't even in the same time zone...
Yes, UltraVNC is GPL'd, and, once I finish my modifications, my source will be, too. Looks like it may be a while, though - they've changed some of the source structure, and I can't find the version of my source that included the "-portable" switch.
I don't know much about how this would work, but would someone want to take this, package it for U3 and list it on their site? This would be an awesome addition to my U3 drive, and I don't know enough about it to do it myself.
Hi,
is this still on going? the link for the file doesn't work anymore.
I would be interested too. So far UltraVNC is installed on my usb with registry setting deleted from registry and it seems to work fine...
Thanks, I'll be on the lookout !
Yep, still ongoing, just waiting for the 1.0.3 viewer release, so I can make it portable. I tried the same method, at first, and noticed while perusing my registry that there were still several registry settings there. Upon inspecting the source, I realized that I could change that without loosing any functionality (except for the MRU, you'll notice).
Sounds like making a portable-only vncviewer might be a good idea after all. Gimme a few days (probably more like a week, gotta rebuild my PC and a friend's), I'll get right on it. A version that don't need the -portable parameter. Maybe I'll change the target output filename to pvncviewer.exe?
I might just do that, but make an App\VncViewerPortable.exe, using the PAF setup. I'll also have to grab the source files that correspond JUST to the viewer app itself, and include that as an option. Guess it'll keep me busy until the next vncviewer version.
Not yet. I've recently upgraded hardware, replaced a dead drive, and had to reinstall windows as a result. Add to that friends, neighbors, etc keep coming to me with their virus/malware-ridden computers for me to "fix". Finally, I'm still in school, which is also taking up the remainder of what time I have.
With this version, you can create a .vnc file after establishing the connection by clicking the "system menu" (the icon at the top-left corner of the window), and selecting "Save connection info as..." (or press Ctrl-Alt-F5). Next time you start the viewer, click the "..." button and load the file.
Originally the "Save connection settings as default" created a "options.vnc" file in the %temp% folder, but it never got reloaded automatically, so I figured "if it doesn't really do what it looks like it says, why have it there?"
Perhaps I'll eventually put it back in, and have it actually load it at startup (if it's either in the Data directory or in the App directory), but the uvnc crew say another version's on the horizon, so I'll wait until that's been released first.
268f851078