Solved

Changes to user security settings will stick

Posted on 2007-03-22
3
833 Views
Last Modified: 2013-12-04
I have just setup BlackBerry Enterprise server on a Windows SBS 2003 domain controller.  When setting up the Blackberry software, I had to add a new user to the domain (BESadmin) in order to properly setup the software.  For the Blackberry software to work, I have to give the user BESadmin "Send As" permissions for the entire domain.

Problem:  While I am able to properly add the BESadmin to the entire domain and to the organizational unit, I cannot do the same for the individual user account.  There is only one user who I need the BESadmin to have Send As permission for, but their account is set to not inherit permissions, and when I make any changes to their security settings they seem to apply fine but are later removed when I check back in.  Since the Blackberry software tells you to wait 20 minutes before restarting their software, I wait each time I have changed the users security settings and go back for a final check and they have always changed back.

What can I do to get my changes to stick??
0
Comment
Question by:doulos777
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 10

Accepted Solution

by:
abraham808 earned 500 total points
ID: 18773323
Make sure they are not a Domain Admin or Account Operators or any one of the protected accounts:
http://support.microsoft.com/kb/817433

Method 2: Enable inheritance on the adminSDHolder container
If you enable inheritance on the adminSDHolder container, all members of the protected groups have inherited permissions enabled. In terms of security functionality, this method reverts the behavior of the adminSDHolder container back to the pre-Service Pack 4 functionality.
Enabling inheritance on the adminSDHolder container
If you enable inheritance on the adminSDHolder container, one of the two protective access control list (ACL) mechanisms is disabled. The default permissions are applied. However, all members of protected groups inherit permissions from the organizational unit and any parent organizational units if inheritance is enabled at the organizational unit level.

To provide inheritance protection for administrative users, move all administrative users (and other users who require inheritance protection) to their own organizational unit. At the organizational unit level, remove inheritance and then set the permissions to match the current ACLs on the adminSDHolder container. Because the permissions on the adminSDHolder container may vary (for example, Microsoft Exchange Server adds some permissions or the permissions may have been modified), review a member of a protected group for the current permissions on the adminSDHolder container. Be aware that the user interface (UI) does not display all permissions on the adminSDHolder container. Use DSacls to view all permissions on the adminSDHolder container.

You can enable inheritance on the adminSDHolder container by using ADSI Edit or Active Directory Users and Computers. The path of the adminSDHolder container is CN=adminSDHolder,CN=System,DC=<MyDomain>,DC=<Com>

Note If you use Active Directory Users and Computers, make sure that Advanced Features is selected on the View menu.

To enable inheritance on the adminSDHolder container: 1. Right-click the container, and then click Properties.
2. Click the Security tab.  
3. Click Advanced.  
4. Click to select the Allow Inheritable permissions to propagate to this object and all child objects check box .
5. Click OK, and then click Close.  
The next time that the SDProp thread runs, the inheritance flag is set on all members of protected groups. This procedure may take up to 60 minutes. Allow sufficient time for this change to replicate from the primary domain controller (PDC).

0
 

Author Comment

by:doulos777
ID: 18773527
The user was setup (by previous IT staff) as a domain admin.  I have removed that setting and re-applied the needed security.  I will let you know how things turn out.
0
 

Author Comment

by:doulos777
ID: 18775878
WORKED GREAT!!

The user was also a Domain Admin.  Once I removed that setting, they were able to get and keep new permissions.
0

Featured Post

The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I’m often asked about newer and larger USB drives connected to SBS2008 and 2011 failing Windows Server Backup vs the older USB drives not failing. As disk space continues to grow and drive technology change SBS2008 and some SBS2011 end up with the f…
Security measures require Windows be logged in using Standard User login (not Administrator).  Yet, sometimes an application has to be run “As Administrator” from a Standard User login.  This paper describes how to create a shortcut icon to launch a…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question