I'm having problems with VNC Deployment ToolTypically, 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 regedit and selecting "Connect Network Registry..." from the File menu and entering the name of the remote computer. You should get the same (or similar) error trying to access the remote machine. If you don't, then try browsing to:
(HKLM\SOFTWARE\RealVNC\WinVNC4 if you are deploying legacy VNC Enterprise Edition 4.x)
and adding a value to see if you get an error writing to the registry at that stage.
If the error is not a registry-related API call (eg, RegConnectRegistry, RegOpenKeyEx etc.), for example OpenSCManager, then it might be better to use the Computer Management console to connect to the remote computer and browse the services running on it. Open the Computer Management console > More Actions > Connect to another computer and enter the name of the remote computer.
If neither of the above give an error (ie, you are able to use the built-in Windows tools to examine the remote computer, but are unable to use VNC Deployment Tool), then it's possible you have found a bug.
2) If you are able to verify that the problem does not lie with VNC Deployment Tool, then ensure that you are running it as a user with administrative privileges on the remote computer (domain admin is best) or have explicitly provided suitable credentials using the Credentials command from the Scan menu.
3) Verify that the following are configured correctly *on the remote computer*:
* Remote Registry and Server services are running.
* File Sharing is enabled, but Simple File Sharing is not.
* There is no firewall active.
4) Verify that the built in "Administrator" account is enabled. It is disabled under Windows 7 by default, meaning that attempting to deploy using these administrative credentials will fail with an "Access Denied" message, or similar.
5) Here are some troubleshooting steps to try:
a) Network Neighbourhood uses NetBIOS name resolution so this has to be enabled for DHCP, otherwise you can use IP range scan instead.
b) We don't support different IP ranges (or network segments), but we support the following approach to bootstrap this: if your network is relatively small and static, then you can use a plaintext file for scanning. Enter one hostname or IP address per line and save it with a .nwk suffix. Load it into the deployment tool, select the root node and hit F5 to scan all the hosts. Once it's completed, you can save it back so the scan results are remembered, push VNC Enterprise Edition to all the hosts, or do anything that the deployment tool would have allowed had it discovered the hosts automatically.
c) Check if the RemoteExec service is still running on the target machines. Check this by typing:
sc query type= service state= inactive
If RemoteExec is amongst the entries, delete this by typing:
sc delete RemoteExec
and try running the Deployment Tool again.
Windows Vista and Windows 7 Notes
6) Under Windows Vista and Windows 7, the 'Remote Registry' service is disabled by default (unlike previous versions of Windows). You will need to enable this service on all of your Vista/7 machines.
7) If you're receiving permissions issues when running VNC Deployment Tool on a Windows 7 computer, you may need to explicitly run the application as an Administrator. This is accomplished by right-clicking on the VNC Deployment Tool icon and selecting "Run as administrator".
This list is by no means exhaustive. You will need to contact your network administrator for further assistance if this does not resolve the problem.
Related ArticlesNo related articles were found.
AttachmentsNo attachments were found.
1st of March, 2013