Modifying an existing script using k1000
I enabled the ultraVNC install script across our network and it seems to be working great with the options I selected from the configuration policy wizard for the setup. I was wondering what the best way was to install a newer version of ultra vnc using this wizard.
My thought process is that I will need to go into the script it creates once I run the confiuration policy and set the options... and modify the .inf and .ini and push the new setup.exe manually, which will take some time. I was wondering if anyone knew of a way to save the dependencies so the new setup.exe you push will become the default (and the install script to reflect the new setup.exe, the new .ini, and the new .inf) when you run the configuration wizard the next time.
I hope this question makes sense, and someone is able to help me with this as I am new to kbox scripting.
Answers (5)
You can change the software version by creating a new script with the UltraVNC wizard or by modifying your current one. Replace the installer dependency with the newer version. Also make sure to reflect the changes to the filename in the task steps at the bottom of the script page.
In v5.4 of the K1000 1.0.9.6.2 is the default version. 1.1.8.0 is the current stable version that adds full support for windows 8.
Comments:
-
Thank you. That's what I ended up doing yesterday. I will push this down to my test system today and see what happens. I appreciate your response. - Strangeronfire 11 years ago
Change a registry key or copy a .txt file down to the machine as part of the script. Change your verify to look for the updated reg key or .txt file. If it does not exist then remediation will run the script.
Comments:
-
uhm...what?
Maybe my question above was confusing. I'm looking for a way to change the software version that is installed under "Configuration Policy" such as the ultra vnc script it creates. I would like to install a newer version of ultra VNC instead of the old version that gets installed using the configuration policy wizard. - Strangeronfire 11 years ago
I think I may have traveled the same journey you have about a year ago. Things may have changed but will be looking soon as we are not using the latest UltraVNC.
What I did back then was get the http://vnced.sourceforge.net msi packager. Then I used Orca to modify the version to something I can track in kbox. Pretty simple actually.
I did other customizations such as hiding the tray icon, setting the password, and running the service.
In my script I added a line to delete the viewer binary as standard users wouldn't need that and deleting the Start > All Programs > UltraVNC menu structure.
<?xml version="1.0" encoding="utf-8" ?>
<kbots xmlns="http://kace.com/Kbots.xsd">
<kbot>
<config name="UltraVNC Service 1.0.9.6.1 32bit" type="policy" id="309" version="1357581040" description="Ready - Installs UltraVNC Server only no icons - ws">
<dependencies>
<dependency name="/packages/kbots/309/UltraVNC 1.0.9.6.1.msi" checksum="10135f56c7d85947ddf01f3dee65b3c7" />
</dependencies>
<execute disconnected="true" logged_off="true">
<schedule minutes="0" hours="11" daysOfMonth="*" months="*" daysOfWeek="*" />
<event name="NOW" />
</execute>
</config>
<compliance>
<verify on_failure="break" attempts="2">
<on_verify_success>
<log_message type="activity" message="Installing UVNC 1.0.9.6.1 Service" />
<launch_program path="SYS" program="msiexec.exe" wait="false" parms="/i "$(KACE_DEPENDENCY_DIR)\UltraVNC 1.0.9.6.1.msi" /qn" />
<launch_program path="SYS" program="cmd.exe" wait="true" parms="/C "rd /s /q "$(KACE_DEPENDENCY_DIR)""" />
<launch_program path="SYS" program="cmd.exe" wait="true" parms="/C del /q "C:\Program Files\UltraVNC\vncviewer.exe"" />
</on_verify_success>
<on_verify_failure>
<on_remediation_success>
</on_remediation_success>
<on_remediation_failure>
</on_remediation_failure>
</on_verify_failure>
</verify>
<verify on_failure="break" attempts="1">
<file_exists path="C:\Program Files\UltraVNC\" file="vncviewer.exe" />
<on_verify_success>
<launch_program path="SYS" program="cmd.exe" wait="false" parms="/C del /q "C:\Program Files\UltraVNC\vncviewer.exe"" />
</on_verify_success>
<on_verify_failure>
<on_remediation_success>
</on_remediation_success>
<on_remediation_failure>
</on_remediation_failure>
</on_verify_failure>
</verify>
</compliance>
</kbot>
</kbots>
The UltraVNC 1.0.9.6.1.msi is the only dependancy file I upload to the script. This has only been deployed to XP machines so far, but, will be testing it on Win 7 in the next push.
Create a copy of the script. At the bottom of the script edit Choose
To edit the policy using this editor, click here
Attach your new version of VNC as a dependancy to this script.
Edit Step 12 specifically to reflect this change.
| Directory: | |
| File: | |
| Wait for completion | |
| Parameters: | |
The rest look okay but IM not 100 percent sure.
Save and run
Comments:
-
The problem is this was put together using the kace wizard including answer files and such to your liking. There is no one msi or other binary used to accomplish the customized install. You have to repackage it. - worzie 11 years ago
Kace has a article about this.
http://www.kace.com/support/resources/kb/article/how-to-update-vnc-installations
Comments:
-
I think I tried this howto once. I'll have to try again soon, but I'm pretty sure there was something that prevented me from using it. I think there was something different in the package that no longer works with the wizard. - worzie 11 years ago
