The version of UltraVNC included with the KBOX appliance shows only a black screen when attempting to control vista clients.

I have uploaded the latest version of VNC to the dependencies for the script and changed the executable path. It is, therefore, installing the new version, but the password is not established on the server, and the other desired customizations(No system tray icon and such) do not take effect.

How can I update the version of VNC that is installed with the KBOX and still manage to configure the installation properly?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Step One:
  • Install VNC on a test machine (Vista or XP)
  • Configure all settings including password
  • All settings will be stored in a file called "ultravnc.ini" in "C:\Program Files\UltraVNC"

Step Two:
  • Modify the UltraVNC Script in the KBOX to contain the following dependencies:
Ultravnc.inf
Ultravnc.ini
UltraVNC_105_Setup_W32.exe


Step Three:
  • Modify the Task Section to contain the following:
    • On Success:
  1. Run a batch file
    • Script Name = InstallVNC
    • Batch File Contents:
      mkdir "c:\program files\ultravnc"
      REM Copy File from kace directory and put into vnc directory
      copy "c:\program files\kace\kbox\packages\kbots\1245\ultravnc.ini" "c:\program files\ultravnc"
      REM 1245 is the script number and will mostly be different on your kbox
    • Be sure to include the full path where the ultravnc.ini file will resides when the script is executed
    • To determine the script number (1245), use the following FAQ: How to determine the Script Number?
    • For the picture example, it showed that the script number is 1245
    • Program Files\Kace\kbox\packages\kbots\1245

  2. Launch Program (need to modify this line to launch the new UltraVNC_105_Setup_W32.exe)
[blockquote]
  • Directory = $(KACE_DEPENDENCY_DIR
  • File = UltraVNC_105_Setup_W32.exe (note: file name will vary depending on the version of VNC)
  • Parameters = /loadinf="$(KACE_DEPENDENCY_DIR)\ultravnc.inf" /verysilent
[/blockquote]



Reference:

How to Determine the KBOT Script Number A KBOT, or Script, is an action that you can create in the KBOX and deploy to your machines. It is valueable during troubleshooting to know what number your script is.


To do this find the script in the list of scripts and right-click on it. Then choose "copy link location" (or the equivalent for your browser) and paste that somewhere.

You will get something like this:

http://kbox/adminui/kbot.php?ID=21

The script number in this example is 21

This is the same number that will appear in kbots_cache files, localexecutation.dat and other resources when troubleshooting kbots.

Regards,
Ted

Answered 08/12/2009 by: KACE SEs
Yellow Belt

Please log in to comment
0
Does the above proecdure get around Windows Defender & Windows Security issues?
I currently push out VNC to all my computer but Vista will not allow the vnc program to start without user intervention.
Answered 10/05/2009 by: kdasanmartino
Second Degree Green Belt

Please log in to comment
0
Kris,

Do you have UAC disbaled?
Answered 10/05/2009 by: DContreras
Orange Belt

Please log in to comment
0
No, I don't think so. Is there a way to disable and enable via Kbox?
Answered 10/05/2009 by: kdasanmartino
Second Degree Green Belt

Please log in to comment
0
I believe that the user interaction is caused because of the change to post 1.0.2 VNC installers where they actually go out to the internet to download the latest files from the web site. In version 5.0 of the KBOX, we have repackaged the VNC installer to avoid this. Trial KBOX is not upgradable currently, but we should be able to post the repackaged VNC to be able to have you set it up with the trial so that it is completely silent. Let me check into it.
Answered 10/05/2009 by: chrisgrim
Senior Purple Belt

Please log in to comment
0
I am a current Kbox user that is running Version 5.0.
So all I need to do is repackage the VNC to get around this?
Answered 10/05/2009 by: kdasanmartino
Second Degree Green Belt

Please log in to comment
0
Actually, if you are a current KBOX user with v5, you don't have to do anything. You just need to deploy VNC from the UltraVNC Wizard:



Answered 10/05/2009 by: chrisgrim
Senior Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Share