Copyright © 2023 Pneuma Solutions


Remote Incident Manager (RIM) is a powerful, cross-platform fully accessible remote desktop application used to provide technical support, training, and system administration to clients both visually impaired and sighted alike. In addition to providing a streamlined remote desktop experience, RIM has a few unique qualities previously unseen in other remote desktop applications

Why RIM?

If you are coming from previous remote desktop applications or screen reader-based assistance tools, you will find that RIM significantly streamlines your workflow.

Inclusive Design

Remote Incident Manager is truly a first of its kind. It is the first fully accessible remote support solution that can be used by both blind and sighted support pros and end users. Thus, RIM can fully replace an existing solution, as it provides everything you could ask for in a secure remote support solution, plus complete accessibility.

Easy to Install and Deploy

In a one-to-one situation, the installation could not be simpler. A one-click instant install ensures that the end user's process for setting up their machine to receive assistance will be quick and painless. What's more, the installation process launches RIM after it finishes, so they will be instantly ready to connect. Technicians can easily manage their machines via an easy to use web-based interface. Enterprise users can use this dashboard to deploy RIM to machines in their workplace. Ready-made installers can be issued to end users in seconds. The installer itself can be further customized via command line arguments which can in turn be utilized in an automated deployment.

Shared Session

Unlike Windows Remote Desktop or other similar applications, a remote session sandbox is not created; what the end user's machine is doing is what you'll be seeing. This means that you can easily troubleshoot a problem they are having while keeping their existing configuration intact. This further allows you to work collaboratively on a project, send files to and from via the clipboard, etc.

Fast and stable connections

Because RIM uses the latest advancements in direct computer-to-computer connections, the responsiveness is head and shoulders above other solutions. While RIM's central service initiates the connection, it gets out of your way once the connection is established. All this without the need to make cumbersome and invasive changes to network configurations.

High Quality Audio

RIM uses the latest advancements in real-time audio encoding technology to provide extremely responsive, high-fidelity stereo audio. You will hear any and all audio that is playing on the end user's machine during the session.

High-Quality Visual Output

Again, Remote Incident Manager is an all-inclusive solution designed to replace previous infrastructures, rather than be used alongside them. As such, RIM's screen output is equally as responsive and stable. Using the mouse is fully supported as well.

Voice Communication

Gone are the days of having to place a separate phone call or web conference alongside the remote session. RIM provides crystal clear, low-latency voice communication right inside your session.

Accessible in All Use Cases

RIM is the first remote access solution that provides unparalleled accessibility, irrespective of the screen reader (or lack thereof) that either party is using.

differences in Screen Readers are now Irrelevant

Before RIM, it used to be difficult to assist someone running a different screen reader than your own. With RIM, this is now a thing of the past. RIM doesn't care what either party is running. You could be running JAWS while the person you're assisting could be running NVDA or even VoiceOver; with RIM, none of that matters. Not only will you be able to hear the end user's speech irrespective of their screen reader, RIM's keyboard handling will be stable and reliable irrespective of screen reader configuration. This is a significant advantage of a screen reader-independent solution.

No Screen Reader? No Problem!

A blind IT professional can now easily help a sighted end user, even if they do not have a screen reader installed on their computer. In the absence of a screen reader on the remote computer, RIM will see to it that you will still be able to get speech provided you are using either the free NVDA Screen Reader or VoiceOver on Mac OS. Remote incident Manager will initiate its accessibility module which allows you to control the client's machine with speech as if they had a screen reader. Not only does the end user not have to worry about installing a screen reader, they don't even hear the speech that you're now hearing while you control their computer.

Documentation Conventions and Terminology

  • Key combinations are denoted by the plus symbol, i.e. Option+Shift+Backspace.
  • RIM connections occur between a target and a controller.
    • A target computer is the computer that will be receiving remote support.
    • A controller connects to a target computer for remote support.

System Requirements

In order to run Remote Incident Manager, your computer should meet or exceed the following minimum requirements:


  • Windows 7 SP1 or later
  • Windows Server 2012 or later
  • at least 4GB of ram
  • Admin privileges for initial installation (not required for automatic updates)


How you acquire and install Remote Incident Manager depends on your use case and configuration, but in any case the process is quite straight forward.

Typical Installation for Individuals

There is only one installation package to use, whether you are offering or receiving assistance.

  1. Download Remote Incident Manager
  2. Run the downloaded file.
  3. If you have user account control enabled, press Alt+Y to approve the installation.
  4. Once the file is launched, the installation will automatically commence. There are no next buttons to worry about. Just sit back, relax, and let it do its thing. Within seconds, the program will be installed and will launch automatically.

That's all there is to it! A desktop shortcut will be automatically created to aid in subsequent launches of RIM. Additionally, RIM sets up a multipurpose global hotkey (Windows+Shift+Backspace) which, among other things, automatically launches the program from wherever you are.

Unattended Access Installer

If the person providing assistance has provided you a custom installer, you will be advised of this when the installer launches. This is because this installer will automatically configure RIM for what is known as unattended access. This is what will allow the person helping you to initiate a session with your computer without you having to enter a keyword. We will cover unattended access indepth later on in this manual.

Silent Installation

You'll want to do this when deploying RIM to multiple machines. Simply use the /S command line parameter in your deployment script. Note that it is case-sensitive, so a capital S is required.

Additional Considerations for Windows Servers

To install RIM on your Windows Server, connect to the server via RDP. In order to get the most stable connection experience, we recommend using the Remote Desktop app from the Microsoft Store.

Obtaining Sound and running Narrator

In order to obtain sound, do the following once connected:

  1. Press windows key+r.
  2. Type cmd and hit enter. Wait about ten seconds.
  3. Type:
    net start audiosrv
    and hit enter.
  4. Now, press CTRL+Windows+Enter to enable Narrator. If everything worked properly, you should get speech.

You can now follow the install procedure as described above.
Please note that if you need sound for subsequent connections via RIM, you will need to install a virtual sound output device on your server. The free version of Virtual Audio Cable should suffice.

Getting Connected

Remote Incident Manager's connection process is designed with speed and simplicity in mind, both for the person receiving assistance as well as for the person providing it.

Connecting to a Controller

When you first launch Remote Incident Manager, you will be in target mode by default. This means that you are going to be connecting to a person who has set up a remote support session for you.
You will land in an edit box labeled "keyword." Enter the keyword issued to you by the person assisting you, and then simply hit enter. That's it, you're connected!

Accepting a Request to Connect

If a technician provides support to you on the regular, your machine may be set up to receive a request to connect without either of you having to enter a keyword. RIM will announce that your technician is attempting to connect. In order to accept the connection, press Windows+Shift+Y, and the session will begin momentarily.

Connecting to a Target

The process for setting up the session is fairly similar. Rather than entering the keyword, you will want to navigate to the "Provide help instead" button. When doing this for the first time, you will be asked to set up an account.

  1. Enter your email address.
  2. Check your email for a verification code, and then enter it into RIM.
  3. You will then be asked to enter your name, location and phone number.
  4. Lastly, you will receive another verification code on your phone. Enter this code into RIM.
    1. If you do not have a mobile phone capable of receiving text messages, please fill out this form. We will assist you in getting your account verified.
    2. A note for international numbers: If your verification code doesn't come through, make sure the country code before your number is denoted by the plus sign, rather than 00.

