UltraVNC 1.0.9.5 Released-require VNCed UltraVNC MSI Creator for latest version of Ultravnc 1.0.9.5
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2011-01-04
I too would like VNCed to add the new version of UltraVNC (1.0.9.5) to the MSI creator. The old version works great for WinXP and below. The new verison of UVNC enables the ctr+alt+del command from the Windows login screen in Win7 and Server 2008.
Please update VNCed to work with Windows 7!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Version 1.1.9 is now available which includes UltraVNC 1.0.9.5. There are separate bat files for 1.0.8.2 and 1.0.9.5.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2011-01-18
Great project, Mike.
I have inherited a domain where a previous version of UltraVNC was installed via the .exe file at each client. I have found that when trying to deploy one of your MSIs that I create, it seems to install along side the existing version, rather than upgrading the current one. This causes obvious conflicts between the new and old versions, where neither will work.
Is there a way to include a "this is an upgrade" option when creating the MSI files?
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After manually uninstalling the old ultravnc and running the MSI generated using "UltraVNC 1.0.9.5 - STEP2.build_ultravnc_msi.bat" the version of VNC listed in the properties tab is 1.1.0.2. This is the same as before installing with the new MSI. Checking "about" in the icon from the system tray reports version 1.0.2 build Jun 18 2006. Whats up with all that?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
how to make only 1 instance of winvnc to run @ startup ( when user logins 2 winvnc are running )..i don't want for user startup, it should be automatic in service with local service…irrespective of logins only 1 instance should run.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have just double checked. You end up with 2 winvnc.exe processes running in task manager, this is the case even when using the official UltraVNC installer.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
yes there are 2 winvnc running ( 1 has user & another as System ). Can't it be stopped from running. I want it to run as local service. ( automatic & system service )
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
seems like in 1.095 both are running as System Service. ( vnc viewer was not able to connect to destination IP if both instance is running as System Service )
in 1.09.6, one instance is user & another is System. I will do more testing on other machines & I will update whether im ok with it or not. ( now vnc viewer is able to connect to destination machine IP when 1 instance is user mode & System Service Mode )
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
UltraVNC 1.0.9.5 Released-require VNCed UltraVNC MSI Creator for latest version of Ultravnc 1.0.9.5
I too would like VNCed to add the new version of UltraVNC (1.0.9.5) to the MSI creator. The old version works great for WinXP and below. The new verison of UVNC enables the ctr+alt+del command from the Windows login screen in Win7 and Server 2008.
Please update VNCed to work with Windows 7!
I will try and get an update out in the next couple of days. I haven't got Win7 or Server 2008 so will require feedback.
Version 1.1.9 is now available which includes UltraVNC 1.0.9.5. There are separate bat files for 1.0.8.2 and 1.0.9.5.
Great project, Mike.
I have inherited a domain where a previous version of UltraVNC was installed via the .exe file at each client. I have found that when trying to deploy one of your MSIs that I create, it seems to install along side the existing version, rather than upgrading the current one. This causes obvious conflicts between the new and old versions, where neither will work.
Is there a way to include a "this is an upgrade" option when creating the MSI files?
Thanks!
As the original wasn't installed via an MSI the upgrade option won't work.
You could do a batch file before installing the MSI that nukes the existing copy.
Which directory is the old version installed in? as I would have expected the MSI to overwrite existing files in the same directory.
After manually uninstalling the old ultravnc and running the MSI generated using "UltraVNC 1.0.9.5 - STEP2.build_ultravnc_msi.bat" the version of VNC listed in the properties tab is 1.1.0.2. This is the same as before installing with the new MSI. Checking "about" in the icon from the system tray reports version 1.0.2 build Jun 18 2006. Whats up with all that?
something must have gone wrong with the uninstall of the old version, the 'about' of the new version displays 1.0.9.5
If you go to c:\program files\ultranvc\winvnc.exe ; what is the version of the exe file? it should be 1.0.9.5
how to make only 1 instance of winvnc to run @ startup ( when user logins 2 winvnc are running )..i don't want for user startup, it should be automatic in service with local service…irrespective of logins only 1 instance should run.
Which version of the MSI Creator are you running?
I have just double checked. You end up with 2 winvnc.exe processes running in task manager, this is the case even when using the official UltraVNC installer.
yes there are 2 winvnc running ( 1 has user & another as System ). Can't it be stopped from running. I want it to run as local service. ( automatic & system service )
seems like in 1.095 both are running as System Service. ( vnc viewer was not able to connect to destination IP if both instance is running as System Service )
in 1.09.6, one instance is user & another is System. I will do more testing on other machines & I will update whether im ok with it or not. ( now vnc viewer is able to connect to destination machine IP when 1 instance is user mode & System Service Mode )
You may be better off asking for help in the UltraVNC forums as they will know more about the inner workings of the service.
Does the latest version of VNCed work with 1.0.9.6.1 ?