Loading Profile...
Why does Ultra 1.0.2 get installed when I try to "push install" 104 to my computers?
Also, when I do a push install, VNCScan seems to install the 1.0.2 version even when I am trying to do the 1.0.4 of Ultra. I can tell because it will create a service "winvnc", not "winvnc.exe" and it install to the "ORL" directory.
I’m confused
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Was UltraVNC 1.0.2 previously installed on the remote computer? If so, try uninstalling UltraVNC from the old computer prior to deploying 1.0.4.
You can do this by right-clicking the computer, choosing VNC Management, and then uninstall VNC from the computer.
I think that there's a bug that is not cleanly upgrading some computers without this manual step. This could confirm it. -
Inappropriate?This is on a fresh install. The ORL directory is created on the Push install of 104. Any ideas?
I’m confused
-
Inappropriate?I'm confused, too. Are you sure that you chose "Ultra104" instead of "Ultra" while creating the deployment profile?
Would it be possible for you to post the output of the deployment window while deploying so that I can troubleshoot it? You can copy/paste it into here. -
Inappropriate?When I use the "Push Installation" the command box disappears when it is finished running. I am runnign the Push install as a connection option in group preferences.
-
Inappropriate?Ok, this is starting to make more sense to me as to where the bug might be. You're telling the program to remove and re-push it with each connection attempt using the settings in the group properties?
-
Inappropriate?Yes... I am using the Push install as necessary, as it is the only thing that will work. Though it does not seem to push teh Ultra104, like I want it to.
The only reason I have done this is because the Ultra104 service will nto install and let me make a connection. -
Inappropriate?I've created a remote script to clean up any fragments of VNC from remote systems. You can download the wizard that will install the script into VNCScan for you at http://www.bozteck.com/downloads/unin...
Close VNCScan, and then run the MSI. It should just silently put things into place so that when you open VNCScan back up, it will be an available script in the "Remote Scripts" menu.
Try running that against the computer in question to see if this puts things back into order. After it has ran, you should be able to deploy UltraVNC 1.0.4 using the standard deployment wizard and the service should install correctly.
I’m Hopeful
-
Inappropriate?Gives me a System.IO.Directory not found exception. I am runnign Vista.
I will try it on XP -
Inappropriate?At what point do you get that error? A new version of VNCScan was just released that may fix this, anyways.
You may want to upgrade to it and give it a try. -
Inappropriate?Steve - When I ran it on Vista it said this as soon as I ran the script. However, I noticed it was because the script was looking for "Documents and Settings" like iin XP. So, I removes the reference in the script to the "Documents and Settings" and included all the files from the VNCScan "Jobs" directory and it seemed to run without error. However, it still did not allow me to deploy and get the winvnc.exe service running on the remote machine.
-
Inappropriate?That's bizarre. Have you tried installing the new version of VNCScan just released today and trying with it?
-
Inappropriate?No, I will try that!
Thanks,
Rick -
-
Inappropriate?Great! You may want to get the June 24 version if you run into a problem deploying Ultra104 to computers that have not had it installed before.
I’m happy
EMPLOYEE
