Distribution groups can be used only with email applications such as Exchange Server to send email to collections of users. Distribution groups are not security enabled, which means that they cannot be listed in discretionary access control lists DACLs. Security groups can provide an efficient way to assign access to resources on your network.
By using security groups, you can:. User rights are assigned to a security group to determine what members of that group can do within the scope of a domain or forest. For example, a user who is added to the Backup Operators group in Active Directory has the ability to back up and restore files and directories that are located on each domain controller in the domain.
This is possible because, by default, the user rights Backup files and directories and Restore files and directories are automatically assigned to the Backup Operators group.
Therefore, members of this group inherit the user rights that are assigned to that group. You can use Group Policy to assign user rights to security groups to delegate specific tasks.
Permissions are different than user rights. Permissions are assigned to the security group for the shared resource. Permissions determine who can access the resource and the level of access, such as Full Control. Some permissions that are set on domain objects are automatically assigned to allow various levels of access to default security groups, such as the Account Operators group or the Domain Admins group. Security groups are listed in DACLs that define permissions on resources and objects.
When assigning permissions for resources file shares, printers, and so on , administrators should assign those permissions to a security group rather than to individual users. The permissions are assigned once to the group, instead of several times to each individual user. Each account that is added to a group receives the rights that are assigned to that group in Active Directory, and the user receives the permissions that are defined for that group.
Like distribution groups, security groups can be used as an email entity. Sending an email message to the group sends the message to all the members of the group. Groups are characterized by a scope that identifies the extent to which the group is applied in the domain tree or forest. The scope of the group defines where the group can be granted permissions.
The following three group scopes are defined by Active Directory:. In addition to these three scopes, the default groups in the Builtin container have a group scope of Builtin Local. This group scope and group type cannot be changed. The following table lists the three group scopes and more information about each scope for a security group. Local groups on computers in the same domain, excluding built-in groups that have well-known SIDs. Special identities are generally referred to as groups.
Special identity groups do not have specific memberships that can be modified, but they can represent different users at different times, depending on the circumstances. For information about all the special identity groups, see Special Identities. Default groups, such as the Domain Admins group, are security groups that are created automatically when you create an Active Directory domain. You can use these predefined groups to help control access to shared resources and to delegate specific domain-wide administrative roles.
Many default groups are automatically assigned a set of user rights that authorize members of the group to perform specific actions in a domain, such as logging on to a local system or backing up files and folders. For example, a member of the Backup Operators group has the right to perform backup operations for all domain controllers in the domain.
When you add a user to a group, the user receives all the user rights that are assigned to the group and all the permissions that are assigned to the group for any shared resources. Default groups are located in the Builtin container and in the Users container in Active Directory Users and Computers. The Builtin container includes groups that are defined with the Domain Local scope. The Users includes contains groups that are defined with Global scope and groups that are defined with Domain Local scope.
You can move groups that are located in these containers to other groups or organizational units OU within the domain, but you cannot move them to other domains. Some of the administrative groups that are listed in this topic and all members of these groups are protected by a background process that periodically checks for and applies a specific security descriptor.
This descriptor is a data structure that contains security information associated with a protected object. This process ensures that any successful unauthorized attempt to modify the security descriptor on one of the administrative accounts or groups will be overwritten with the protected settings.
The security descriptor is present on the AdminSDHolder object. This means that if you want to modify the permissions on one of the service administrator groups or on any of its member accounts, you must modify the security descriptor on the AdminSDHolder object so that it will be applied consistently. Be careful when you make these modifications because you are also changing the default settings that will be applied to all of your protected administrative accounts. The following tables provide descriptions of the default groups that are located in the Builtin and Users containers in each operating system.
Members of this group can remotely query authorization attributes and permissions for resources on the computer. The Access Control Assistance Operators group applies to versions of the Windows Server operating system listed in the Active Directory default security groups by operating system version. The Account Operators group grants limited account creation privileges to a user. Members of this group can create and modify most types of accounts, including those of users, local groups, and global groups, and members can log in locally to domain controllers.
Members of the Account Operators group cannot manage the Administrator user account, the user accounts of administrators, or the Administrators , Server Operators , Account Operators , Backup Operators , or Print Operators groups. Members of this group cannot modify user rights. The Account Operators group applies to versions of the Windows Server operating system listed in the Active Directory default security groups by operating system version. By default, this built-in group has no members, and it can create and manage users and groups in the domain, including its own membership and that of the Server Operators group.
This group is considered a service administrator group because it can modify Server Operators, which in turn can modify domain controller settings. As a best practice, leave the membership of this group empty, and do not use it for any delegated administration.
This group cannot be renamed, deleted, or moved. Allow log on locally : SeInteractiveLogonRight. Members of the Administrators group have complete and unrestricted access to the computer, or if the computer is promoted to a domain controller, members have unrestricted access to the domain.
The Administrators group applies to versions of the Windows Server operating system listed in the Active Directory default security groups by operating system version. The Administrators group has built-in capabilities that give its members full control over the system. This built-in group controls access to all the domain controllers in its domain, and it can change the membership of all administrative groups.
Membership can be modified by members of the following groups: the default service Administrators, Domain Admins in the domain, or Enterprise Admins. This group has the special privilege to take ownership of any object in the directory or any resource on a domain controller. This account is considered a service administrator group because its members have full access to the domain controllers in the domain.
Default user rights changes: Allow log on through Terminal Services existed in Windows Server , and it was replaced by Allow log on through Remote Desktop Services. Remove computer from docking station was removed in Windows Server R2. Adjust memory quotas for a process : SeIncreaseQuotaPrivilege. Access this computer from the network : SeNetworkLogonRight. Back up files and directories : SeBackupPrivilege. Bypass traverse checking : SeChangeNotifyPrivilege.
Change the system time : SeSystemTimePrivilege. Change the time zone : SeTimeZonePrivilege. Create a pagefile : SeCreatePagefilePrivilege. Create global objects : SeCreateGlobalPrivilege. Enable computer and user accounts to be trusted for delegation : SeEnableDelegationPrivilege. Force shutdown from a remote system : SeRemoteShutdownPrivilege. Impersonate a client after authentication : SeImpersonatePrivilege. Load and unload device drivers : SeLoadDriverPrivilege. Log on as a batch job : SeBatchLogonRight.
Manage auditing and security log : SeSecurityPrivilege. Modify firmware environment values : SeSystemEnvironmentPrivilege. Perform volume maintenance tasks : SeManageVolumePrivilege. Profile system performance : SeSystemProfilePrivilege. Remove computer from docking station : SeUndockPrivilege. Restore files and directories : SeRestorePrivilege. Shut down the system : SeShutdownPrivilege. Take ownership of files or other objects : SeTakeOwnershipPrivilege. The purpose of this security group is to manage a RODC password replication policy.
This group has no members by default, and it results in the condition that new Read-only domain controllers do not cache user credentials. Members of the Backup Operators group can back up and restore all files on a computer, regardless of the permissions that protect those files. Backup Operators also can log on to and shut down the computer. By default, this built-in group has no members, and it can perform backup and restore operations on domain controllers.
Its membership can be modified by the following groups: default service Administrators, Domain Admins in the domain, or Enterprise Admins. It cannot modify the membership of any administrative groups. While members of this group cannot change server settings or modify the configuration of the directory, they do have the permissions needed to replace files including operating system files on domain controllers.
Because of this, members of this group are considered service administrators. The Backup Operators group applies to versions of the Windows Server operating system listed in the Active Directory default security groups by operating system version. Members of the Cert Publishers group are authorized to publish certificates for User objects in Active Directory.
The Cert Publishers group applies to versions of the Windows Server operating system listed in the Active Directory default security groups by operating system version. Members of the Cloneable Domain Controllers group that are domain controllers may be cloned. In Windows Server R2 and Windows Server , you can deploy domain controllers by copying an existing virtual domain controller. In a virtual environment, you no longer have to repeatedly deploy a server image that is prepared by using sysprep.
This security group was introduced in Windows Server , and it has not changed in subsequent versions. Members of this group are authorized to perform cryptographic operations. I've never done it but this KB article goes into detail: How to mark an attribute as confidential in Windows Server Service Pack 1. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.
Create a free Team What is Teams? Learn more. Ask Question. Asked 8 years, 11 months ago. Active 4 years, 11 months ago. Viewed 12k times. Improve this question. Doug Doug 2 2 gold badges 5 5 silver badges 15 15 bronze badges. Just an off-the-top-of-my-head question: you said you don't know of anything in common with the specific users. Are the "broken" users all in groups protected by AdminSDHolder thekortrights. Why do you think that removing Authenticated Users from the Pre-Windows Compatible Access Group will make your system more secure?
It looks like the broken users are all not in the protected groups. That might be significant, I'll have to read this. See if this solution works for you by signing up for a 7 day free trial. What do I get with a subscription? With your subscription - you'll gain access to our exclusive IT community of thousands of IT pros. We can't always guarantee that the perfect solution to your specific problem will be waiting for you.
If you ask your own question - our Certified Experts will team up with you to help you get the answers you need. Who are the certified experts? How quickly will I get my solution? We can't guarantee quick solutions - Experts Exchange isn't a help desk.
0コメント