Application Files

Select an application category from the list below to see all the downloadable files and their descriptions in that category. Go to Archived Applications Files to find previous versions of applications.

RMS Enterprise

Prerequisites

  • RMS Enterprise will only migrate data from an RMS 3.3 database. Any older RMS versions must first be upgraded to 3.3 before attempting to install RMS Enterprise and migrate data to it.
  • For complete system requirements, please refer to the RMS Enterprise Installation Guide.

Changes in this release

  • Implemented the display of location schedules on mobile devices
  • Implemented support for the RMS Enterprise Scheduling Interface for Google Calendar
  • Fixed a bug in the Configuration pages where the display of a manufacturer / model URL that contains a dash would be truncated
  • Improved time zone support for Australia and New Zealand. New mechanism to add / remove time zones via the includeTimeZones.txt configuration file
  • Internal changes implemented to support hosted RMS
  • Added new feature: System Maintenance Mode
  • Added support for TLS encryption when configuring the SMTP server for notifications
  • Fixed some crosstalk between the Lamp Life and Source Usage dashboard widgets so that refreshes don't lead to missing data and buggy rendering
  • Enhanced the server to inform the client gateway of the location's localized short time and date patterns for better localization on the touch panels
  • Fixed a bug so that changes to boolean metadata values are reflected in the UI
  • Fixed a bug on the RMS Server where a client gateway re-init or a reboot of the master would disable the bargraphs of the asset parameters

Known Issues

  • Report queries that use exact whole number filter (Equal or Not Equal) in the hour value for Lamp Hours will not return a positive report unless the value is a whole number (does not include a decimal).
  • System upgrades from RMS 3.3 to Enterprise will initially report Hotlist items that are based on UTC time. At the time of migration to RMS Enterprise, the application timezone is not set, so the timestamp will appear to be inaccurate.
  • RMS does not fully support localized floating point numbers. Due to a limitation with Flex/Flash, the RMS user interface always displays floating point numbers in the US format with a period (e.g. 3.14) rather than with a comma as used in some countries (e.g. 3,14). Also, any text fields that allow user entry of floating point numbers also require them to be entered in the US format. The only exception is that RMS reports do render floating point numbers correctly based upon the user's locale.
  • The mobile location scheduling view has encountered a variety of issues on certain mobile platforms detailed below (If you experience an issue, try Chrome, Firefox, or Safari which functioned properly in our tests):
    1. The Samsung Galaxy S3 and S4 running the default browser ("Internet") on Android 4.3 fails to render the meetings in the hourly schedule grid
    2. The Motorola Photon 4G running Android 2.3.5 crashes with a stack trace when the mobile page display is attempted
    3. The Nokia Lumia 1020 running Internet Explorer on Windows Phone 8.0 will only show the full meeting details if the QR code is rescanned while the user is logged in
    4. The Nokia Lumia 2520 tablet running Internet Explorer on Windows 8.1 RT does not display the full meeting details (only limited details can be seen)
    5. The Puffin browser on Android results in "Error 102 (net::ERR_CONNECTION_REFUSED)"

Hot Fix for the RMS Enterprise (v.4.3.13 Available from AMX Technical Support)

Changes in this release:
Fixed a bug with the database update scripts that was reported in the field. The bug was causing the RMS server upgrade to fail during installation.


ZIP | 234.78 MB | v. 4.3.12 | 2014-03-28
RMS-ENT
RMS-ENT-SCH
RMS-ENT-SMA
RMS Enterprise Software Development Kit

Prerequisites

  • None

Changes in this release

  • Updated to prevent messages from exceeding the maximum message size.
  • Fixed an issue which could prevent parameter updates from being received from duet modules.
  • Fixed an issue which prevented registration of the power status parameter and control method for certain TV and Monitor devices.
  • Corrected an issue which could result in out of memory errors under certain conditions.
  • Corrected an issue which sometimes prevented detailed meeting information from being correctly displayed when in a multi-location configuration.
  • Increased the page timeout values for the meeting ending dialogues that are included with the sample touch panel pages.
  • Asset parameter thresholds associated with the online status asset parameter will now be registered with a default status type of Location Communications Error.
  • Fixed an error in the HVAC NL monitoring module related to cooling and heating setpoints.
  • Optimized the DVX monitoring module to be more efficient in certain scenarios.
  • Fixed an issue with the DVX monitoring module which prevented the front panel lockout parameter from updating correctly.
  • Added the ability to configure a default subject and message for new meetings.
  • Added support for the LED indicator that is included with certain Modero X touch panels.
  • Fixed error that sometimes occurred when a location was not mapped to a scheduling resource.
  • The duration time is now unable to go below 15 minutes on the scheduling panel.
  • Fixed an issue which prevented new meetings from being created while an active meeting was in progress.
  • Fixed an issue which sometimes caused the meetings to be scheduled one minute into the future.
  • When relocating a touch panel asset on the server, the client will now properly reconfigure it's connected touch panel displays to reflect the new locations.
  • Text entered via help requests, maintenance requests, and the meeting creation pages will now allow the usage of the comma and carriage return characters.
  • Fixed an issue with the NetLinx SDK which sometimes caused the active meeting event to be included with the set of next active meeting events.

