3.2.4 Message Processing Events and Sequencing Rules

The following list shows the sequence of steps involved in a Remote Assistance Connection String request:

  1. The client initiates the conversation with the server by performing DCOM activation, as specified in [MS-DCOM] section 3.2.4.1.1, of the PCHService CLSID specified in section 1.9. As a result of the activation, the client gets the PCHService's interface from the server.

  2. The client then obtains an additional IPCHService interface from the PCHService interface as specified in [MS-DCOM] section 3.2.4.4.3.

  3. The client then invokes the RemoteUserSessionInfo method of the IPCHService interface to retrieve an ISAFSession interface pointers' collection of type IPCHCollection.

  4. Enumerate the ISAFSession interfaces of the server by repeatedly calling the Item method of the IPCHCollection interface. The collected list of session information is presented to the Remote Assistance user, by means of an implementation-specific user interface, to decide which session to connect to.

  5. From the collected ISAFSession interface values, a session is chosen by the Remote Assistance user. The SessionID and corresponding DomainName and UserName are passed in a call to the RemoteConnectionParms method of the IPCHService interface. This call returns the Remote Assistance Connection String for the specified session. Sessions with no DomainName or UserName MUST be ignored.

  6. This Remote Assistance Connection String is valid to begin the Remote Assistance connection.