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 scheduling support
• Fixed a bug with Directory Support configuration where the "group base" wasn't using the correct property and authentication would fail querying the directory for a user's group membership
• Fixed a bug that prevented a database migration from 3.3 from working
• Fixed a bug that prevented the RMS server from starting successfully in environments where network access to the internet is blocked
• Corrected the Asset Inventory report so that asset metadata is included in the report instead of erroneously including location metadata
• Fixed a bug where a non-monitored asset (i.e. an asset created from within the UI) that was not assigned a model, when edited, would generate an error because the logic was assuming an associated model

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
• 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

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

Prerequisites

• Supported panel must have a minimum of 128 MB RAM
• NI-2100 (firmware v3.41.422 or greater)
• NI-3100 (firmware v3.41.422 or greater)
• NI-3101-SIG (firmware v3.41.422 or greater)
• NI-4100 (firmware v3.41.422 or greater)
• DVX-2100HD (firmware v3.51.339 or greater)
• AMXmeetingroom requires an outside internet connection and access to www.amx.com in order to activate the license key and to download the AMXmeetingroom compatible Duet modules for the AV devices in the meeting room
• The NetLinx panel and master should be connected such that they can communicate together
• Panel - The touch panel must be set to device ID 10001
• NI Controller - The NetLinx controller must be set to device ID 5001
• The system number of the master may be set as desired
• Both the panel file and token file must be the same revision and build

Revision Changes
AMXmeetingroom v1.0.3.20420 has been modified with the following features:

• Added features for DVX firmware v 4.1.355 and greater
• Added ability to select dual mono mode or single stereo mode for microphone inputs when using DVX
• Enhanced valid signal notifications when using DVX
• Fixed IR channel mapping
• Fixed Lighting presets losing names
• Fixed Lighting configuration for Dynalite
• Fixed Camera Preset labels
• Fixed signal routing to VTC

Known Issues

• Some baud rates are not supported by certain Duet modules
• Some device Duet modules return blank as default baud rate, AMXmeetingroom will return 'Default'
• Attempting to change control method for IP only devices may affect control or feedback of the device
• When using a DVX, enhancements to this version of software are best utilized with DVX firmware v 3.53.316 or greater
• I/O and relay functions may not always display in the text field
• Once Camera 1 controlled through VTC is selected, it is currently not possible to change the control for Camera 1
• Camera 2 custom IR buttons cannot be removed once populated

Maintenance release addresses several cosmetic issues. This release also includes v2.1.16 fixes and features.

Please see release notes for more information.

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

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

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

Features:

• Changed all "Exchange2010" nomenclature to "ExchangeEWS"
• Changed the RMS room management page to allow manual entry of room mailboxes in addition to selecting from Exchange Distribution Lists
• Fixed time zone issues
• Updated documentation to reflect Exchange 2007 support
• Added time zone support required by Exchange 2007
• Added support for Exchange 2007
• Added support for full-access permissions and delegation. Impersonation is still supported, but no longer required

Known Anomalies - This section contains the identified issues that this version is shipping of the product contains...

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

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
• Microsoft Exchange 2003/2007 SP2 or greater

Features

• v3.3.4 Release
• Change to configuration dialog to allow resource selection.
• Updated the RMS Exchange Organizational Form to filter macro events when the room resource is selected or changed.
• Bundled a new AMXMAPI.DLL library that allows for long Exchange mailbox names.
• v3.3.2 Release
• change to exchange resource resolution to fix Outlook 2003 issue with Location
• v3.3.1 Release
• fixed issues with MAPI Entry ID not staying constant throughout appointment lifetime

Known Anomalies

• The SP2 change to Microsoft Exchange no longer guarantees that the old MAPI Entry ID will stay the same if something in the appointment changes (in particular details, but may be other fields). This can potentially cause the same appointment to be added with a new key and deleting the old one in RMS. This would appear transparent except for the loss of the appointments Scheduled Macros, Welcome Image and Welcome Text. Microsoft added Global ObjectID to the MAPI interface which is guaranteed to remain the same for all copies of the appointment. RMS will now use that ID for identifying the Exchange appointment.

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.

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.