> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/library-packs/it-operations/goto-logmein-rescue/usage-guide-goto-logmein-rescue.md).

# Usage guide: GoTo LogMeIn Rescue

The GoTo LogMeIn Rescue Secure Remote Support library pack enables IT teams to:

* Launch secure LogMeIn Rescue sessions directly from Nexthink.
* Move quickly from device diagnostics to hands-on remote troubleshooting.
* Use PIN-based or channel-based Rescue connection methods.
* Use the Rescue Calling Card when required by your organization.
* Maintain device context while following existing service desk processes.

The pack provides signed **Remote Actions**, so you do not need to create scripts manually.

## Library pack uses

{% hint style="info" %}
Jump to Use cases on this page to see relevant scenarios.
{% endhint %}

Use the library pack content for the following purposes.

### Escalating from diagnostics to remote support

Use the provided **Remote Actions** when an issue identified in Nexthink requires hands-on troubleshooting.

Technicians can start a LogMeIn Rescue session without manually creating a session link. This reduces tool switching when moving from diagnostics to remediation.

### Managing end-user consent

Configure consent according to your organization's support policies.

You can use the Terms & Conditions configured in LogMeIn Rescue.

Depending on the Rescue account configuration, the Rescue applet can request additional consent before sensitive operations.

### Preparing remote support

The library pack includes preconfigured and signed **Remote Actions**. You do not need to create or sign the scripts manually.

Before technicians use the pack, administrators must configure the required **Remote Action** parameters in Nexthink. They must also complete the corresponding setup in the Rescue Admin Center.

## Use cases

In addition to the relevant use case covered below, you may uncover other troubleshooting scenarios specific to your environment.

### Starting a PIN-based remote support session

Use a PIN-based connection when your Rescue configuration requires users to join with a session PIN.

From Nexthink:

1. Identify the device that requires hands-on troubleshooting.
2. Run the relevant LogMeIn Rescue **Remote Action** for a PIN-based session.
3. Ask the user to follow the LogMeIn Rescue connection and consent prompts.
4. Continue troubleshooting in LogMeIn Rescue after the connection is established.

### Starting a channel-based remote support session

Use a channel-based connection when your organization routes Rescue sessions through configured channels.

From Nexthink:

1. Identify the device requiring remote assistance.
2. Run the relevant LogMeIn Rescue **Remote Action** for a channel-based connection.
3. Confirm the required consent in accordance with your organization's configuration.
4. Continue the support session in LogMeIn Rescue.

***

RELATED TOPICS

* [Manage Remote Actions](https://nexthink.gitbook.io/opd/user-guide/remote-actions/managing-remote-actions)
* [Configuration guide: GoTo LogMeIn Rescue](/platform/library-packs/it-operations/goto-logmein-rescue/configuration-guide-goto-logmein-rescue.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nexthink.com/platform/library-packs/it-operations/goto-logmein-rescue/usage-guide-goto-logmein-rescue.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.