Hot Fix for the RMS Enterprise Software Development Kit (v.4.1.17 Available from AMX Technical Support)

Changes in this release:

  • Messages received via the RMS Scheduling NetLinx API will now be encoded correctly when they contain extended ASCII(ISO-8859-1) characters.
  • Previously, when a meeting ended, an end and start event were sent. This issue has been corrected and these events will no longer occur.
  • Fixed an issue which prevented the end booking response message from being sent unless logging was set to DEBUG.
  • Previously, when an ad hoc create meeting command was issued, two events with differing booking IDs for the same booking were sent. The event with the non-standard booking ID will no longer be sent.
  • Addressed an issue which sometimes caused the server API URI to become corrupted.
  • Fixed an issue which would prevent the organizer from being populated in the event booking response data structure.
  • Fixed an issue which would could prevent meeting info on touch panels from being displayed if no location or application locales were selected in RMS.
  • Fixed an issue which prevented the Display Usage asset parameter from updating.
  • Fixed an issue which prevented GUI Adapter generated times and dates from being formatted based on the associated location locale.
  • The response returned from the ?asset.location command will now contain the client key.
  • Added two helper functions to the NetLinx GUI Adapter API to force the date and time formatting patterns to a specific pattern for all touch panels.


ZIP | 38.13 MB | v. 4.1.13 | 2013-09-13
RMS-ENT
RMS-ENT-CLOUD
RMS-ENT-SCH
RMS-ENT-SMA
RMS Enterprise Scheduling Interface for Google Calendar

Prerequisites

  • RMS Enterprise Server version 4.3 or later
  • Google Apps account
  • If installing the RMS Enterprise Scheduling Interface for Google on a Windows Server, it is a requirement to also install the Windows Feature called Desktop Experience in order for the RMS Scheduling Configuration Tool to work properly

Changes in this release

  • Initial implementation of appointment synchronization between Google Apps and RMS Enterprise

Known Issues

  • Altering the attendees on an individual occurrence of a recurring meeting changes the attendees on all occurrences in RMS. This is due to a limitation on the RMS Server that does not support unique attendee lists at the Booking level. In RMS, attendees are tied to the Event which represents the recurring meeting (i.e. the entire series).


ZIP | 32.73 MB | v. 1.0.10 | 2014-03-28
RMS-SCH-GGL
RMS Enterprise Scheduling Interface

Prerequisites

  • RMS Server version 4.1.10 or later. This release of the Scheduling Interface requires some new web service APIs on the RMS Server.

Changes in this release

  • The Scheduling Interface and Configuration Tool have been modified to support RMS Lotus Notes Plug-in.
  • Consumes new scheduling web service APIs on the RMS Server to optimize appointment synchronization for better performance and scalability.
  • Added a fix to strip invalid, non-printable control characters from the subject and details of the appointments before they are sent to the server.
  • Cleaned up the existing database resource profiles before registering a new plugin.

Known Issues

  • This release only supports the Exchange EWS and Lotus Notes scheduling plug-ins.
  • Notifications of new / modified event bookings are not supported in this release.
  • Welcome text and welcome image configuration and display on touch panels are not supported in this release.
  • There are no scheduling related reports in this release.


ZIP | 1.39 MB | v. 4.1.19 | 2013-09-13
RMS-ENT
RMS-ENT-SCH
RMS-ENT-SMA
RMS Enterprise Interface for Microsoft Exchange Web Services (EWS)

Prerequisites:

  • RMS Enterprise Server version 4.1.10 or later.
  • RMS Enterprise Scheduling Interface version 4.1.19 or later.
  • Microsoft Exchange 2010 SP3.

