Skip to main content This browser is no longer supported. Show
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Take ownership of files or other objects
In this articleApplies to
Describes the best practices, location, values, policy management, and security considerations for the Take ownership of files or other objects security policy setting. ReferenceThis policy setting determines which users can take ownership of any securable object in the device, including Active Directory objects, NTFS files and folders, printers, registry keys, services, processes, and threads. Every object has an owner, whether the object resides in an NTFS volume or Active Directory database. The owner controls how permissions are set on the object and to whom permissions are granted. By default, the owner is the person who or the process that created the object. Owners can always change permissions to objects, even when they're denied all access to the object. Constant: SeTakeOwnershipPrivilege Possible values
Best practices
LocationComputer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment Default valuesBy default this setting is Administrators on domain controllers and on stand-alone servers. The following table lists the actual and effective default policy values. Default values are also listed on the policy’s property page.
Policy managementThis section describes features, tools, and guidance to help you manage this policy. A restart of the device isn't required for this policy setting to be effective. Any change to the user rights assignment for an account becomes effective the next time the owner of the account logs on. Ownership can be taken by:
Ownership can be transferred in the following ways:
Group PolicySettings are applied in the following order through a Group Policy Object (GPO), which will overwrite settings on the local computer at the next Group Policy update:
When a local setting is greyed out, it indicates that a GPO currently controls that setting. Security considerationsThis section describes how an attacker might exploit a feature or its configuration, how to implement the countermeasure, and the possible negative consequences of countermeasure implementation. VulnerabilityAny users with the Take ownership of files or other objects user right can take control of any object, regardless of the permissions on that object, and then make any changes that they want to make to that object. Such changes could result in exposure of data, corruption of data, or a denial-of-service condition. CountermeasureEnsure that only the local Administrators group has the Take ownership of files or other objects user right. Potential impactNone. Restricting the Take ownership of files or other objects user right to the local Administrators group is the default configuration.
FeedbackSubmit and view feedback for Which of the following best describes what happens to the permissions for both files as they are created in the D :\ public reports folder?Which of the following BEST describes what happens to the permissions for both files as they are created in the D:\PublicReports folder? Permissions are removed from Reports.
Which of the following best describes what happens when share and NTFS permissions combine?When using share permissions and NTFS permissions together, if there is a conflict in the configuration, the most restrictive permission prevails. For example, if a user has NTFS full access to a specific file in a folder that is not shared, the user cannot access the file from the network.
What happens when a user belongs to two groups and a specific permission is allowed for one group and denied for the other?What happens when a user belongs to two groups, and a specific permission is allowed for one group and denied for the other? Denied permissions always override allowed permissions.
What best describes share and NTFS permissions select two?NTFS permissions apply to users who are logged on to the server locally; share permissions don't. Unlike NTFS permissions, share permissions allow you to restrict the number of concurrent connections to a shared folder. Share permissions are configured in the “Advanced Sharing” properties in the “Permissions” settings.
|