MI for Ultra VNC x64 on Windows 7
Hi Everyone,
I made a package for UltraVNC x64 to do a managed install on x64 systems. It was pretty simple seeings how UVNC records response files now. The package works great on Win 7 X64 if I run it by hand, running it as a distributed install it doesn't seem to do anything other than download the MI. I know the machine I'm testing on works with other MI's (Trend, Office 07 so far), I'm guessing it is a UAC issue, but not really sure. I have the installer recording a log file to the "temp" directory, but I am unsure where this is for local system accounts on windows 7. I did not write any custom scripts to do this, its just a command line. The MI is just a zip file containing the UVNC x64 installer, and the inf file. The hour I have wasted on this is already too much for just VNC, I'm hoping someone can give me some ideas of what I'm missing, it has to be really easy.
I made a package for UltraVNC x64 to do a managed install on x64 systems. It was pretty simple seeings how UVNC records response files now. The package works great on Win 7 X64 if I run it by hand, running it as a distributed install it doesn't seem to do anything other than download the MI. I know the machine I'm testing on works with other MI's (Trend, Office 07 so far), I'm guessing it is a UAC issue, but not really sure. I have the installer recording a log file to the "temp" directory, but I am unsure where this is for local system accounts on windows 7. I did not write any custom scripts to do this, its just a command line. The MI is just a zip file containing the UVNC x64 installer, and the inf file. The hour I have wasted on this is already too much for just VNC, I'm hoping someone can give me some ideas of what I'm missing, it has to be really easy.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
GillySpy
14 years ago
I always start with this guide:http://www.kace.com/support/customer/faq/index.php?action=artikel&cat=4&id=821&artlang=en
The temp directory is probably c:\windows\temp but to find out you could use this FAQ to examine the environment:
[link]http://www.kace.com/support/customer/faq/index.php?action=artikel&cat=5&id=731&artlang=en[/link]
MI's can be exported if someone had a working configuration perhaps they could share it? Even if it doesn't work that would help to eliminate some variables in the equation.
The temp directory is probably c:\windows\temp but to find out you could use this FAQ to examine the environment:
[link]http://www.kace.com/support/customer/faq/index.php?action=artikel&cat=5&id=731&artlang=en[/link]
MI's can be exported if someone had a working configuration perhaps they could share it? Even if it doesn't work that would help to eliminate some variables in the equation.
Posted by:
lindsamw
14 years ago
I verified the package ran under local system using the psexec advice from the faq. Still having issues with it, so I went and got the VNCED ultravnc msi creator (http://vnced.sourceforge.net) will let you know how that goes.
Posted by:
lindsamw
14 years ago
Tried the VNCED MSI Creator, it did create me a package I liked for the most part, but it has a couple of issues for me.
1. It installs a 64bit piece of software into the c:\program files (x86) folder.
2. It changes the name of the software, so in inventory, it just shows up as UVNC, not as UVNC 1.0.8.2 or whatnot.
Going to play around with my package some more, see if I can figure out why it won't run through the kbox.
1. It installs a 64bit piece of software into the c:\program files (x86) folder.
2. It changes the name of the software, so in inventory, it just shows up as UVNC, not as UVNC 1.0.8.2 or whatnot.
Going to play around with my package some more, see if I can figure out why it won't run through the kbox.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.