Поиск часто задаваемых вопросов
Video: Data Center Expert | How do I configure Active Directory Authentication?
Adding an Active Directory Server and Users/Groups
1) Define a user within your Active Directory (AD) server that will be used to make the connection between Data Center Expert (DCE) and your AD server.
2) Within the DCE client, go to: System menu > Users and Device Group Access.
3) Select the Authentication Servers tab.
4) Select Add Authentication Server...
- Enter the IP address of your AD server.
- Under Server Type, select Active Directory.
- Select Next.
5) For the Bind User DN, you will need to enter the path to the AD server user location in a specific format. Details on syntax can be found in Data Center Expert | Tips for configuring Active Directory integration .
- You may need to contact your AD server administrator to acquire the information.
6) Enter the password for the Bind user that has been defined within the AD server.
7) Enter the search base of where the groups and users are located in AD. Select Next.
8) Check the boxes for the users and user groups. Select Finish.
Adding/Removing Users and User Groups to an Existing Authentication Server Connection
1) Within the DCE Client, go to: System menu > Users and Device Group Access > Authentication Servers tab.
2) Select the main Authentication server and then select Edit Authentication server.
3) Select Next twice and then select the additional users and user groups you would like to provide access to DCE.
4) To remove a user or user group uncheck the associated box. Select Finish.
For configuring users or user groups, see knowledge base Video: Data Center Expert | How do I configure Active Directory Authentication? .
Note: DCIM support can only verify the protocols work with the software, and are unable to assist with organization configuration strings/settings. It is expected the end user understand the methodologies and nuances of the connection protocol within their network. Schneider Electric can only provide information stating the protocol has been verified and tested using Active Directory and OpenLDAP without issue.