Now that you're logged in, enter the keyword that the target will use to connect to you. When you navigate past the edit box, you will come across a checkbox that determines whether or not to start a voice conversation during the session (this can be toggled on or off during the session as well). After that, you will find the "Start" button. When you click this, you will be in the waiting room until your target connects. At this point, you will want to send the keyword you just entered to the person you'll be connecting to, as this is what they will use to connect. Once they have connected, you will receive an alert informing you that the remote session is about to begin. Take note of the mentioned Windows+Shift+Backspace shortcut as that will bring up the RIM menu on your machine. If you rely on the keyboard exclusively, this is the only way to direct keyboard input back to your own system. After you dismiss this dialogue, the remote session will be initiated.

Working within a Session

Things to Know before you Begin

A few things will happen immediately after the connection is established.

  • The remote control window for the session will appear.
  • You will be informed about the status of the running screen reader, or lack thereof, on the client's machine.
  • If the client is running a screen reader, a toast notification informing the user that the remote session has begun will provide instant confirmation that the user's system audio is working.
  • Last but not least, all keyboard and mouse input will immediately be directed to the target computer. To direct control back to your machine, do either of the following:
    • press Windows+Shift+Backspace.
    • right click the RIM window's title bar.
    • left click the RIM icon.

Remote Control Zone

At this point, you're all set to perform whatever tasks need doing on the client side. Should you need to switch back to controlling your own machine, bring up the RIM menu, then select the "Minimize session" option. You will be taken back to your machine until you switch back into the session window or press Windows+Shift+Backspace again. When you go back into the session window, keyboard control will once again be directed to the client computer.
Once you're done, either the controller or the target can go into the RIM menu and choose the "Disconnect Session" option. When the session ends, the target machine will get a toast notification informing them of this.

The RIM Menu

As mentioned earlier, accessing the RIM menu directs you back to your machine. There are a number of options in this menu. They include:

  • Update RIM on Target: Forces an update of RIM on the target computer
    • This option shows if the target's machine is running an older version of RIM
  • Minimize Session: brings control back to your machine as described above
    • You can also use the shortcut windows+shift+m to minimize the session.
  • Transfer File to Target: Appears if a file is on the clipboard.
    • Although this alternate method of completing a file transfer is always available, it is only necessary for transferring files to Mac targets.
  • Flip Session: Allows your client to remote control your machine and hear its audio. As the original controller, you can flip the session back by selecting this option a second time.
    • You can also use the keyboard shortcut Windows+Shift+F to flip the session back and forth.
  • Start/stop Voice Conversation: Allows you to toggle the voice chat on or off for your session.
    • Note that this option is unavailable in unattended sessions as they do not support voice chat. However, prompted sessions still support this.
  • Start Remote Accessibility: This option appears when no screen reader is running on the remote computer. This will enable speech on your end, but the client will not need to worry about hearing speech.
  • Reboot and Reconnect: Allows you to reboot the computer and automatically reconnect the session.
  • Send Control+Alt+Delete: Sends this keystroke to the remote machine.
  • Request Unattended or Prompted Access: Allows you to send a request for unattended access to the client computer. This is useful if you are a sysadmin and need to perform routine maintenance, or even for something as simple as controlling your home machine while on the go.
  • Lock the Target Machine: Performs the equivalent of Windows+L.
  • View Connection Details: Provides a detailed lowdown on your connection, as well as the target machine. Information includes:
    • Connection statistics
    • Information about the computer, including Windows version, available ram, etc.
    • Running processes
    • Installed packages
  • Disconnect Session: Terminates the session.
    • Remember that this option is available to both sides of the session.
    • This is also possible via the keyboard command Windows+Shift+D.

File Transfers

RIM provides a simple avenue for transferring files, irrespective of platform used.

  1. Bring up the RIM menu, and click on "Minimize Session." Control will be directed back to your computer.
  2. Select the file(s) and/or folder(s) you want to transfer using your file manager.
  3. Copy the selected contents to the clipboard in the usual way. You will receive a notification that a file is ready to be transferred. You have two options.
    1. If the target is a Mac
      1. Activate the RIM session menu, and click on the "Transfer File to Target" option.
      2. Upon completion of the transfer, the target Mac will generate a temporary directory containing the transferred contents. These should then be copied and pasted to their intended directories.
    2. If the target is a Windows machine:
      1. Switch back to the remote session, and locate the folder on the target machine where you wish to paste the content.
      2. Last but not least, paste as you normally would.

Note that the transfer time will depend entirely on the size of the content being sent as well as your network speed.

Remote Accessibility Module

Whether you're assisting a user who doesn't use a screen reader, or you're diagnosing an issue with a malfunctioning screen reader, RIM is fully prepared to come to your aid. The remote accessibility module consists of two components:

  • An addon for the NVDA screen reader that enables the screen reader to receive output from the remote computer
  • A self-contained accessibility module initiated on the target computer at the request of the controller. The advantage to this approach is that the end user does not hear speech on their computer while you're controlling it. Instead, the Remote Accessibility Module pipes the speech output through to the running copy of NVDA on the controller side. This way, you can accessibly assist an end user without them having to install or even download a screen reader.

Setup Procedure

For first-time initialization of the accessibility module, here is what you will need to do:

  1. Connect to a computer that does not have a screen reader running.
  2. If NVDA is currently running, you will be asked to install an addon that will allow your copy of NVDA to communicate with the remote computer during the session. Accept the installation prompts, and wait for NVDA to restart.
  3. By now, the remote accessibility module will be fully initialized, and you will hear speech output as you control the remote computer.

From this point forward, if you are running a screen reader on the controling computer, the remote accessibility module will automatically start during remote sessions in which the remote computer does not have a screen reader running. Should you be running a screen reader other than NVDA, RIM will disengage that screen reader and then switch you over to NVDA. If you need to stop the remote accessibility module on the remote machine in order to start another screen reader, simply press insert+q as you normally would to quit NVDA.

Rebooting and Reconnecting

Whether you're installing system updates or working your way out of a system hang, RIM has got you covered during the reboot process. Selecting the "Reboot and Reconnect" option off the RIM menu will allow you to either perform a graceful reboot or an emergency reboot, depending on what state the computer is in. While the computer is rebooting, RIM will inform you that reconnection attempts are being made.
Note that if the computer is rebooted by a software installation or manually rebooted in the usual way, you will be asked if you wish to reconnect the session. Of further note is that in either case, Mac targets will only reconnect once the user logs in. This is due to the fact that RIM cannot start automatically on the login screen due to platform limitations, most notably FileVault disk encryption.

Unattended or Prompted Access

RIM allows you, as the controller, to configure machines for unattended or prompted access. This allows you to provide remote assistance without the user having to launch RIM, enter a keyword, or even be near the computer. This is useful if you are a sysadmin performing routine maintenance on computers in your workgroup, or for clients you provide support to on the regular. You may also want to allow unattended for your home computer should you need to access it from someplace else.
There are a few ways to configure machines for unattended access.

During an Interactive Session

  1. Bring up the RIM menu.
  2. Select "Request Unattended or Prompted Access."
  3. You will be asked what kind of connection you want to configure. Your options are:
    1. Unattended: Allows sessions to be initiated without any intervention whatsoever from the end user.
    2. Prompted: This configuration presents the user with a prompt informing them that you are conecting to their machine. They will need to press Option+Shift+Y on Mac OS, or Windows+Shift+Y on Windows, should they wish to accept the connection.
  4. You will be asked to give this machine a name. Enter a personal name for the machine, or if applicable, the machine ID as it appears in your workgroup.
  5. Press enter.
  6. On the client machine, a dialogue pops up asking the user if they're fine with their computer being set up for the access you requested. If they answer yes, then you will get a prompt informing you that the access has been approved.

