{"id":1079,"date":"2011-06-21T13:46:12","date_gmt":"2011-06-21T05:46:12","guid":{"rendered":"http:\/\/www.sharepointboost.com\/blog\/?p=1079"},"modified":"2023-07-31T11:40:58","modified_gmt":"2023-07-31T03:40:58","slug":"sharepoint-ad-administration-delegating-authority-to-selected-users","status":"publish","type":"post","link":"https:\/\/www.boostsolutions.com\/blog\/sharepoint-ad-administration-delegating-authority-to-selected-users\/","title":{"rendered":"Sharepoint AD Administration, delegating authority to selected users"},"content":{"rendered":"

Decrease workload by delegating tasks evenly to responsible managers. Sharepoint AD Administration<\/a><\/strong> provides system administrator authority but with limited abilities to create, edit, rename, <\/strong>and\/or delete <\/strong>OUs and AD properties. Assigned individuals also have the capability to reset passwords, create and manage users and groups, and edit AD progiles from within a predefined OU.<\/p>\n

Most companies have a password policy, and it is usually scheduled every 60 days for password change. The new password change should be different, not to mention the complexity it requires.<\/p>\n

Usual password change flow looks like this, in 4 steps:<\/p>\n

\"\"<\/a><\/p>\n

And on some times, some employees forget the current password as even 60 days sounds like a long time, in fact it’s quite often for a password change. So on some instances, password change would be in a rush that they actually forget which password is used for the change.<\/p>\n

With Sharepoint AD Administration: <\/strong><\/p>\n