Why the imported AD user with Administrator privilege behaves as Non-Administrator User?

Why the imported AD user with Administrator privilege behaves as Non-Administrator User?


      In Applications Manager,  domain settings must have User permission as  "Full Control" in order to import users as Administrator. 
Domain Settings

                    New to ADSelfService Plus?

                      • Related Articles

                      • Permissions required for Non-Admin user to monitor Microsoft Monitors

                        1) To enable WMI permissions for the non admin account follow the steps mentioned in the below link. https://pitstop.manageengine.com/portal/en/kb/articles/configuring-non-admin-user-account-for-wmi-monitoring As an alternative to Steps 1-6 in the ...
                      • User Privilege for DamengDB Monitoring

                        To effectively monitor DamengDB in Applications Manager, the Monitor user must be granted the Data Viewer privilege. To grant this privilege to the newly created user, please follow the steps given below: Connect to your DamengDB instance using a ...
                      • Steps to verify WMI access for Non-Admin Domain user

                        This guide provides how to enable and test WMI access with a regular domain user without generic admin rights. Make sure you have followed the steps in the article Setting WMI access through Active Directory & Group Policy Object. This ensures you ...
                      • Configuring non-admin user account for WMI monitoring

                        QUESTION: How to set up WMI monitoring without domain admin or local admin credentials RESOLUTION: Windows will only allow members of the Administrators or Domain Admin groups to read WMI class information by default. However, you can configure a ...
                      • Setting WMI access through Active Directory and Group Policy Object for non-admin user

                        In our case, we run Active Directory on Windows 2008 R2 and we want to scan the target machine which is Windows 2012 R2 machine. Our domain is called “APMCLU” and we name our dedicated WMI user-account “wmiuser”. First – Setting done from Active ...