Note for personal account holders: If you exceed the number of machine slots available to you in your current plan, RIM will notify you of this and prevent the machine registration from continuing. If you wish to register the machine, either unregister one of your other machines or upgrade your plan.

Registering a Machine to your RIM account

Should you wish to register one of your own machines for unattended access, you can do so without having to start an interactive session with the machine.

  1. Start RIM in Receive Help Mode.
  2. Click on the "Add this machine to your RIM account" button.
  3. Enter your email, then click next.
  4. Wait for the two-step login code to arrive, enter it, then you should be logged in.
  5. You will be asked what type of access you would like configured for this machine. Your options are:
    1. Unattended: Allows sessions to be initiated without any intervention whatsoever from the end user.
    2. Prompted: This configuration presents the user with a prompt informing them that you are conecting to their machine.
  6. Give the machine a name, then activate the "Add Machine" button.
  7. The machine will be registered to your account, which will allow any controller machines logged into your RIM account to connect to this machine.

Note for personal account holders: If you exceed the number of machine slots available to you in your current plan, RIM will notify you of this and prevent the machine registration from continuing. If you wish to register the machine, either unregister one of your other machines or [upgrade your plan.]

Getting Connected

Now that we've registered the machine for unattended access, here is how we will start a session.

  1. Start RIM in controller mode.
  2. Rather than entering a keyword, locate and activate the"Choose a machine" button.
  3. When you click this, a list of machines will appear. Choose the one you want, then hit enter. You may also use the search bar to narrow the list down to a specific machine.

If the target machine is configured for prompted access, the end user will get a prompt. Once they answer yes, you'll be connected. If the session is unattended, you will immediately be connected and dropped into the remote control zone.
Please note: Voice conversations are not supported during fully unattended sessions.

Creating a Shortcut for an Unattended Session

For extra convenience, you can create desktop shortcuts that allow you to automatically launch unattended sessions. In order to do this:

  1. Access the list of unattended computers, and select the one you want to create a shortcut for.
  2. Click on the "Create Shortcut" button.
  3. A shortcut will be automatically added to your desktop.

Now, when you activate this shortcut, you will either automatically land in the remote session, or send a prompt to the user's machine that they can accept.

More Ways to use Unattended Session Shortcuts

Unattended session shortcuts, like any other shortcuts, can have global hotkeys associated with them. This can be extremely useful if you are a maintenance tech managing multiple computers in a workgroup. For example, if your workgroup consists of 6 computers that you perform routine maintenance on, you could configure Alt+Control+1 through 6 as hotkeys for each respective machine. This ought to significantly speed up your workflow.
In addition, you can call up an unattended session via the run box if you copy the shortcut into your user directory. Once you've copied the shortcut, you may start an unattended session by typing your-session-name.url in the run box.

Revoking Unattended Access

If you no longer want your machine to be controlled unattended, you can revoke the controller's access. You do not need to be in a session in order to do this.

  1. Access the Remote Incident Manager icon in your system tray.
    1. If using the keyboard, press windows+b, then space, then left or right arrow until you find the icon.
  2. Right click this icon, or press the applications or shift+f10 key.
  3. Select the "Revoke Unattended Access" option.
  4. You will arrive at a list of computers, select the one you want to revoke.
  5. You will be asked if you wish to revoke the machine; answer yes.

That's it! The controller will receive a message stating that this machine is no longer available for unattended access. Should they need unattended access again, they can reinitiate the procedure to request permission for unattended access as described above.

Key Command Reference

Minimize SessionWindows+Shift+M
Flip SessionWindows+Shift+F
Disconnect Session (Controller or Target)Windows+Shift+D

The RIM Management Dashboard

RIM features a web-based dashboard to facilitate various machine and account management tasks. You can manage your existing unattended computers, create preconfigured installers for target computers, and much more.
It should be noted that the feature set of the dashboard is largely dependent on which subscription tier your account is under. For example, enterprise users can assign machines to target groups, as well as create silent and/or MSI-based installers. On the other hand, creating standard (nonsilent) custom installers for unattended machines is possible with a pro subscription or above, and personal unattended accounts are limited to the amount of machine slots under their plan.

Locating the Dashboard

If you're a controller, the easiest way to get to the dashboard is through the main RIM interface. Clicking the RIM Dashboard button will automatically open the dashboard in your default browser, with the login already taken care of.
If you are a network administrator who does not have RIM installed, you can simply log into your account on the RIM website and your dashboard will appear.

Managing Targets

When you click the "Configure Targets" link, you will arrive at a page that allows you to manage all the machines you have configured for unattended access. You can click on any one of these machines in order to manage it. Once inside, you will be able to:

  • Rename the target
  • Move the target to a different group (more on target groups later)
  • Delete the target

Target Groups (for Pro Accounts and Above)

Say for instance you're workgroup is spread out among several different locations. Or maybe you want to designate groups of machines to your routine maintenance techs. Target groups allow you to do just that. In order to do this, simply click the "Create Target Group" button, name your group, and submit.
You may have as many target groups as is needed for your use case.

Access Control (for Enterprise Organizations)

If your organizations assign a support technician to a specific set of machines, you probably want to ensure they only have access to that specific set. This is where the access control setting for target groups comes in.
When you click on a target group, you are given options to manage the machines in the group, as well as the group itself. The access control section is where you may grant access to this group on a per-account basis. Simply enter the email address of the account you wish to add, then click the "Give Access" button. Once this is done, you will be presented with a table of accounts that are given access to this group. Below each account is a "Revoke Access" button. This button does not require further confirmation.
It should be noted that all organization administrators are automatically granted access to manage any and all groups that are created under the organization.

Setting up a Preconfigured RIM Installer (Pro or above)

One of the easiest ways to set up a machine for unattended or prompted connections is by creating a custom installer. This is incredibly useful if you are configuring mass deployments, or even as a simpler way to get RIM up and running on an end user's computer you plan on providing support for on the regular. IN order to do this:

  1. In the target management screen, click the "Build Target Installer" button.
  2. You will first be asked if you want this machine to be configured for fully unattended access, or for prompted access in which the user has to accept a prompt to initiate the connection.
  3. You will then be asked for a target group assignment. Note that the target group selection will automatically go to your chosen target group if you initiate the installer configuration from your group's page.
  4. You will be asked how long you want this installer to be valid for. It can be valid for anywhere between 7 to 30 days. Note that this timeframe only affects the functionality of the installation package. In other words, the machine's RIM configuration will not be disabled when the installation expires.
  5. You are then given the option to assign a bass name. Any machine provisioned via this installation package will have this base name assigned to it.
  6. If you are an enterprise admin, you will see a checkbox that allows you to build the installer as an MSI package. This option is useful for mass deployment of a custom installer to a machine cluster that will be designated to the given target group.
  7. You will be asked to provide an installer name, and optionally some notes. These are for internal records and will not appear within the created installer.
  8. Click on "Build Installer." You will be presented with the download link that you can either copy to the clipboard and send to your end user. Alternatively, you may download the installer directly for use in mass deployments.

