1. In Microsoft Dynamics, navigate to Settings > Solutions.
   
2. Click Import.
   

   Result: The Select Solution Package window is displayed.

3. Browse to and select the Rescue solution file associated with this deployment, then click Next.
   Tip: The solution file is usually saved on a network drive. You will typically search for a zip file with a name like Rescue-Managed-[version.number].

   For detailed information, contact your network administrator.

4. Proceed through the solution import wizard.

   Result:

   Attention: Make sure you select the Enable any SDK message processing steps included in the solution box.
   
   

1. Log in to the Rescue Administration Center.
   Note: Don't have a Rescue Account? Request a Trial.
2. In the Rescue Administration Center, select the Technician Group you want to work with on the Organization Tree.
3. On the Settings tab, navigate to Exporting session data, and set the Post session details ... fields to https://dynamics.logmeinrescue.com/api/integration .

   Result:

1. In Microsoft Dynamics, navigate to Settings > Solutions > All Solutions.
2. Double-click the Rescue solution item.

   Result: The Solution: GoTo Rescue configuration window is displayed.

3. Choose the Production or the Beta instance.

   Result: This pre-populates the endpoint.

   Note: Endpoint settings can be modified if necessary.

4. Enter your Rescue Company ID and Single Sign-On (SSO) password (if SSO is to be used).
   Note: You can find your Rescue Company ID and SSO password under Global Settings > Single Sign-On.
   
5. Verify your Microsoft Dynamics ORG URL is correct.
6. Enter your Office 365 tenant ID.

   Result:

   Tip: To find your Office 365 tenant ID in Microsoft Azure, navigate to Azure Active Directory > App registrations > Endpoints, and copy your globally unique identifier (GUID) from the MICROSOFT AZURE AD GRAPH API ENDPOINT URL field.
   

7. Optionally, configure the following settings the way you want your integration to work.

   Option	Description
   Require Active Tech Console:	When selected, the user requesting the PIN is required to have an active Rescue session in the Technician Console.
   Close ticket at session end:	When selected, the Rescue session record is automatically deactivated at the end of the session. This makes it possible to trigger other custom processes at this point.
   Reassign case on Session Start:	If the session returned from Rescue is assigned to a different CRM user than the one assigned to the case in CRM, the case is reassigned based on the session record.
   Do not pass cfield1:	When selected, Microsoft Dynamics does not pass the value of custom field 1 to the Rescue Technician Console. By default, this custom field is used to pass the email address related to the Microsoft Dynamics ticket. Tip: Make sure to select this option if you use custom field 1 to pass data other than the email address to Rescue, so your data is not overwritten.

8. Click Save.

If GoTo session data is not being written to the Dynamics case, a Dynamics Administrator should check the status of the session key for the GoTo Rescue Dynamics application by following the below procedure.

1. In MS Dynamics, navigate to Settings > Customizations > Customize the System.
2. On the left panel, under Components expand Entities > GoTo Session.
3. Select Keys.

   Result: The Session Key status is displayed.
   

4. If the Session Key status is in Pending, manually activate the key:
   1. Under Settings > System > System Jobs locate the failed job Create index for Session Key for entity GoTo Session.
   2. Select the failed job, and delete it using the X icon above the list of System Jobs.
   3. Navigate back to Settings > Customizations > Customize the System.
   4. On the left panel, under Components expand Entities > GoTo Session.
   5. Select Keys.
   6. Select the Session Key.
   7. Click More actions > Reactivate Key.
   8. Refresh the list until the status shows Active.