Security: Access Control

This article describes how can you check the status of your Software Maintenance Agreement (SMA) for Access Management System (AMS). This article applies when: - You want to check if you still have a valid SMA to see if you are still eligible to get support via the Bosch Central Support team - You want to check if you need to extend the Bosch Assurance Agreement for Access Management System (AMS) for yourself or your customer

This article explains the integration of B/G intrusion panels in AMS.   The integration of B/G intrusion panels AMS requires the installation of the intrusion RPS API version V2.1.25920 or later only applies to AMS 3.01 version of AMS and for version 3.0 the API version is V2.1.25454, also the earlier AMS 3.0 version RPS cannot be installed on the same PC. For small installations it is possible to install AMS and RPS on the same computer, with the following prerequisites: • AMS has never been installed on that computer • SQL Server database has never been installed on that computer • You install RPS before AMS The RPS API must be installed on the same computer as the RPS tool. The RPS tool is needed to configure and manage the communication with the B/G panels. The RPS API conveys communications from AMS to the RPS tool, which then communicates with the panels. SDK communication to the B/G panels is integrated in AMS. No separate installation is required, but Mode2 and a Automation Pass-code must be enabled on the panel   Step-by-step guide   1. Install the RPS API on the RPS Computer 2. Make sure that these processes are running on the RPS PC 3. Set the Automation Device and change the default password. While you are in RPS, also set the date and time of the intrusion panel. After you finished the work in RPS, load the configuration to the panel and disconnect the RPS from it. 4. AMS > Configuration > Panels > RPS API configuration menu Set-up the connection parameters to connect AMS to RPS API "rpspc" is the name of the PC on which RPS and RPS API are running User name to login to RPS - Default: Admin Password to login to RPS - Default: 1111 Press to test the connection Test is successful: 5. AMS > Configuration > Panels > Panel administration menu Define: To which division of AMS the intrusion panel shall belong to Whether you want the panel users managed from AMS (Under administration) Whether you want the panel to be the part of MapView The access data to the panel 6. AMS > Configuration > Panels > Panel administration menu Define the access data to the panel Use the password you defined in RPS for the Automation Mode 2 Device connection 7. AMS > System data > Authorization profiles for panels menu: Create authorization profiles and assign area(s) of panel(s) to it. Define to which user group of the intrusion panel will be this Authorization profile assigned 8. AMS > Personnel data > Card menu, Intrusion tab: If the selected Cardholder is planned to be a Intrusion panel user as well, then select the checkbox and define the necessary data. Only the Pass-code the Language are mandatory, the rest can be left blank 9. It is manddatory that the date and time settings are properly set at the intrusion panel and synchronized with AMS Server 10. Until the RPS is connected to the intrusion panel, AMS cannot synchroniza with the panel.

Disclaimer: this guide is intended for Windows advanced users. Knowledge on Windows registry and batch files is highly recommended. If you don’t have knowledge on modifying the Windows registry, do not continue as any mistake can damage the operating system.   Step-by-step guide   This document consists of three parts: Import or create a certificate to the RPS computer Enable Https and configure the certificate binding Import the certificate into AMS server  

Very often, it is easier to troubleshoot most AMS problems when logging is enabled. By default, this option is disabled in AMS. These steps will detail how to enable logging for AMS. Step-by-step guide  Log into the AMS server or client with administrative privileges 2     Click on the “Configuration” option\ 3     Next select the “Options” selection 4     Select the “Debug logfiles” option 5     Now check the “DMS, Terminal and MAC name” under the (Technicians) column. Leave the options under the (Support) column Unchecked unless specifically directed to. 6     In order for the logs to be available, the AMS server PC will need to be rebooted 7     After the AMS server is rebooted, reproduce the issue and it should now be listed in the log files for engineering to evaluate.    The log files are typically located in the C:\ProgramData\Bosch\Sicherheitssysteme\Access Management System\Logs

This article steps through the process of enabling the "pin or card" function in Access Professional Edition

This article could be useful if getting a login error in AMS Map View v5 in a Domain environment.

This article describes the use of the AECT utility within the AMS installation folder, that will check your PC specs to see if AMS can be installed. This is only a "guide" as to the recommended specs for installing AMS.

This article contains how-to series about data migration from Access Professional Edition (APE) to Access Management System (AMS).

This article will guide users on the process of adding a reader extension board to an AMC controller in AMS.

  When logging to Access Management System (AMS), Visitor Management receive an error “Access Denied”.   Cause One possible cause is the user missing a “User profile”, or the User Profile doesn’t have execute rights for Visitor Management.   Solution One possible solution would be the following: Verify the user has a User Profile assigned. In AMS go to Configuration -> Operators and Workstations –> User rights Go to User Profiles, make sure to assign a profile if there is none.   Verify the Profile has execute rights for Visitor Management. Go to User Profiles, make sure the user profile assigned has provisioned the execution rights for Visitor Management. This rights may vary according to the user.   Note: The user and password to log in to Visitor Management are set under the “User account” tab.  

Causes One thing that can cause the Identity Server error is the "certificates" not being updated during the installation process. This error can happen on the server or the client.   Solution For a possible resolution to the issue, follow the steps below: On the AMS server navigate to C:\Program Files (x86)\Bosch Sicherheitssysteme\Access Management System\Certificates folder. Right click on the AccessCertificateTool.exe and select "run as administrator".  The following should come up:   Click in the output folder section and another window should come up with "save as" option. Leave everything default and select the save option: Next select the "Generate" option. When it is completed you should see a screen similar to the one below. Select restart and then test visitor management on the server and/or the client again.

This article may be useful if migrating an Access Professional database to an AMS system

This article explains in a step by step guide how can you setup pincodes to work in AMS 4.0

This article could be useful for you in case of AMS_RPS integration issues

When adding doors in AMS, the software will by default, assign each door strike relay based on the first available unused output on the controller.

This article can help with adding maps to a Security Escort system.

This article may be useful for individuals that have a problem applying licenses in AMS 5

When attempting to run the AECT utility to check PC specs, there may occur a situation where it doesn't run at all when selecting run as administrator or just double clicking on it to open it. Typically nothing will appear or possibly a text file may appear like the one in the screenshot from this article.

When upgrading from a version 2.xx escort to a version 3.xx, one of the steps is to backup and restore a transponder.xml file.

This article contains the part numbers for the Security Escort licenses