Now that you have your installer, it can be run in one of two ways. In either case, the machine will be added to your list of machines in both your account as well as the RIM client after the installer is complete.

Normal Execution

The user will get a prompt when running the installer, containing the following information:

  • The technician's name along with their organization, if applicable
  • the nature of the connection, I.E whether a prompt is required or not

The user can choose to either answer yes or no to the installation. Answering no will cancel the installation. After the installer finishes, the user will get a prompt informing them that their machine is now set up for remote access.

Silent Install (Enterprise Installers Only)

A silent install can be initiated by running the executable installer with the /S command line parameter. This is useful when installing RIM as part of a mass deployment routine.

Session History

You can view your entire history of past sessions through the RIM dashboard. The session history currently contains the date and time of each session, the name of the computer you connected to, and the duration of the session. You may also choose to add comments to a session via the "Add Comment" link within the session row. This is useful for adding notes on the current status of an incident for your own sake as well as for the sake of organization administrators.

Managing your Subscription (Personal )and Pro Plans)

The dashboard allows you to easily view and manage your RIM subscription details. Upon clicking the "manage subscription" link, you can:

  • Upgrade your plan
  • Update your payment method
  • Cancel recurring payments

Upgrading your Plan

You can easily upgrade your subscription. If you are on a monthly plan, you will be prorated the remaining charge from the new amount, with the full new amount being charged for subsequent months. Clicking "Upgrade Subscription" reveals a page nearly identical to the initial plan selection page. There are a few notable differences which we will outline below:

  • You cannot downgrade your plan to one with fewer machines. You can, however, upgrade from a monthly to a yearly plan with the same number of machines as your current plan. In order to downgrade, you would need to cancel your plan, wait for it to expire, then initiate a new plan with fewer machines.
  • Enterprise plans, including the enterprise addon, cannot be acquired directly through this page.

Canceling Recurring Payments

When you click "Cancel Automatic Renewal," you will be asked for confirmation, after which your subscription will be set to expire at the end of the current term.

Frequently Asked Questions

Here are answers to some common questions concerning RIM. When faced with an issue, please refer to this document whenever possible. If your question is not covered, please Contact us.


What Platform(s) are supported?

The initial release of the client is only going to target Windows, but Mac and other devices are definitely on our roadmap. Windows is by and large the easiest operating system to work with when developing a remote access infrastructure, so while it is entirely possible to support RIM on more platforms, the process of implementing support for said platforms may be more involved.

Our company is still using Windows 7. Will RIM work under this configuration?

Yes, RIM supports Windows 7.

Connection Information

Generally speaking, how responsive is RIM?

The roundtrip latency during an RIM session is extremely minimal. Because we don't rely on a central service, most of the time your connections are direct from one computer to another - this is what is known as peer-to-peer. If your network configuration doesn't allow for peer-to-peer connections, we fall back to any number of relays located around the world rather than relying on one central server. Thus, even then your latency will still be farely minimal.

Where are your relays located?

Currently, we offer relays in the following locations:

  • U.S.
    • Virginia
    • California
  • Teronto, Canada
  • London, England
  • Warsaw, Poland
  • Bangalore, India
  • Singapore
  • Sidney, Australia
  • Sao Paulo, Brazil

General Session Troubleshooting

The target machine to which I am connected doesn't respond properly to keyboard commands that work fine on my keyboard. What's going on?

This could be due to a conflict in keyboard layouts. On rare occasions, if a keyboard layout is different enough from your own it may confuse RIM. Should that occur, please contact us with a report containing information about the keyboard layout of both machines.

After a computer is reimaged and has been reconfigured with the same computer name, is there anything that needs to be done to get RIM up and running again?

Simply remove the machine from your account, reinstall RIM, then add the machine back into your account.

Pricing and Payments

So, getting help from a person over RIM is totally free, right?

You bet! The subscriptions and/or one-off payments are for individuals and organizations seeking to offer remote assistance. No need to worry about getting a subscription if you're the person receiving help. In fact, you do not even have to set up an account if you are merely receiving help.

I don't really do remote assistance regularly, but I may be helping a friend or family member on occasion. Are there any options that don't involve a subscription?

Certainly! We do accommodate as many use cases as we can.

  • Anyone can assist a user over RIM for free for up to 30 minutes a day. So if you need to help someone install some software, fix a problem real quick, or send over a few files, we've got you covered. These minutes don't have to be used in one sitting.
  • There are, of course, going to be situations where a particular issue requires a little more time. Or maybe you're assisting someone learning a new piece of software and might be connecting on and off over the next few days. That's where our day passes and incident passes come in.
    • Incident passes allow you to connect to a single target as many times as is needed over a 24 hour period.
    • Day passes allow you to connect to multiple targets over a 24 hour period.
    • Packages of prepaid hours allow you to have a set number of hours available to be used entirely on your own time.
  • You can accumulate several of these passes and hourly packages and use them whenever the time calls for them. If you have multiple day passes, for instance, you do not need to use them consecutively. Similarly, You don't need to use your prepaid hours in one session or 24 hour period.

I purchased a package of prepaid hours. What happens to my free daily allotment?

Good news: Your free 30 minute daily allotment is not going anywhere! When you start a keyword-based session, RIM will start off by using your free 30 minute daily allotment. Your prepaid time will be used after your free 30 minutes is up.

How long will my prepaid hours last? Are they tied in with my subscription?

Prepaid hours are entirely separate from your subscription. That being said, your prepaid hours will remain in your account for one (1) year past the date they were first used.

How do I go about bringing RIM to the attention of my place of work?

We've assembled a Self-Advocacy Kit (SAK). A packet of e-mail formatted letters you can send to appropriate individuals on behalf of yourself or an employee. For the record, RIM provides the same functionality as less accessible mainstream solutions. As such, RIM can replace an existing infrastructure, rather than be used alongside one. It is therefore considered a reasonable accessibility accommodation and should be provided to you by your organization. Accessibility isn't a favor, it's a right to inclusivity.

What payment methods do you accept?

We process payments through Stripe, so we are able to directly accept Visa, Mastercard, Amex, or Discover. Additionally, Stripe can accept payments via Google Pay.

How do these passes work? Does the clock start immediately upon payment, or on the day I initiate the session?

Passes only begin when the controller initiates the session. So if the target's machine fails on them requiring a trip to the shop and a same-day turnaround is not possible, you can simply hold off until the machine is back in good shape and your day pass will still be waiting for you.

So this means these passes don't expire?

No. Rest assured that your accumulation of day passes will be waiting patiently for you to activate them whenever you're ready.

What happens if I connect to another machine on the day an incident pass has been used?

That depends. If the machine is within your subscription, I.E. if you're accessing your home machine while on the road, then it's business as usual. Any other connections that aren't the initial target you connected to will work under the usual 30 minute allotment.

I hold an active personal subscription. Would I still be able to assist a user outside the group of targets for up to 30 minutes, or via a pass?

Yes! Your 30 minute daily allotment is still present for any machine outside of your subscription. Additionally, acquiring a subscription does not replace any existing passes you may have.

I have a personal subscription, and the target computer underwent a hardware upgrade. Will Rim count this as a machine switch?

Only if RIM needs to be reinstalled. So, while a hard drive upgrade or any other situation requiring a Windows reinstallation would be considered a machine switch, upgrading the ram would not.

