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.
When logging to Access Management System (AMS), Visitor Management receive an error “Access Denied”.
One possible cause is the user missing a “User profile”, or the User Profile doesn’t have execute rights for Visitor Management.
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.
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.
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.
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
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.
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 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
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
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.
An HTTP 500 error is an Internal Server Error. The root cause of the issue in this case is that there is not enough space left in the AEMC storage.
There is a setting in the AEMC/Allplex system to overcome the insufficient space problem. The user will have to configure the following setting in the server setup --> housekeeping section. You will need to define the number of days to keep the database. The default value is unlimited.
Log into the AEMC/Allplex and select "Server setup" from the options on the left.
Then select "Housekeeping" from the options on the top.
Housekeeping allows the user to manage the Activity Log and Audit Log in the system. User can delete the unwanted logs that are no longer required manually as well as to specify the number of days of the logs to be kept in the system and the system will store the logs of only the most recent specified number of days in the system.
How to Use the Auto Housekeep?
Choose the number of days of both the Activity Log and Audit Log to be kept in the system.
User are given a choice of 30, 60, 90 and 120 days. For example, if user chooses 30 days, the system will automatically delete the Activity and Audit Logs from the system if they are more than 30 days from today's date. User can also choose unlimited, which means the system will not delete the logs from the system.
2. Click on the floppy disk button to save the settings.
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