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

  • Fixed a bug with the database update scripts that was causing the RMS server upgrade to fail.


ZIP | 229 MB | v. 4.3.13 | 2014-07-09
RMS-ENT
RMS-ENT-SCH
RMS-ENT-SMA
RMS Enterprise Software Development Kit

Prerequisites

  • RMS Server version 4.3 or greater

Changes in this release

  • Reduced amount of disk space required at runtime
  • Added support for G5 touch panels
  • Added G5 touch panel file with new look and feel
  • Improved touch panel performance
  • Updated API to allow a default event booking duration to be specified
  • The keyboard is automatically displayed when creating a meeting on a G5 touch panel. Updated API to allow this feature to be disabled
  • Updated RmsTouchPanelMonitor.axs to support G5 touch panels


ZIP | 34.62 MB | v. 4.3.12 | 2014-08-07
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.3 or later. This release of the Scheduling Interface requires some new web service APIs on the RMS Server.

Changes in this release

  • Implemented support for certificate-based client authentication and more robust validation of server-side certificate for HTTPS / SSL when using the Exchange EWS Scheduling plug-in.
  • Implemented support for trolling time delay settings via UI.


ZIP | 1.36 MB | v. 4.1.22 | 2014-07-09
RMS-ENT
RMS-ENT-SCH
RMS-ENT-SMA
RMS Enterprise Interface for Microsoft Exchange Web Services (EWS)

Prerequisites:

  • RMS Enterprise Server version 4.3 or later.
  • RMS Enterprise Scheduling Interface version 4.1.22 or later.
  • Microsoft Exchange 2010 SP3.
  • Microsoft Exchange 2013 SP1.
  • Microsoft Office 365.

Changes in this release:

  • Implemented support for certificate-based client authentication and more robust validation of server-side certificate for HTTPS / SSL.
  • Implemented support for Microsoft Exchange 2013 SP1 and Microsoft Office 365.
  • Implemented support for trolling time settings via UI.


ZIP | 2.25 MB | v. 4.1.9 | 2014-07-09
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/resourcemanagementsuite.
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/resourcemanagementsuite.

  • 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/resourcemanagementsuite.
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/resourcemanagementsuite.

  • 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/resourcemanagementsuite.

  • 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/resourcemanagementsuite.

  • 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 of Use | Privacy Policy | Warranty