This article assumes that an UltraVNC policy script exists
If not exists than UltraVNC policy, this is created under Scripting | Configuration Policies | Windows UltraVNC Wizard, or access the direct link at http://SMA_HostName/adminui/kbot_vnc.php
Note: Always test scripts on a few non-production systems to ensure proper function before deploying to production systems.
This template enables you to create a script to distribute UltraVNC to Windows® devices. UltraVNC is a free application that enables administrators to log in to devices remotely. For more information, see http://www.uvnc.com
Go to the Windows UltraVNC page:
1. Go to the Scripting.
2. From the Scripts tab, click on the VNC script created using the Wizard.
Note: Best practice would be to rename this script with the UltraVNC version and save. This will allow you to use the prior version and be able to distinguish between versions.
3. Scroll down and click the Duplicate button.
4. On the Scripts tab, find Copy of UltraVNC Policy and click it.
5. Modify the name to reflect the version of UltraVNC being used. It will be just above the Save button
6. The files that are the dependencies for this script are now visible.
7. Mouse to the right of the current Ultra VNC Setup.exe dependency and click the trash can symbol (this will be invisible until the link to the .EXE is moused over)
8. Add new dependency and browse to the updated version installer for VNC that has been created and downloaded to the client system (downloaded from UltraVNC website)
9. Under Dependencies click the link for ultravnc.ini and edit it with the desired setup parameters, this information can be referenced at the Ultra VNC website and an example is provided below.
Example:
[Setup]
Lang=en
Dir=C:\Program Files\UltraVNC
Group=UltraVNC
NoIcons=0
SetupType=server_silent
Components=ultravnc_Server_S
Tasks=installservice,startservice,installmirror
10. In the On Success portion of the script locate the line that lists the name of the VNC installer and edit it to reflect the name of the new installer (for this example, it is line 12)
11. Save the script and test on a system which does not have any version of VNC currently installed.
Warning: Installing VNC on top of an already installed version of VNC (any version) will trigger a failure in the installer which causes a reboot.
If an offline VNC script is deployed to a system that has VNC, the only way to recover is to boot that system into safe mode and delete the script.
Suggested actions to help prevent this from occurring:
A. Use only Online KScripts unless the specific functions of the Offline KScripts are needed
B. Manually duplicate the On Success steps under remediation and delete them from On Success. Then set up a Verify step to check for the presence of a file and point to the location where VNC might be installed on the client systems. For the On Success have it write a note indicating VNC is already installed. You will then be able to use the Search Logs feature to search for systems that had the script executed against them and already had VNC installed and the version can then be manually checked in Inventory or by a report.
C. With ample time for completion based on check-in and scripting settings, and accounting for systems that may not be powered on, create a script to first uninstall VNC.
Note: If you are deploying to a Windows 7 or 2008 R2 server you will not be able to send CTRL+ALT+DEL by default. The following Group Policy will require editing:
Computer Configuration | Administrative Templates | Windows Components | Windows Logon Options
Set the policy to Enabled with the setting of Services
Referenced from VNC Forums:
http://kb.realvnc.com/questions/91/I+cannot+send+a+Ctrl-Alt-Delete+combination+to+my+Windows+7+computer,+through+VNC
