View Articles by Category

There are no sub categories

Category » VNC Deployment Toolrss button

There were 9 articles found in this category:

  1. questionWhich Deployment Tool version do I use with which VNC release?
    Each version of VNC has a parallel version of VNC Deployment Tool. The correct versions must be used together: VNC Deployment tool 1.6.21 is compatible with VNC 5.0.5 VNC Deployment tool 1.6.20 is compatible with VNC 5.0.4 VNC Deployment tool 1.6.19 is compatible with VNC 5.0.3 VNC Deployment t ...
  2. questionVersion numbers used in VNC Deployment Tool do not match those in the VNC Server About dialog
    VNC Deployment Tool reports version numbers where the revision numbers are 60,000 lower than the actual numbers, as seen in VNC Server's About dialog. For example, VNC Deployment Tool claims the local version is "5.0.0.24153" but the number given on the About dialog is "5.0.0.84153".
  3. question"SCManager: CreateService failed: 1073" error in the remote logfile
    If you are having problems deploying to remote machines using the VNC Deployment Tool, check the logfile on the remote machine for the following: <11> 2012-10-16T14:31:41.507Z HOSTNAME vnctool[5808]: SCManager: CreateService failed: 1073 <11> 2012-10-16T14:31:41.507Z HOSTNAME vncto ...
  4. questionI'm having problems with VNC Deployment Tool
    Typically, most error messages you get from VNC Deployment Tool indicate a problem with the underlying network configuration---often a permissions problem. That is the case with anything that says "Access denied" or similar. 1) Verify that the problem is not with VNC Deployment Tool by running ...
  5. questionRecommended scan options for VNC Deployment Tool
    If you scan by selecting Network Neighbourhood or Entire Network, it uses NetBIOS. This is a consequence of the API we use and it is not possible to use DNS instead. If you scan by IP address, it will use DNS to determine the hostname. If you use DHCP, this might not be a viable solution as t ...
  6. questionUsing the VNC Deployment Tool on Windows 7
    When running the VNC Deployment Tool on Windows 7, you will need to: Ensure that you're logged on as the Domain Administrator Right-click on the VNC Deployment Tool icon and "Run as administrator.." Please note that the "Credentials" feature does not currently work as intended on the Windows 7 ...
  7. questionDoes VNC Deployment Tool support MSI?
    The current VNC Deployment Tool does not support MSI as an installation method. This is being looked in to for future release versions.
  8. questionWhat port(s) does VNC Deployment Tool run on?
    VNC Deployment Tool uses Microsoft's standard remote access APIs rather than using specific ports directly. Some firewalls have built-in rules to enable these, usually called "Enable file sharing" and "Enable remote administration". If not, then you could try opening ports 135, 137-139 and 445. ...
  9. questionHow to enable logging at the deploying computer and for each target computer
    VNC Deployment Tool creates a log file on the target computer at C:\vnctool.log, by default. If the C:\ directory is not writeable, the target computer's log file location can be changed by creating a Registry key HKCU\Software\RealVNC\VNCTool\installLog on the deploying computer and enter a sui ...