Once the Easy Connect password has been exchanged between two machines, it should not be necessary to use the password to connect or offer assistance for subsequent sessions, unless the DNS resolution, IP address or other system authentication elements subsequently change. The command line interface will default to use of Easy Connect if it has been previously established.
Note that the switch is not case sensitive, though I have typed it this way to help you avoid the most common syntax error.
The most common problem is larger networks and across firewalls, is the establishment of appropriate Ports. NAT is supported, if the appropriate protocols are supported on router and firewall interfaces. Checking remote system visibility via ping, tracert or pathping are obvious tests while in the cmd window. You can also use Remote Desktop Connections as a test of system availability, or to provide uni-directional support from the command interface.
Also provides a list of additional Remote Desktop Connection configuration options. With just a little preconfiguration and some simple guidelines, Microsoft Windows 7 provides far greater remote system and user assistance. If session logging is not configured using Group Policy, both the User and Helper are free to disable session logging on their own computers.
Session logs are XML-formatted documents so that they can be easily integrated into other data sets—for example, by importing them into a database managed by Microsoft SQL Server A unique session log file is created for each Remote Assistance session on the computer. For example, a session log created at P. The main Remote Assistance scenario within a corporate networking environment is supporting desktop computers that are on the corporate network and joined to a domain. Additionally, the Remote Assistance exception in the Windows Firewall must be enabled.
For more information, see the section titled "Remote Assistance and Windows Firewall" earlier in this chapter. Because most corporate networks have a perimeter firewall blocking access from outside the internal network, supporting remote users who are connecting from outside the corporate network can be more difficult. However, most enterprises now use virtual private network VPN technologies to allow remote users to connect to their corporate networks over the Internet, and this kind of scenario generally poses no problem to Remote Assistance functionality.
The standard approach to using Remote Assistance in an enterprise environment is for Help Desk personnel to offer Remote Assistance to users who telephone to request assistance. A typical scenario might be as follows:. User Jane Dow the User is having problems configuring an application on her computer. She phones Help Desk, explains her problem briefly, and asks for help.
She responds with the information, which she can get from computer properties or by running ipconfig. Jane then explains the problem she is having, either by using the Chat feature of Remote Assistance, or more likely over the telephone. Jacky asks Jane to perform a series of steps to correct the problem and watches her screen in his own Remote Assistance window as she does this. If the instructions Jacky provides are too complex or if time is limited, Jacky can ask Jane if he can share control of her computer.
Jacky then proceeds to perform the steps needed to resolve the problem, either correcting the issue or demonstrating to Jane how to fix the problem if it occurs again in the future. If at any time Jane wants to force Jacky to relinquish control of her computer, she can click the Stop Sharing button or the Disconnect button, or she can press the Panic key Esc. Examples of possible usage scenarios include:. A user who is having a problem configuring an application on her computer can phone the Help Desk for assistance.
This scenario is the standard one for enterprise Help Desk environments and is described in more detail in the section titled "Using Remote Assistance in the Corporate Help Desk Environment" earlier in this chapter.
A user who is having trouble installing a printer sends a Remote Assistance invitation to Help Desk using Windows Mail. A user is on the road and is connected to the internal corporate network using a VPN connection over the Internet. The user is having problems configuring Windows Mail on her computer, so she opens Windows Live Messenger and notices that someone she knows in Corporate Support is currently online.
She sends a Remote Assistance invitation to the support person using Windows Live Messenger, and that person responds to the invitation, asks for control, and shows the user how to configure Windows Mail. A user who is having problems installing an application uses Easy Connect to request help from a support technician. Because this is the first time he has requested help from this particular support technician, the user must communicate the password for the session to the support technician using an OOB method such as making a telephone call.
The next time the user needs help, however, he will not need to provide a password because of the trust relationship that was established during the first Remote Assistance session between them.
The preceding list is not intended to be complete—other corporate support scenarios using Remote Assistance are possible. Generally speaking, however, corporate environments will use Offer RA to provide assistance to users who phone Help Desk when they have problems.
Some enterprises may also allow users to submit Remote Assistance invitations either via e-mail or by saving invitation files to network shares that are monitored by support personnel. Others might use IM applications that support Remote Assistance within the corpnet. Helpers can have multiple Remote Assistance sessions open simultaneously—one session for each User they are supporting.
The invitation that was created could be sent to multiple recipients—any of whom may connect. All subsequent connect attempts will be blocked until the first Helper disconnects, after which another Helper may connect.
If the User disconnects the session, the Remote Assistance application terminates and no further connections will be allowed. In addition, a Windows 7 user cannot transfer a file with a Windows Vista user during a Remote Assistance session. This means that enterprises who want to implement Offer RA as a support solution for their Help Desk departments should ensure that computers used by support personnel who will help users running Windows 7 are themselves running Windows 7 and not Windows XP.
Voice support for Remote Assistance in Windows XP is not supported by Remote Assistance in Windows 7, and any attempt by a User on a Windows XP computer to use this feature during a Remote Assistance session with a Helper on a Windows 7 computer will cause a notification message regarding this limitation to appear.
A Windows 7 user cannot transfer a file with a Windows Vista user during a Remote Assistance session. Windows 7 Resource Kit. Windows Internals, Part 2, 6th Edition. Windows 7 Inside Out, Deluxe Edition. Sign in. Your cart. Windows Remote Assistance is a useful feature that allows you to make someone you trust to take over your PC to fix some issues remotely. If you want to use it, you need to enable it in advance. How to enable Remote Assistance on Windows?
Here are three methods. It is very easy to enable Windows Remote Assistance using command line. The User must enter the e-mail address of the Helper in the To field to send the message to the Helper.
The path can be either a local folder or network share, and the User must have appropriate permissions on the destination folder to create the file. The path must include a file name for the ticket.
MsRcIncident file extension will be automatically added to the file name. The password must be six characters or more.
0コメント