Our company bought the pro subscription, but we have two techs - one that does help-desk during the day, and a system maintenance tech that works in the evening. Would we be able to assign the evening sysadmin a controller seat?

Definitely. In situations where multiple technitions will be using RIM, we offer up to two (2) additional controller seats for $50 a month per seat - $500 a year per seat - to accompany the pro plan if needed. This will make it easier for multiple controllers at different workstations or offices to provide remote support.
If you have multiple controller seats, you can purchase additional channels for them so that sessions can run simultaneously. Each additional channel is $50 a month, or $500 a year.


Are RIM sessions encrypted?

Yes. All sessions, be they direct peer-to-peer connections or connections using a relay, are encrypted end to end using Datagram Transport Layer Security (DTLS). This is the same technology seen in the HTTPS protocol that modern websites implement for security.

Can Pneuma Solutions eavesdrop on sessions relayed by the public cloud?

No. Session key negotiation and encryption are performed end to end between the controller and the target. In other words, everything is encrypted before it even leaves your device. That way, the cloud service merely relays the data as is, making it impossible for the service to decipher the data.

What measures have been taken to prevent remote code execution (RCE) vulnerabilities?

All RIM code which is exposed to input from the network is written in memory-safe programming languages including Rust and JavaScript.

Is RIM HIPAA-compliant?

Yes. The best configuration in this case would be an on-premises deployment, so please get in touch with us if your use case depends on this.

Do any ports need to be opened on the target or controller?

No and no.

What connections would need to be allowed on a network in order for RIM to function?

When utilizing the public cloud, an https connection to is required. In optimal cases this is enough for RIM to establish a peer-to-peer connection between the controller and the target. However, it helps to allow UDP connections through ports 19302 and 3478 (the standard STUN and TURN ports). This ensures that if a relay is being utilized, RIM will not have to fall back to a tcp connection on port 443.

What background processes does RIM run, and are they light on system resources?

  • rim-host-service.exe: target process
    • This is an always-on background process that runs by default as long as RIM is installed.
    • It is very light on system resources
    • It runs with maximum privileges for the purpose of elevating RIM when needed, I.E. when user account control or a similar secure screen appears during a session.
    • It downloads some components of RIM in the background so as to reduce installation time and file size.
    • It does not phone home for any other purpose
  • Remote Incident Manager.exe: main executable
    • This process's background tasks depending on how the machine is configured.
      • Normally, Its purpose is to listen for and initiate automatic updates. It checks for updates every five minutes.
      • On unattended machines, it listens for and initiates unattended or prompted access connections requested by the controller.
    • Still fairly light on system resources
    • Phones home only with an anonymous machine ID. No personally identifiable information is ever transferred.
    • Unattended access background processing can be shut down via the icon in the system tray for disabling unattended access. A controller deleting a machine from the unattended access group has the same result. However, the main process will still run in order to check for and download updates.

Remote Accessibility Module

Is there anything the target machine needs to configure for first-time use of the Remote Accessibility Module?

Not at all! There are no dialogue boxes, permission request screens or anything of the sort.

Does the Remote Accessibility Module work on secure screens such as User Account Control?

Yes! Since the RIM host runs with elevated privileges, this allows us to leverage the Remote Accessibility Module for secure screens. Gone are the days of getting trapped in a user account control dialogue in the middle of a program installation!

What is the minimum version of NVDA required for the client support addon?

The current minimum version required is 2021.3.

Will the RIM Client Support addon run on a portable copy of NVDA?

Yes, and this includes secure screens since the RIM host process takes care of elevation.

Can I use the Remote Accessibility Module with the Windows Store version of NVDA?

This is not possible due to the Windows Store version of NVDA not allowing the use of addons. You'll have to either use a portable version of NVDA, or have your IT install the standard version of NVDA on your machine.

Unattended Sessions

Are voice conversations supported during unattended sessions?

No. However, prompted sessions do support voice conversations.

If I delete an unattended machine from my controller account, will it automatically revoke permission on the target?

Yes. Once an unattended target is removed, the change will be effective immediately. If the target machine is powered down or otherwise not connected to the internet, the change will be effective as soon as an internet connection is established on their machine.

The target machine rebooted after installing updates and drivers, and it requires a password to log in. How does the session continue from here?

RIM will attempt to automatically reconnect the session if an installation triggers a reboot. You will also be able to Control+Alt+Delete into the login screen if the target machine requires that.

I have multiple machines playing the part of the controller. Will the list of machines set up for unattended access populate across all machines?

Yes. The list of machines configured for unattended access is stored within your account, so it will populate automatically.


Remote Incident Manager is useful in a wide array of scenarios of varying frequency. Thus, our pricing structure makes every reasonable attempt to meet you where you are. Additionally, remember that RIM is always free for the person receiving help.

Free Tier

Anyone can use RIM to assist another user for up to 30 minutes a day. These minutes do not need to be used in one sitting, and a usage meter will keep tabs on how many minutes you have on any given day. Throughout your 30 minutes, you may connect to any number of people, over any number of interactive sessions.

Consumer Pricing


Passes are useful if you're providing assistance on an as needed basis. When you pay for a pass, that pass will wait patiently for you to activate it whenever you are able. This also means that you can hold several passes in storage and use them whenever they're needed.

Incident Pass ($10)

An incident pass will allow you to assist a single user for as long as is needed over a 24 hour period. At any point during the 24 hour period, reconnections can be made. So let's say you start out by setting up an overnight Windows re-installation. Once that machine is able to use RIM, you can come back and configure the end user's system as they see fit.

Day Pass ($20)

A day pass will allow you to assist several users over a 24 hour period. So if you have multiple errands to run, you'll want one of these.

Hourly Prepaid Packages

These packages allow you to have a designated amount of hours on your account. A 5 hour pass costs $25, and a 15 hour pass costs $50. These hours will last for a year from the date of their initial use, or a year from the date of purchase if not used. These hours can be used for any interactive sessions, and RIM will only deduct the exact, down-to-the-minute amount of time you used. For example, if you have 5 hours and you use 12 minutes, you will have 4 hours, 48 minutes remaining. Of further note is the fact that your free daily 30 minute allotment is prioritized before your prepaid time is used. If you run out of time, be it prepaid time or your free daily allotment, you will receive a 5 minute and 1 minute warning. If you are about to run out of paid time and you refill your account before the clock runs out, your session will be uninterrupted.

Personal Unattended Access Subscriptions

These plans allow you, as AN individual controller, to configure a set number of physical machines for unattended access. These plans are scalable (up to ten targets) in order to meet your needs. Whether you're simply looking to control your desktop from the road, or you're the go-to tech support for a few folks in your family, these plans have you covered.
Note that the subscriptions do not concern interactive sessions, I.E. those initiated via a keyword. The incident passes and day passes described above can be used alongside a subscription to facilitate interactive sessions. If you don't have any passes, the daily 30 minute allotment is used.

Number of TargetsMonthly PriceYearly Price

Personal Community Support Package

The personal community support package is useful if you occasionally provide technical support for tasks that run longer than the free daily allotment. This package gets you three (3) hours a day in addition to the 30 minute daily allotment. These hours do not roll over, and unattended access is not included in the base package. However, this package is available as an addon for personal unattended subscriptions. This package is available for $149 per year. A monthly option is not included.


RIM Pro is suitable for either a single support person or trainer, or a small support team. Each pro plan allows connections to an unlimited number of targets, as well as target group configuration.

