Open the Table of Contents
You are here: About Commuter Licensing > Remotely Obtaining Commuter Licenses > Overview of Remotely Obtaining Commuter Licenses
Overview of Remotely Obtaining Commuter Licenses
WRCommute (the Windows-interface utility) and rcommute (the Windows/UNIX
command-line utility) are provided to allow the remote user to generate
a commuter locking code to send to the local user checking out the commuter
authorization from the Sentinel RMS License Manager, and also to install
the commuter authorization received from the network user.
Here is an overview of how to obtain and install a remote commuter authorization:
- A remote user
runs WRCommute or rcommute
to generate a commuter locking code for the remote computer, and sends
the commuter locking code to the local user who has access to the Sentinel
RMS License Manager.
- The local user
runs WCommute or lcommute (entering the remote
user’s commuter locking code) to check out a remote commuter authorization,
and sends it to the remote user.
- The remote user
runs WRCommute or rcommute
to install the remote commuter authorization.
Notes:
- The commuter
locking code used to lock a commuter authorization is not the same as
the locking code displayed by echoid.
You must use WRCommute
or rcommute to obtain it.
- A remote commuter
authorization cannot be checked back into the License Manager, but will
simply expire on the remote computer.
- The duration of a remote checked out license can be extended before its expiration. See Extending Remote Check Out Days.
- Remote clients using applications licensed using RMS v8.1.1 (or earlier) must ensure that the versions of the tools used in this process—such as, WRcommute, rcommute, Wcommute, and lcommute—are matched.