On public computers, you’d often find that no executable files (EXEs) are allowed to run. This is for a reason, of course: a computer with Internet connection is a valuable resource and thus a target for exploits. Antivirus is not a sufficient defense for publicly accessible computers, and even executable file restrictions do not guarantee your computers are safe.
Remote access is obviously a very sensitive (often we’d call it intimate) matter. So, security is a major concern here. Many remote desktop software vendors claim their products are secure, but sometimes the details are a bit vague. Let’s try and figure out what we need to know when choosing remote access tools.
Remote support saves time and effort but what if your user can’t get online? This simple troubleshooting checklist helps you get connected. It might be useful even for experienced technicians, especially at the end of a long business day.
In modern times web browsers are the most popular and widely used software. No doubt the Internet is playing an unprecedentedly important role in people's personal and work life. Web browsers provide access to zillions of bytes of information and many thousands of tools used in workflow.
One of such browser-based tools is DeskRoll. It enables access to remote machines without installing additional software on the controlling device.
You are supporting a customer remotely but suppose that you (or they) have no Internet connection. What's next?
Remote access tools are the bread and butter of today’s support technician. For many remote access needs, traditional tools (bundled with the OS, provided by the OS vendor, etc.) are used: RDP, SSH clients/servers, Telnet, etc. Let's see how they compare with each other.
Remote technical support is an appealing alternative to traditional on-site support. Remote support means accessing your client’s computer remotely to do system modifications, updates or fixes. Of course, it requires certain skills and tools, but sometimes there’s no viable alternative.