Folders and Roles are used to control what devices AWMS Users can access. Certain conditions may arise causing a conflict between the Folder hierarchy and internal AWMS rules. Among them are the following:
- An AWMS User has access to some of the APs in a Group but not to all of them
- Two unique Folder IDs exist with the same Folder path
Access to some, but not all APs in a Group
If an AWMS User has access to one AP in a given Group, that User must have access to ALL of the APs in that Group. Imagine an AMP with just 2 APs, both in Group1, and with a Folder hierarchy that looks like this:
-Top (Contains AP1)
----Building1 (Contains AP2)
You cannot create a User Role whose top level access is set to the Building1 Folder. Doing so would give a User with that Role access to AP2, but not to AP1, both of which are in Group1.
The solution to this problem depends on which of the APs, if any, you want the User to have access to. Possible solutions include:
- put both APs in the same Group
- move AP1 into the Building1 Folder
- move AP2 to some other Folder
- create another Folder at the same level or below Building1 and make that the top level Folder for the Role
In a nutshell, what you need to look for are Roles that give a User access to some APs in a Group but not to all of them.
Two unique Folder IDs with the same Folder path
Sometimes when Folders are created using a script, more than one ID may exist with the same Folder path. You can find instances of these by running the following query from the AMP command line:
# dbc 'select id, name from ap_folder where path in (select path from ap_folder group by path having (count (path) > 1))'
If the above command returns duplicate Folder names, run the query below and send the output from both queries to Customer Support:
# dbc 'select count(*) from ap where ap_folder_id in (select id from ap_folder where path in (select path from ap_folder group by path having (count (path) > 1)))'