Ask any IT pro about the importance of rebooting a remote computer and you’ll most certainly hear that this is an absolutely essential task. The primary purpose of a reboot is to bring the computer to a relatively clean state; caches get cleared, memory gets flushed, and you are given the opportunity to start anew. This “clean-sheet” is often required if a computer’s performance is shaky or requiring repair, which makes the auto-reboot function an absolute must-have during a technical support session.
Furthermore, technicians often install software patches and updates that usually require a reboot afterwards. Without a remote reboot feature, such tasks would otherwise require a termination of the support session and a new session to be started following each reboot.
In many instances, a computer may be seriously infected to a point where it can function only in safe-mode. This starting point for the technician can be easily reached by rebooting the remote computer into safe-mode and running anti-virus software to cure infected files.
See continuation of post (Part 3): Unattended Access to a Remote Computer
See previous post (Part 1): File & Clipboard Transfer
Register now for a fully featured 15-day free trial of Techinline