Changes in this release:

  • Made significant performance improvements when synchronizing appointments from Exchange to RMS Enterprise via the EWS API.
  • Corrected the mapping of Recurring Master appointments and their individual Occurrences. A Recurring Master is now represented by a single Event record for the series in the RMS database and the Occurrences each have a Booking record.
  • Removed the synchronization window. The plug-in will not sync appointments that are in the past and will sync all future appointments into RMS. The only caveat to "all future appointments" is listed in the Known Issues below.

Known Issues:

  • Recurring appointments in Exchange 2013 that have "No End Date" specified will result in an error: "You have exceeded the maximum number of objects that can be returned for the find operation. Use paging to reduce the result size and try your request again."
  • Recurring appointments in Exchange 2010 that have "No End Date" specified will be limited to two years of occurrences synchronized into RMS. After the two years elapses, no further bookings for that series will be synchronized into RMS. It is recommended that recurring appointments either have a specific end date or a number of occurrences defined.
  • Changing the attendees of an existing meeting doesn't actually modify the meeting in Exchange. This is simply how Exchange behaves. As a result, the meeting will not be resynchronized to RMS and the attendee changes won't be reflected in RMS. Something such as the subject, body, or date/time must be changed in order for a synchronization to RMS to occur.
  • Ending or extending a meeting from the touch panel will only update the resource's calendar. The meeting time will not be adjusted on the calendars for the organizer and attendees.
  • The RMS Exchange Appointment Organizational Form is not compatible with this plug-in.


ZIP | 2.24 MB | v. 4.1.5 | 2013-09-13
RMS-SCH-EWS
RMS Enterprise Interface for Lotus Notes Domino

Prerequisites

  • RMS Enterprise Server version 4.1.10 or later.
  • RMS Enterprise Scheduling Interface version 4.1.19 or later.
  • Lotus Notes 8.5.3 FP4.

Changes in this release

  • Initial implementation of appointment synchronization between Lotus Notes 8.5.3 FP4 and RMS Enterprise.

Known Issues

  • By default, the reservation documents from Lotus Domino Resource database do not have attendees and detail message properties, therefore RMS is not able to display attendees/details for an appointment.
  • It is highly recommended that the RMS Troller window service and IBM Lotus Domino server are running on the same time zone to avoid the potential date time format issues.
  • If the Lotus Notes client is open and running while the RMS Lotus Notes plug-in attempts to communicate with the Domino server, this can sometimes cause the Lotus Notes communication to stop. Sometimes this message is displayed: "This database is currently in use by another person or process, and cannot be accessed at this time." It is recommended that the Lotus Notes client software is not running at the same time the "RMS Enterprise Legacy Troller" Windows service is running.
  • In some cases you may receive the following error when connecting to the Notes server using the RMS Configuration Wizard and/or during a synchronization cycle: "Notes error: Could not open the ID file." If this happens, the "RMS Enterprise Legacy Troller" Windows service must be configured to log on with a Windows account that has the notes.ini and user.id files in its application directory.
  • Adhoc meeting that is added/modified/ended through Resource Reservations may not be updated on the User's Calendar due to the limitation of Lotus Notes Client.

ZIP | 3.35 MB | v. 4.1.5 | 2013-09-13
RMS-SCH-LN
Novara RMS 3.3
  • Device Interrogation (ability to monitor device status in RMS) now supported.
  • Adds "enabletelnet=1 or 0" to config.properties.

NOTE: If you are upgrading from the initial version of Novara RMS (1.0.38), you must save a copy of your existing config.properties file as the initial version did not preserve the file. Starting with 1.0.54, the installer will no longer overwrite config.properties for future upgrades.

Known Issues:

Any change of a Novara 3000 series controller's "RMS Peer Group" or "Device Name" requires restarting the RMS proxy application.

If the IP address of a keypad that was previously connected to the RMS proxy is changed the RMS proxy application must be restarted.

If a controller is added in RMS and the "device name" is changed on the keypad to display updated information regarding the "device name" the room should be deleted and re-added in RMS.

Multi-language support has passed limited testing. English has been thoroughly tested.

Multi-platform support has passed limited testing.

Please see the manual for specific information about the languages and platforms that have been tested with the RMS proxy.

Hot Fix for the Novara RMS 3.3 Application (v.1.0.71 Available from AMX Technical Support)

