In this section, we present a typical scenario for using this usage model to fix a home PC remotely.

With the popularity of the Internet, more and more people access it to download software, chat, and search for information. As a result viruses are common and prolific and they cause operating problems for home PC users. With the usage model proposed in this paper, the MSP technician is able to remotely fix viruses, and the only thing the user has to do is call the technician and complete several simple configurations under the guidance of the technician. Figure 8 describes the whole work flow of this usage model from the time the user calls the technician to the time the problem is fixed and the remote connection is disabled.

The PC user only needs to take the following actions to get his/her PC problem fixed:

1. Call the IT technician.
2. Enter the configuration UI under the guidance of the IT technician.
3. Configure the IP address and TCP port of the service. Configure the password for the admin user account.
4. Read the UUID in the configuration UI and convey this information to the IT technician.
5. Enable the remote connection of his/her machine and wait for the IT technician to fix the machine.
6. Disable the remote connection after the IT technician fixes the problem.

Figure 8: Workflow of a typical usage scenario
click image for larger view
 

Not only does this usage model require minimal work on the part of the home PC user, but it also simplifies the process for IT technicians of fixing PC problems remotely. The IT technician only needs to complete the following steps to control and fix a PC after receiving a phone call from the home PC user:

1. Guide the home PC user to enter the configuration UI.
2. Tell the IP address and TCP Port of Proxy to the home PC user and guide him/her to start the configuration UI.
3. Get the UUID and admin password from the home PC user and enter them on the management console.
4. Check if the service receives the Hello packet from this PC on the management console. If so, access the home PC with the admin user account.
5. Configure the SOL/IDER setting of the home PC and boot the home PC through the local OS image.
6. Use the scan and antivirus software on the local OS image to repair the host OS on the disk of the home PC.
7. Close the connection and inform the home PC user that the problem is fixed (or not) and that the connection is closed.