msra.exe /getcontacthelp address in C#

Printing Quick Response Code in C# msra.exe /getcontacthelp address

Here, address is the value of the ADDRESS attribute in Karen s Remote Assistance history contact information on Tony s computer, which is stored as an XML element in the RAContacthistory .xml file located in the \Users\TALLEN\Appdata\Local folder on Tony s computer . The contents of this file might look like the following:

< xml version="1.0" > <RAINVITATIONCOLL> <RAINVITATIONITEM NAME="KBERG" COMPUTERNAME="KBERG-PC" AVATAR="Qk1QgA [lots of characters] " PUBLICKEY="BgIAAAC " ADDRESS="5823b8d7b47af2c1cd94f32535a79d8f0569e7d0.RAContact" TYPE="1" TIME="20090320170235.779000"/> </RAINVITATIONCOLL>

Using this example, the shortcut Karen creates on Tony s computer should execute the following command:

Karen can then create a similar shortcut on her own computer using Tony s Remote Assistance history contact information, which is stored as an XML element in the RAContacthistory .xml file located in the \Users\KBERG\Appdata\Local folder on Karen s computer . After this is done, Tony can request assistance by simply double-clicking the shortcut on his desktop, and once he has informed Karen of this, Karen then double-clicks the corresponding shortcut on her own computer, and when Tony agrees to allow the connection, the session is started . diReCt FRoM tHe SoURCe

he new Easy Connect feature simplifies Remote assistance by enabling a direct p2p transfer of the Remote assistance invitation using pNRp. When the User

starts Remote assistance and selects Invite Someone You Trust To Help You and then Use Easy Connect, a Remote assistance invitation is created, encrypted, and published as a payload on a node in the pNRp cloud. This invitation will be retrieved by the Helper from the pNRp cloud and the information is used to establish a Remote assistance connection to the User. When the invitation is created, a 12-character alphanumeric password is generated automatically and is displayed in the Tell Your Helper The Easy Connect password dialog box. The first time the User uses any particular Helper, the password must be relayed OOB to the Helper before the Helper can connect to the User s computer. The password is case insensitive and avoids characters and numbers that could look similar (such as I and 1, 5 and S, and 0 and O). after the pNRp node has been created in the pNRp cloud, the User s computer waits for an incoming connection from the Helper s computer. This node will exist for 30 minutes before expiring and invalidating the invitation. The Helper starts Remote assistance, selects Help Someone Who Has Invited You and then Use Easy Connect, and enters the password relayed OOB from the User. The Helper s computer uses the password to locate the pNRp node containing the User s invitation, grabs the payload (that is, the invitation), and decrypts it. Remote assistance uses the invitation to connect to the User s computer. Of course, after the Remote assistance connection has been established, the User must still provide explicit consent before his desktop is remoted. When a Remote assistance session has been established using Easy Connect, the User and the Helper become trusted contacts of each other. The Remote assistance history store on each computer is used to maintain a list of records of trusted contacts that were established using Easy Connect. These records contain the following information for each trusted contact:

User name Computer name User graphic (associated with the user logon account) Date and time of connection public key of the connected user

Each history record identifies a specific user on a specific computer. a record is created only if each side of the connection has positive confirmation that the other side has received the user s entire contact info. Note that the Remote assistance contact history does not include the user s role (User or Expert). This means that when trust is established between two user/computer pairs, either one of them may take the role of User and ask the other for assistance. The next time the User tries to solicit assistance from the same Helper using Easy Connect, the User simply starts Remote assistance and selects the Helper from the User s Remote assistance contact list no password is needed because the Helper is already trusted by the user. The Remote assistance ticket is exchanged using Secure pNRp. all the User needs to do is notify the Helper that assistance is requested, and this can be done by telephone, IM, or any other OOB method. after the User has notified the Helper that assistance is requested, the Helper starts Remote assistance and selects the contact of the user. The Helper s computer uses Secure pNRp to retrieve the Remote assistance invitation and the Remote assistance session with the User is established without any password needing to be entered by the Helper.

Scenario 2: Soliciting Remote assistance by Creating Remote assistance Tickets and Saving Them on Monitored Network Shares

Another way that you can use Remote Assistance in an enterprise environment is by having users create invitation files and save them on a network share that is monitored by Help Desk personnel . This way, when Help Desk determines that a new ticket has been uploaded to the share, a support person can call the user on the telephone to obtain the password for the ticket and then use the ticket to establish a Remote Assistance session with the user who needs help . To make the procedure easier, administrators can first deploy a script on users desktops that uses command-line Remote Assistance (via Msra .exe) to create the invitation file and save it on the network share . For example, let s say that users invitation files should be uploaded to \\FILESRV3 .contoso .com\Support\IncomingTickets, a folder in the Support share on the file server named FILESRV3 . The following script, named SubmitTicket .vbs, could be deployed on each user s desktop to accomplish this task .