RIM Pro Base Package ($99 per month, $999 per year)

This allows a single controller to control an unlimited amount of targets.


We offer upgrades to the number of controller seats and/or channels, as well as the feature set available to you.

Multi-seat and Multichannel Setups

Each additional controller is an additional $500, and so is its associating channel should you choose to allow for simultaneous connections equaling the number of controllers. Following is a breakdown of all available upgraded plans.

Number of ControllersNumber of ChannelsPrice

RIM Pro Enterprise Addon ($1000, plus $1000 for optional SSO integration)

This addon brings the features of RIM Enterprise to individual support reps or small units. Features include:

  • Unattended mass deployment to Windows servers
  • Completely silent mode for pre-configured unattended target installers
  • Optional integration with your organization's single-sign-on (SSO) system (requires an additional $1,000 setup fee).

Note: Identity verification may be required for this add-on.

RIM Enterprise Public Cloud Edition

The enterprise edition offers an unlimited amount of controllers and targets, along with the features described above. The price of each plan is determined by the number of simultaneous channels that can run at any given time.

  • 5 channels: $5000 per year
  • 10 channels: $7500 per year
  • 15 channels: $10000 per year
  • 20 channels: $12500 per year
  • 25 channels: $15000 per year

There is an additional one-time fee of $1000 for setup and onboarding, irrespective of which plan you choose.

activating a subscription or pass

When you make a purchase through RIM, you will be issued an activation link. Upon clicking the link, your pass or subscription will be activated and ready for use. Remember that the time period for a pass only begins when you initiate a remote session using said pass.

Change Log

Versions of RIM will be denoted by headings at level 2. Substantial updates with several features for both platforms will be divided into Mac and Windows subheadings at level 3.


  • macOS: We are unfortunately no longer able to offer automatic stereo microphone input in voice conversations on this platform, because in some cases, this prevented microphone input from working at all on a Mac. Note that this change has no effect on captured audio output from the target machine; that is still stereo.


  • macOS: Fixed a bug that prevented RIM from coming up when activating the application through the Finder or Dock, rather than using the global hotkey.


  • Voice conversations now automatically use stereo when the audio hardware supports it. This is useful when using RIM for training in audio production.


  • Fixed a recently introduced problem that could prevent RIM from working on a fresh operating system installation.


  • Fixed the message that displays remaining free time.


  • Localization of RIM into other languages is now in beta. The following languages are currently supported: German, Spanish, French, Italian, and Swedish. To use RIM in one of these languages, press the "Language (BETA)" button at the bottom of the "Provide Help" or "Receive Help" window, then choose your language from the drop-down list and press the "Switch Language" button. We look forward to your feedback.


  • The process of starting a new RIM session on the controller side is now smoother. The original window, where you entered your keyword or chose a target machine, will not go away until the main session window is ready. If the initial window no longer has focus when the session starts, e.g. if you switched tasks while waiting for the target user to enter a keyword, then RIM will notify you that the session is ready, and the main session window will appear when you return focus to RIM.
  • macOS only: As part of the previous change, we modified the way that RIM adds and removes itself in the Dock and the Command+Tab list. Please let us know if you find any problems with the current behavior.
  • Windows targets only: If a screen reader is started on the target machine while remote accessibility is active, then remote accessibility will quietly shut down to avoid double speech output.


First official release for Mac OS! New features include:

  • ability to configure unattended or prompted sessions from within an interactive session.
  • All new permissions instructions for users who are not using VoiceOver.


This version provides a consistent, cross-platform way of opening the RIM controller session menu with the mouse. A controller can either click the large RIM icon at the upper-left corner of the session window, or as was previously possible on Windows, they can right-click anywhere on the title bar.



  • Added support for the FN+Number key workaround for using the function row on MacBooks.
  • RIM for Mac now customizes the menu bar, and in particular, the "About" option on the application menu now opens our own About dialog rather than the generic one.



When connecting a Mac controller to a Windows target, with both sides using the same non-US keyboard layout, keyboard input from the controller wasn't being translated correctly. Version 3.1.47 for Windows fixes this problem.


  • Added support for the new RIM Personal Community Support subscription package.



RIM is now able to automatically resume capturing screen content and audio output if the target machine switches to the lock screen during a session.



  • Implements reboot and reconnect for Mac targets, including both standard and emergency reboots.
    • As with unattended access, RIM doesn't come up on the macOS login screen due to platform restrictions, particularly FileVault. So the target user will need to log back in before RIM can reconnect.
  • The notification about file transfers, introduced in the previous update, is now shown only once per RIM session.



  • This update modifies the user interface for file transfers. When one or more files are placed on the clipboard on either side of the connection, the controller now receives a notification saying that the file transfer can be completed through the RIM menu. If the controller chooses this menu option, the file transfer is performed, and when done, a temporary folder containing the transferred file or files is opened on the destination machine. This method of file transfer is necessary when the destination machine is a Mac. When the destination is a Windows machine, the file transfer can be completed using either this new method or the old method of pasting in File Explorer on the destination machine.



  • RIM for Mac now works as an unattended target. It also performs updates in the background as the Windows version does.
    • We still have some work to do on access to the lock screen, and we don't believe we'll be able to provide access to the login screen before a user is logged in at all, due to limitations of the platform.
    • we haven't yet figured out how, or if, we'll be able to implement pre-configured target installers, so you'll need to use one of the other available methods of setting up unattended access.
  • Eliminates one source of latency in audio captured from Mac targets.



Fixed a problem that sometimes caused RIM to crash in response to activity on the Windows clipboard during a RIM session.


Adds some more logging related to audio on the target. So if you can reproduce laggy audio on the target, please do so with this version, then send logs.



This update adds mouse support for Mac targets. RIM now requests permission to use macOS accessibility features. For new installations, this replaces the input monitoring permission request, so the total number of permission steps doesn't go up. But for updates, you'll need to grant this permission before you can use RIM after updating.



Fixed a crash that was affecting Mac targets at session initialization.


This update marks a major milestone in the Mac port of RIM. The remote accessibility feature of RIM is now available when connecting to Mac targets. Using a special configuration of VoiceOver on the target machine, the controller, whether using Windows or Mac, will hear speech while the target user does not hear any speech or sound effects. There is also no visible indication that VoiceOver is running on the target. The process of starting remote accessibility, either automatically or manually, works just as it does with Windows targets. And of course, when the session ends, the special configuration of VoiceOver is shut down, and VoiceOver is restored to its previous settings.

Note that both Windows and Mac controllers now need to be running version 3.1.37 to get full functionality when connecting to a Mac target.



The remote accessibility feature is now compatible with NVDA 2023.1.



  • RIM now consistently uses stereo audio, particularly for Mac controllers.
  • When using RIM for Mac as a controller with the remote accessibility feature, RIM now uses the voice and speaking rate as defined in the Spoken Content section of system settings.



When a Mac controller connects to a Windows target that's not running a screen reader, you can now run the remote accessibility module on the Windows target and get speech output on the Mac controller. Note that you still need to use NVDA keyboard commands when interacting with the Windows target, not VoiceOver commands, and we're using the NVDA laptop keyboard layout.


In response to user feedback, we removed the sound effect when displaying notifications about the status of a remote session.



