Copyright © 2022 Pneuma Solutions
Remote Incident Manager (RIM) is a powerful, 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
If you are coming from previous remote desktop applications or screen reader-based assistance tools, you will find that RIM significantly streamlines your workflow.
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.
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.
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.
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.
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.
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.
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.
RIM is the first remote access solution that provides unparalleled accessibility, irrespective of the screen reader (or lack thereof) that either party is using.
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 Narrator; 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.
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 the free NVDA Screen Reader. 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.
- Key combinations are denoted by the plus symbol, i.e. windows+shift+escape.
- 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.
In order to run Remote Incident Manager, your computer should meet or exceed the following minimum requirements:
- Windows 7 SP1 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.
There is only one installation package to use, whether you are offering or receiving assistance.
- Download Remote Incident Manager
- Run the downloaded file.
- If you have user account control enabled, press Alt+Y to approve the installation.
- 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.
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.
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.
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.
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!
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.
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.
- Enter your email address.
- Check your email for a verification code, and then enter it into RIM.
- You will then be asked to enter your name, location and phone number.
- Lastly, you will receive another verification code on your phone. Enter this code into RIM.
- 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.
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.
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.
As mentioned earlier, accessing the RIM menu directs you back to your machine. There are a number of options in this menu. They include:
- Minimize Session: brings control back to your machine as described above
- 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 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
- 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 are quick and easy, as the standard copy/paste process works across the session.
- Bring up the RIM menu, and click on "Minimize Session." Control will be directed back to your computer.
- Select the file(s) and/or folder(s) you want to transfer using your file manager of choice. It doesn't matter if this is Windows Explorer, or a third party solution such as Total Commander.
- Copy the selected contents to the clipboard in the usual way.
- Switch back to the remote session, and locate the folder on the target machine where you wish to paste the content.
- Last but not least, paste as you normally would.
That's it, the content will instantly begin transferring to the target computer! Note that the transfer time will depend entirely on the size of the content being sent as well as your network speed.
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.
For first-time initialization of the accessibility module, here is what you will need to do:
- Bring up the RIM menu.
- Select the "Start Remote Accessibility" option.
- 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.
- By now, the remote accessibility module will be fully initialized, and you will hear speech output as you control the remote computer.
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.
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.
RIM allows you, as the controller, to configure machines for unattended 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. You may also want to allow this for your home computer should you need to access it from someplace else.
There are a few ways to configure machines for unattended access.
- Bring up the RIM menu.
- Select "Request Unattended Access."
- 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.
- Press enter.
- On the client machine, a dialogue pops up asking the user if they're fine with their computer being set up for unattended access. If they answer yes, then you will get a prompt informing you that unattended access has been approved.
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.
- Start RIM in Receive Help Mode.
- Click on the "Add this machine to your RIM account" button.
- Enter your email, then click next.
- Wait for the two-step login code to arrive, enter it, then you should be logged in.
- You will be asked what type of access you would like configured for this machine. Your options are:
- Unattended: Allows sessions to be initiated without any intervention whatsoever from the end user.
- Prompted: This configuration presents the user with a prompt informing them that you are conecting to their machine.
- Give the machine a name, then activate the "Add Machine" button.
- The machine will be registered to your account, which will allow any controller machines logged into your RIM account to connect to this machine.
Now that we've registered the machine for unattended access, here is how we will start a session.
- Start RIM in controller mode.
- Rather than entering a keyword, locate and activate the"Choose a machine" button.
- When you click this, a list of machines will appear. Choose the one you want, then hit enter.
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 unattended sessions.
For extra convenience, you can create desktop shortcuts that allow you to automatically launch unattended sessions. In order to do this:
- Access the list of unattended computers, and select the one you want to create a shortcut for.
- Click on the "Create Shortcut" button.
- 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.
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 greatly 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.
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.
- Access the Remote Incident Manager icon in your system tray.
- If using the keyboard, press windows+b, then space, then left or right arrow until you find the icon.
- Right click this icon, or press the applications or shift+f10 key.
- Select the "Revoke Unattended Access" option.
- You will arrive at a list of computers, select the one you want to revoke.
- 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.
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 installers. On the other hand, anyone (including personal users) can create custom installers for their unattended machines.
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.
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
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.
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.
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:
- In the target management screen, click the "Build Target Installer" button.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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, or 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.
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.
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.
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.
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
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.
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.
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.
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.
Yes, RIM supports Windows 7.
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.
Currently, we offer relays in the following locations:
- Teronto, Canada
- London, England
- Warsaw, Poland
- Bangalore, India
- Sidney, Australia
- Sao Paulo, Brazil
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.
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.
- You can accumulate several of these and use them whenever the time calls for them. In other words, if you have multiple day passes, you do not need to use them consecutively.
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.
No. Rest assured that your accumulation of day passes will be waiting patiently for you to activate them whenever you're ready.
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.
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.
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.
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.
No and no.
When utilizing the public cloud, an https connection to https://getrim.app 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.
- 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.
- This process's background tasks depending on how the machine is configured.
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 or anything of the sort. In fact, the self-contained copy of NVDA that the target machine will run does not speak, so the target will not even have to concern themselves with it.
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!
The current minimum version required is 2021.3.
Yes, and this includes secure screens since the RIM host process takes care of elevation.
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.
The target requires assistance with an application that is made accessible via an NVDA addon. Will addons function with the Remote Accessibility Module?
Unfortunately this isn't something we officially support. In these unique circumstances it may be better to transfer a portable full version of NVDA over to the user's machine with your specific configuration. When you launch the portable copy of NVDA, the Remote Accessibility Module will quit on its own. After your work is done, you can relaunch the Remote Accessibility Module to assist you through deleting your portable version of NVDA off of the target computer.
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.
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.
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.
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.
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.
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 Targets||Monthly Price||Yearly Price|
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.
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.
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 Controllers||Number of Channels||Price|
This addon brings the features of RIM Enterprise to individual support reps or small units. Features include:
- Unattended access 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.
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.
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.
- 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.
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 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.