Remote Desktop VNC Integration
Remotely managing desktop systems is an integral element of most Lieberman Software solutions. Our Enterprise Random Password Manager, Random Password Manager, User Manager Pro Suite, Service Account Manager, Task Scheduler Pro, and COM+ Manager products allow desktop management via the free remote control program VNC (Virtual Network Computing) and/or Microsoft’s Terminal Services (or RDP).
Our products can launch an RDP session to target Windows systems without any additional components. However, in order for these products to integrate with VNC, you must first download and install our free VNCPass tool and your preferred version of VNC.
See below for instructions on installing and using VNCPass to connect to remote systems using VNC from within our products.
The High Cost of Remote Desktop Software
Desktop remote management has been the domain of commercial programs such as Symantec PCAnywhere, Netop Remote Control, and others. Due to the high cost of these products, many organizations forgo this capability or investigate free solutions, such as the open source program VNC.
The Low Cost of Open Source Remote Control Desktop Software
Although VNC is an exceptional value, it does have some problems when deployed on more than a few machines. VNC does not have any inherent grouping or discovery mechanism, so users must know the name or IP addresses of machines they need to connect with. Remote installation/removal/configuration on machines that lack VNC is another problem.
We have solved these issues in VNC, not by changing the original VNC program, but by allowing VNC to be installed and managed from within our products. Getting to one or more remote desktops using VNC from within our products is as simple as highlighting the machines and clicking the “Auto VNC Connect” option from the context menu.
Our products will determine whether to use the name or IP address, will remotely install the product or start the service if needed, and will connect to the remote system whether or not the remote password for VNC is known – as long as you are the administrator of the remote machine(s). For extra security, our products can shutdown and/or remove the remote VNC service automatically after you have completed the VNC session. We also push out fixed and/or random passwords to all of your VNC installations.
If you have been using VNC, but have been dissatisfied with its poor security and distribution issues, our products’ management of VNC resolves these problems. If you prefer to use Terminal Services, we provide one-click access to all machines that have Terminal Services or RDP installed and enabled.
VNC and Terminal Services management are included in our products at no charge for customers that own our products and are currently within their maintenance support period.
If you would like help getting started with remote desktop access, or have any questions about this technology, please contact us at:firstname.lastname@example.org.
To access systems (usually servers) with Terminal Server on them, you will need the Remote Desktop Connection facility already installed on Windows systems. (For Windows NT and Windows 2000, you will need to install the component from Microsoft’s web site.) You can connect to systems with Terminal Server by highlighting the systems, right-clicking, and selecting the Terminal Server option on the menu.
Step 1: To use VNC with one of our products, you must first download and install the full version of VNC (both client and server version). You do not have to activate the server service of VNC to run on your system, only the client must be active. You can download VNC from: http://www.realvnc.com
An alternate version of VNC called TightVNC (containing more features) can be downloaded from: http://www.tightvnc.com
There are also non-freeware versions of VNC that can be downloaded.
We do not have VNC itself available for download.
Step 2: Our products do not directly incorporate any GPL code from VNC. To provide a bridge between the open source code base of VNC and our proprietary code, you must install a component known as VNCPASS, available from our web site. This component is available in source form as well as compiled binary. VNCPASS is licensed according to the GPL open source license agreement. You may freely download and share this code without any payment to us.
When our products detect the existence of the VNCPASS component installed on your system, the VNC management menu items become available automatically. Our VNC management allows you to highlight any group of systems, right-click on the context menu, and automatically activate a VNC session using the VNC client already on your machine.
We also provide the ability to push the VNC program components onto any machine of your choice and activate the service remotely. This allows you to see the desktop of any system that you administer without having to manually visit the machine and install VNC. If you did not install both the client and server files for VNC on your machine, it is impossible for us to ship the server components to the remote machines as needed.