RIM now supports the Fn key when using a Mac laptop as a controller.
Note that for the top row of function keys, RIM always treats them as F1 through F12, and you need to use the Fn key if you want to use these keys as system function keys (for adjusting volume and so on), regardless of how the system preference is set on either end of the connection. We figure that in a remote session, you probably want to use these keys as F keys most of the time anyway. Behavior like using Fn+Left Arrow to press Home works as expected.



  • RIM previously didn't let go of its lock on keyboard input when some dialogs were displayed, such as the dialog requesting permission to access the microphone. This is now fixed.
  • When connecting from Mac to Windows or vice versa, it's no longer possible for the controller to trigger the RIM menu on the target machine. This fix requires the corresponding update to RIM for Windows.


  • Added a way to send RIM's log files to Pneuma Solutions, introduced for Mac OS in version 3.1.29. Please only use this function if requested by a representative of Pneuma Solutions.
  • RIM now plays a sound whenever it displays a notification.



RIM will now request permission to display notifications, both on first run and for existing users updating from a previous version. As with most other permissions, granting this permission requires flipping a switch in System Settings. We've also added our own sound for these notifications.



  • We believe the problem that some users have reported with requesting keyboard input monitoring permission on machines running Karabiner Elements is now fixed.
  • The RIM About dialog now has a button to send logs. Please only use this if requested by Pneuma Solutions.



When using RIM as a controller, it is now compatible with advanced keyboard customization tools such as Karabiner Elements.



This is a minor update, with just two changes:

  • Marked RIM as requiring macOS 13.0 (Ventura) or later.
  • Fixed RIM so the virtual keyboard is only connected when RIM is actually running as a target. This means that the Keyboard Setup Assistant won't appear when using RIM as a controller. We're still looking into possible ways to avoid that dialog altogether.


Initial beta build of RIM for Mac OS.


  • When connecting to a target machine with lower display resolution or a higher dots-per-inch (DPI) scale factor than the controller, RIM now scales the remote target display to fit the controller's screen, making the remote display easier to work with visually.


  • Added support for prepaid hours.


  • Fixed a bug that sometimes caused RIM on the target machine to get into a loop that prevented unattended connections.


  • Added a new keyboard shortcut, Windows+Shift+M, while in a session window, to minimize the window and return the keyboard focus to the local (controller) machine.


  • Added logging that will help us diagnose reports of unattended targets being intermittently disconnected from RIM.


  • Fixed some corner cases in remote keyboard input handling. In particular, when running JAWS on the target machine, JAWS now correctly recognizes Pause and NumLock key presses from the controller. Please let us know if you find any regressions in keyboard input handling, particularly for non-US keyboard layouts.


  • Fixed a problem that prevented RIM from updating itself on target machines that were on the Windows Sign-in screen with no active user session.


  • Since the previous update, we've received reports of the Shift modifier being stuck on the target machine when running JAWS. We believe this update resolves that problem. Please let us know if you continue to have trouble with stuck modifiers.
  • Fixed a bug that caused RIM to shut down NVDA on the target machine at the end of a session if NVDA was started on the target machine after enabling remote accessibility.


  • When running JAWS on the target machine with Unified Keyboard Processing enabled, JAWS now reliably responds to keystrokes from the controller.
  • Fixed an error that sporadically occurs when starting the remote accessibility add-on after installing or updating the NVDA add-on on the controller machine.


  • When you connect to a target machine with no running screen reader, RIM will automatically enable remote accessibility if you are running a screen reader on the controller machine. If you're running a screen reader other than NVDA on the controller machine, RIM will even automatically shut down that screen reader and start NVDA if you have it installed.
  • Fixed issues that prevented the remote accessibility module from using your local NVDA configuration settings such as keyboard layout and typing echo.


  • The process of re-establishing a connection when there is a connectivity issue is now more robust.
  • Fixed a problem that sometimes caused RIM's background update process to stop.
  • If the controller is running an older version of RIM than the target, the menu no longer includes an option to update the target.
  • If a screen reader or RIM's remote accessibility module is running on the target machine, you can now stop it through an option on the menu.


  • Fixed a bug that caused users to get logged out of RIM after installing some Windows updates.


  • By popular demand, RIM no longer prompts for a comment at the end of each session. You can still post comments on sessions in the RIM Dashboard. We may add a configurable option to prompt for a comment as a feature in the future.


  • If the target machine is running at least this version of RIM, but hasn't yet updated to the latest version, the controller can now force the target machine to update its installation of RIM through a new option on the session menu.


  • You can now optionally add a comment at the end of a RIM session. Session comments can be viewed in the RIM Dashboard.
  • The Connection Details window is enhanced. The statistics are updated live as long as the window is open, and the window now includes information about the target machine.


  • Fixed a problem that sometimes caused a RIM session to get stuck trying to reconnect.


  • Fixed a problem that sometimes prevented the remote accessibility module from starting.


  • When choosing a target machine for an unattended or prompted session, you can now search through your target machines. To do this, on the Provide Help screen, press "Choose machine" as before, tab to the "Search" field, enter the text to search for, then either press Enter or press the "Search" button.


  • Fixed a problem that sometimes made it impossible to interrupt JAWS speech on the secure desktop.


  • Fixed a visual display bug that caused the list of unattended target machines to overlap with the buttons below it.


  • Enterprise customers can now deploy RIM using an MSI-based installer.


  • Fixed a bug that could cause RIM to crash if the RIM menu is open when a session is reconnected.


  • Adjusted the visual style to be more accessible to low-vision users.
  • Added error messages if required fields are left empty.


  • When you press the "RIM Dashboard" button in the Provide Help window, that window now stays open.


This release adds a complete management dashboard for controllers.

  • All subscribers have access to the dashboard, with feature sets determined by subscription tier.
  • Removed the in-app functions for renaming, deleting, and creating installers for unattended machines as this is now part of the dashboard
  • Brought back the welcome page.


Fixed a bug that sometimes prevented remote screen output from working when a User Account Control prompt was displayed.


  • This is a bug-fix update.


  • Users with either a RIM Enterprise subscription or a RIM Pro subscription with the Enterprise add-on can now create fully silent pre-configured installers for unattended access. To run an installer in silent mode, whether it's the standard installer or a pre-configured installer from an enterprise account, use the /S command line switch (note the capitalization) when running the installer.


  • This is a bug-fix update.


  • This update restores compatibility with Windows 7.


  • RIM no longer mistakenly shows the "Create an Installer for Unattended Access" button if you don't have a subscription.


  • If you have purchased one or more RIM passes, you now have control over whether a particular session will use a RIM pass or the free tier, as well as which pass will be used. RIM also tells you how much time is left on your selected pass.


  • This update introduces support for the new RIM personal passes, which let you use RIM for remote technical support or training for up to 24 hours for as little as $10. Try a RIM pass today.
  • The button that used to be called "Create a Pre-Configured Target Installer" is now called "Create an Installer for Unattended Access".
  • When renaming an unattended target machine, the existing name is now filled in and selected for easy editing.


This release concludes the RIM public beta. RIM pricing plans and restrictions on free usage are now in effect. For free accounts, RIM now displays a usage meter along with a purchase button.


