Re mote Control: So Much More Than Just A Clicker By Mike Fratto   In this age of telecommuting, users expect more from remote connectivity than just file transfers: They need to be able to access services, such as network volumes, network applications and remote print services, and keep multiple file trees synchronized with network versions. And, as for those file transfers, remote users need connections that are more secure than Internet links via FTP and Web servers. For their part, administrators have to support telecommuters who often are using more complex software than their peers were five years ago and may be less technically savvy. Is there one application that can address all demands? If you answered "remote control," you just may be on the right track. Remote-control applications let you connect to another computer on the network or over dial-up lines and direct the remote computer as if you were at the console: You can launch applications, map drives and configure the desktop computer. By providing unprecedented access to the desktop, remote-control applications are ideal for helpdesk personnel. For example, if a user is having difficulty accomplishing a task, a helpdesk staffer can connect to the user's desktop and see exactly what the user is doing. The helpdesk staffer can "take over" the user's machine and walk him or her through the task while he or she watches. Mobile users can connect to their desktops and remotely run applications that they otherwise wouldn't be able to use. However, because response time is generally slow, this method shouldn't replace local applications. Typically, remote control is useful for getting at hard-to-reach apps or performing quick fixes to documents. Finding the be st remote-control package for your enterprise requires a thorough understanding of your network configuration, application needs and security policies . Several packages offer different features and methods for accomplishing the same tasks. I regularly use Stac Electronics' ReachOut 7.0, Symantec Corp.'s pcANYWHERE 7.5 and Traveling Software's LapLink 7.5, and have tested others. It's All in the Features Remote-control application feature sets are becoming standardized. How a vendor implements these features makes a big difference--and will determine if a brand is right for your organization. First, make sure the package supports the network protocols you need. IP/IPX is sufficient for most networks, but many networks use NetBIOS and Banyan VINES. Also, note that some applications are designed to limit the number of concurrent connections on a workstation while others are limited only by the resources of your desktop. In some packages, you may be confined to a certain number of connections base d on network protocols. For instance, only one IP connection may be open while multiple IPX connections are allowed. For helpdesks and power users, multiple concurrent connections are a must. A busy helpdesk may be handling a large support operation while installing software and upgrades and monitoring the progress of each support operation. Operating system support also varies among remote-control packages. Choose a package that provides the connectivity you require. In today's heterogeneous networking environment, you will find a mix of Windows95/3.x/NT and Macintosh desktops and possibly some old DOS machines. Using an application that supports all your desktops will reduce the number of applications you need to manage and will provide greater interoperability. Many vendors supply applications for each operating system, but only a few provide support in one package. Of course, not all functions may be available for all operating systems, but basic remote control and file transfer features should be comm on. Look for backward compatibility if you're upgrading apps so that you don't have to keep multiple versions on your network or desktop. To download an Adobe Acrobat .pdf format version of the Remote Control Software Buyer's Guide charts, click here.

Updated April 8, 1997