Changes in this release:

  • Added Source Usage and System Power tracking based on button feedback (LED) state.
  • Buttons with names starting with 'Select' including custom name buttons will be added to the source usage tracking list in RMS. Usage is tracked in whole minutes.
  • Buttons with 'Power On' & 'Power Off' will track as System Power in RMS.
  • Removed unneeded debug messages and improved others.
  • Resolved issue with scheduled events and execute function where button #1 wouldn't be executed.
  • Resolved an issue where custom button names weren't getting sent to RMS.
  • New Windows Service wrapper. CP-RMS now comes with its own JVM independent of Java version installed on Windows. Resolves issues of 32/64bit JVM compatibility.
  • Improved communication with RMS in the case where a room has no appointments RMS send no reply.
  • This was causing the communication maintenance cycle to think that the connection to RMS was dead, triggering unnecessary offline/online events.
  • Fixed Msg On/Off command not working every time.
  • Improved communications compatibility with RMS 3.
  • Updated communications for RMS 4.
  • Fixed issue where communications with RMS and Keypads would be interrupted just after midnight.
  • Fixed issue where communications with RMS and Keypads would degrade over time requiring a service restart to recover.
  • All IP communication is now Async eliminating locks and slow down under certain conditions.
  • Fixed issue where scheduled macros didn't fire.
  • Removed limitation of 255 keypads in config file. It's now 999.

ZIP | 949 KB | v. 1.0.54 | 2011-1-5
CP-3006
CP-3008
CP-3017-NA
CP-3017-TR-US
NovaraRMS
RMS 3.3 Server

Note: External Scheduling Interfaces were removed from the installer. All scheduling plug-ins must be ordered from AMX and installed along with RMS version 3.3 or greater. For more information please visit the AMX Enterprise applications product page at: www.amx.com/products/categoryEnterpriseTools.asp.

New Features:

  • Added support for RMS Interface for Exchange/Outlook Organizational Form
  • Added user modifiable time zones
  • Added auto refresh feature on System Status and View Device pages
  • Added limited support for multiple bulb projectors
  • Added new RMS IT, Database, and FAQ documentation
  • Updated RMS Configuration Wizard
  • Removed External Scheduling Plug-ins from RMS Server installation
  • Created separate External Scheduling Plug-in installation packages for Exchange, Lotus Notes, GroupWise, Planon, R25, EMS, and PeopleCube
  • For a full listing of bug fixes, please refer to the README.HTM file


EXE | 39.7 MB | v. 3.3.85 | 2009-08-17
ClassroomManager
ExhibitManager
HomeManager
IntelligentManager
MeetingManager
VenueManager
WorshipManager
RMS 3.3 Software Development Kit

New Features:

  • Added - RMSEngine command to change TELNET or HTTP default ports
  • Added - support in RMSProjectorMod to listen for Duet LAMPTIME feedback command
  • Added - support in RMSModuleBase to listen for Duet channel DATA_INITIALIZED (ch 252) for device communicating parameter status
  • Added - support in RMSTransportMod to listen for Duet device transport feedback
  • Added - support for NI-3101-SIG


EXE | 5.75 MB | v. 3.3.33 | 2009-08-17
ClassroomManager
ExhibitManager
HomeManager
IntelligentManager
MeetingManager
VenueManager
WorshipManager
RMS 3.3 CodeCrafter

Note: This version of RMS CodeCrafter (v3.2 Build 22) requires RMS SDK v3.3.33 or later.

New Features:

  • Updated application to work with Windows Vista operating system


EXE | 6.94 MB | v. 3.2.22 | 2009-08-17
RMS CodeCrafter
RMS 3.3 Interface for Microsoft Exchange Web Services (EWS) (Available by Order)

Requirements:

  • RMS Server version 3.3 or later
  • Microsoft Exchange 2007 with Service Pack 1 or greater installed
  • Microsoft Exchange 2010
  • Microsoft Exchange 2010 SP1

New with this release:

  • Numerous updates to the plugin and configuration user-interface
  • Fixed performance problems
  • Added support for certificate-mapped authentication
  • Fixed authentication issue that allowed IIS servers to ignore the user-configured domain name