Fixed a bug that prevented the new Windows+Shift+Backspace hotkey from working in some situations.


  • The Control+Shift+Backspace hotkey is no longer active in RIM. The official hotkey is now Windows+Shift+Backspace. Windows+Shift+Escape also remains available during a session.
  • RIM's new main hotkey, Windows+Shift+Backspace, is now active at all times on machines where RIM is installed, unless another application claims the hotkey first. When a RIM session is active on the controller, this hotkey opens the RIM menu if the session window is focused, or focuses the session window if it's in the background. On the target, this hotkey opens the RIM target menu while the session is active. On either side, if a session is not active, this hotkey opens the RIM window to start a new session.
  • When requesting unattended access, RIM now reliably focuses the approval dialog on the target machine.
  • Updated the remote accessibility module.


You can now create a pre-configured installer that will automatically register all machines on which it is installed as unattended targets in your RIM account.

To do this, use the new button called "Create a Pre-Configured Target Installer", on the "Provide Help" screen. You will then need to enter a base name for the target machine(s); RIM will automatically add the host name of each target machine to this base name. Once target machines are registered, you can rename them as with any unattended target. You can also set the expiration date of the installer, which must be between 7 and 30 days. Once RIM has created the installer, you'll get a link that you can either share directly with the target users, or download yourself so you can share the installer some other way.

Note that when a target user runs the pre-configured installer, it will first show them a confirmation dialog which explains what the installer will do. This dialog includes the name of the controller who created the installer. This confirmation step is designed to prevent abuse. A completely silent mode will be available for enterprise customers.


  • RIM now has a new option for registering a machine for unattended access under your RIM account without having to start a remote session using a keyword. On the machine that you want to register, press the new button called "Register This Machine for Unattended Access", on the Receive Help screen. Then log into your RIM account if you haven't already done so on that machine, enter a name for the machine, and you're done. Note that we're still working on a way to customize the RIM installer, to enable mass deployment and make it as easy as possible to set up unattended access on machines that you don't already have access to.
  • RIM now prevents you from trying to open an unattended connection to the same machine where you're running the controller.
  • We're now experimenting with a third hotkey to open the RIM menu: Windows+Shift+Backspace. That means there are now three options: Windows+Shift+Escape, Windows+Shift+Backspace, and Control+Shift+Backspace. We haven't yet made a final decision on which hotkey or hotkeys to keep, but we will decide before the end of the public beta. We appreciate your feedback.
  • Most options on the RIM menu now have single-letter keyboard shortcuts that you can press once you've opened the menu.
  • This update introduces a more reliable solution to the intermittent problems that users have reported with JAWS not recognizing keyboard input from RIM. Please let us know if you continue to have problems with this scenario.


  • This update introduces two new hotkeys. Windows+Shift+D disconnects the session when pressed on either side. For the controller, Windows+Shift+F flips the session.
  • This update adds safeguards against keyboard modifiers becoming stuck on either machine.
  • There's a new menu option, "Lock the Target Machine", which is equivalent to pressing Windows+L on the target.
  • RIM now has an "About" window, where you can check the version number, contact Pneuma Solutions for support and feedback, read the manual, and view the version change log.
  • RIM no longer prompts for feedback at the end of a session or when closing the "Provide Help" window.


This update fixes a few bugs in the reboot and reconnect process. We haven't yet diagnosed everything that has been reported, but we were able to find and fix a few issues in our own testing.


  • RIM now updates itself in the background on all machines. RIM now includes the currently installed version number in the tooltip of its tray icon. This is the last update users will need to install manually, irrespective of machine configuration.
  • If the target machine is rebooted, but not using RIM’s Reboot and Reconnect feature, RIM now asks the controller whether they want to reconnect to the target after the reboot. If the controller answers no, then the target won’t wait for a reconnect after the reboot.


  • RIM now updates itself in the background on unattended target machines. This is the last update that you will need to install manually on your unattended targets.
  • When updating before an interactive session, RIM no longer needs to go through User Account Control. This means that non-administrator users can update RIM once it has been installed for them by an administrator.


This is a bug-fix update. Please note that unattended targets still need to be updated manually by running the latest RIM installer. However, now you will be able to connect to an unattended target after the installation is done, without requiring someone to close the "Receive Help" window.


  • The Reboot and Reconnect feature is now implemented. Using the new Reboot and Reconnect option on the controller’s RIM menu, you can do either a standard or emergency reboot, and automatically continue the session when the reboot is complete. RIM will also reconnect if the target machine reboots for some other reason, such as when an installer reboots the machine.
  • RIM also automatically attempts to reconnect if the connection drops for any reason. This will help with unreliable Internet connections.
  • When running an unattended session or using Reboot and Reconnect, you can now use RIM while the target machine is on the Windows Logon screen. Note that RIM will need to reconnect the session when the target machine transitions from the logon screen to the main desktop. This is a known limitation of the current implementation which we may address in a future update.
  • RIM is now fully functional when the target user does not have administrator privileges on the target machine, as long as the Remote Incident Manager Host service is running on that machine. Note that administrator privileges are still required to install RIM updates. Also note that new versions of RIM still need to be manually installed on unattended targets. We are working on solutions to both of these problems.

If you've set up unattended access to one or more target machines, you can now create a shortcut to directly access any of these machines. Just press the "Create Shortcut" button under the list of unattended targets, and RIM will create a shortcut on your desktop.


RIM now works on a target machine that has no audio device. This, combined with the existing remote accessibility module, opens up access to servers and virtual machines that could previously not be accessed with a screen reader except through RDP and its very suboptimal audio output.


  • If you haven’t yet pre-ordered the first year of your RIM Pro subscription, you can now easily do so using the new button on the “Provide Help” screen. We are also introducing new pricing options for adding extra controllers and concurrent channels to a RIM Pro subscription. You can add up to two additional controller users and two additional channels for $500 per year each. RIM continues to be free during the public beta, but if you pre-order your subscription now, you will have uninterrupted service when the public beta concludes on September 1.
  • We are introducing Control+Shift+Backspace as an alternative hotkey for opening the RIM menu on both sides of the connection. We also still support Windows+Shift+Escape for now, but the plan is to standardize on Control+Shift+Backspace as the one hotkey for all stages of RIM.
  • If you press the “Provide Help Instead” button on the “Receive Help” screen, RIM no longer sets this choice as the default until you have logged into your RIM account.
  • Fixed a few JavaScript errors that occurred in rare cases.


you can now use the mouse wheel in a remote session.


Hopefully fixed all remaining issues causing the installation process to hang.


This version includes some changes under the hood. In particular, we've included updates to the installation and underlying packages to address issues causing the installation to hang.


  • There is now an option on the RIM menu to send Control+Alt+Delete to the target machine.
  • You can now open the RIM menu by right-clicking on the title bar of the session window. We plan to add the option of opening the RIM menu by clicking on the RIM icon at the left end of the title bar as well.


  • The controller can now flip an unattended session.
  • The controller can now rename an unattended target machine.
  • Fixed a bug that sometimes caused the session to become unresponsive after copying to the clipboard.
  • Fixed a bug that sometimes caused starting the remote accessibility module to fail with a JavaScript error.


Fixed a conflict between the RIM Client Support NVDA addon and the Dropbox addon.


  • You can now pre-order the first year of your subscription to RIM Pro for $999. The link to pre-order will be available in the feedback window when you finish a remote session. Or you can follow the direct link here: Pre-order RIM Pro.
  • If you have unattended target machines in your RIM account, the button to start an unattended session is now more reliably displayed on the “Provide Help” screen.
  • When flipping a session, the original controller can now flip the session back, by opening the RIM menu with Windows+Shift+Escape.