Known Anomalies:

  1. Each meeting instance in an Exchange recurring meeting series is treated as an individual meeting in RMS
  2. The recurring checkbox on the "Edit Appointment" page (displayed when double-clicking on a meeting displayed on the RMS Room Schedule Page) will not be checked even if the meeting is an instance of a recurring series
  3. Welcome text, macros, and images associated with an instance in a recurring series will not be propagated to the other meeting instances in the series
  4. Any meeting deleted from a room's schedule page is only removed from the RMS database and not propagated back to the Exchange server and will reappear after the next troll cycle. This behavior is normal - the delete option should not be available and will be removed in a future version of RMS.
  5. If the creator of a meeting changes the start or end time in Outlook Exchange will create a new meeting with a different unique ID. This will cause RMS meetings to lose welcome text, welcome images, and macros. This is a Microsoft issue, not an RMS bug.
  6. The RMS Exchange Appointment Organizational Form is not compatible with this plugin

Available by Order | v. 3.3.13 | 2013-08-23
NSS-RMS-EWS
RMS 3.3 Interface for Lotus Notes (Available by Order)
All RMS scheduling plug-ins must be ordered from AMX and installed along with RMS version 3.3 or greater. For more information please visit www.amx.com/rms.
Available by Order | v. 3.3.1 | 2009-10-01
NSS-RMS-LN
RMS 3.3 Interface for PeopleCube Resource Scheduler (Available by Order)

All RMS scheduling plug-ins must be ordered from AMX and installed along with RMS version 3.3 or greater. For more information please visit www.amx.com/rms.

  • Requirements
    • RMS Server version 3.3 or later.
    • PeopleCube Resource Scheduler version 8.5 SP2 or later.
  • Features
    • Initial release of RMS Resource Scheduler Plug-in.
    • Supports event synchronization between PeopleCube Resource Scheduler and AMX RMS.
    • Supports events added, extended, and ended by users from a RMS touch panel.
  • Known Issues
    • Recurring event instances in Resource Scheduler are handled as individual appointment reservations in RMS.


Available by Order | v. 3.3.1 | 2009-10-23
NSS-RMS-PPC
RMS 3.3 Interface for EMS (Available by Order)
All RMS scheduling plug-ins must be ordered from AMX and installed along with RMS version 3.3 or greater. For more information please visit www.amx.com/rms.
Available by Order | 2009-10-01
NSS-RMS-EMS
RMS 3.3 Interface for Planon (Available by Order)

All RMS scheduling plug-ins must be ordered from AMX and installed along with RMS version 3.3 or greater. For more information please visit www.amx.com/rms.

  • Requirements
    • RMS Server version 3.3 or later.
    • The Planon software needs to be version FO-SE 4.33 matchcode h.
  • Features
    • Fixed the bug that causing the Plugin to generate duplicate appointments in RMS during trolling cycles.
  • Known Issues
    • Recurring event instances in Resource Scheduler are handled as individual appointment reservations in RMS.


Available by Order | v. 1.0.3 | 2009-10-23
NSS-RMS-PLAN
RMS 3.3 Interface for Novell GroupWise (Available by Order)

All RMS scheduling plug-ins must be ordered from AMX and installed along with RMS version 3.3 or greater. For more information please visit www.amx.com/rms.

  • Requirements
    • RMS Server version 3.3 or later.
    • NovellGroupWise 5 or greater.


Available by Order | v. 3.3.1 | 2009-10-23
NSS-RMS-GW
RMS 3.3 Interface for CollegeNet R25 (Available by Order)

All RMS scheduling plug-ins must be ordered from AMX and installed along with RMS version 3.3 or greater. For more information please visit www.amx.com/rms.

  • Requirements
    • RMS Server version 3.3 or later.
    • CollegeNET API version 1.8 or later.
  • Features
    • Initial Release
  • Known Issues
    • Recurring event instances in R25 are handled as individual appointment reservations in RMS.
    • RMS does not obtain the organizer email address from R25 events and thus cannot deliver email notifications to the R25 event organizer.
    • When events reservations are modified in R25, R25 internally creates new reservation booking records with new events reservation identifiers, thus RMS detects these as new event reservations and then deletes the previous event reservation from the RMS database. Consequently, this also deletes any RMS associated data configured on the previous event reservation record.
    • Reservations that are Ended or Extended from the RMS touch panel are handled as modified R25 events and thus exhibits the same behavior as outline in #3 above.
    • R25 does not support modifying start and end times on individual recurring event instances, thus RMS cannot extend or end recurring event instances.
    • R25 does not support modifying start and end times on event that contain multiple reservations, thus RMS cannot extend or end multiple reservation event instances.


Available by Order | v. 3.3.6 | 2009-10-23
NSS-RMS-R25
Feedback | Gear Store | Site Map | Terms & Conditions | Warranty