Set-Acl cmdlet fails although delegated admins have "Change Permissions" enabled in Windows Server 2012 R2

This article describes an issue that occurs on a Windows Server 2012 R2-based computer that has the Active Directory Domain Services (AD DS) role installed. A hotfix is available to fix this issue. The hotfix has a prerequisite and a restart requirement.
Symptoms
Assume that the delegated admins only have permissions to change the permissions but they're not the owner or in the system access control list (SACL). This issue occurs when delegated admins use PowerShell scripts to manage the access permissions of the objects. When this issue occurs, the admins receive an error message that looks something like this:

This security ID may not be assigned as the owner of this object.

Note This issue also occurs with the initial releases of the Remote Server Administration Tools for Windows 10.

In the newest release that comes with the final release of Windows Server 2016, this problem is solved.
Resolution
To fix this issue, we have released a hotfix. Even though this issue is observed only in Windows Server 2012 R2, the hotfix also applies to Windows 8.1.

Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that don't qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you don't see your language, it's because a hotfix isn't available for that language.

Prerequisites

To apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1 or Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you don't have to make any changes to the registry.

Restart requirement

If there's no active PowerShell instance that uses the AD Provider, you don't have to restart the system.

Hotfix replacement information

This hotfix doesn't replace a previously released hotfix.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More information
This issue occurs because, when a security descriptor is programmatically updated, the application can ask to only update certain parts of the security descriptor. When a delegated admin can only update the discretionary access control list (DACL), the application needs to specify this. Until this update, the Active Directory PowerShell cmdlet Set-Acl didn't use the correct flags to write out the DACL only. So, the call fails for being unable to write the owner part of the security descriptor.
References
See the terminology that Microsoft uses to describe software updates.
File Information
The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). Be aware that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you perform certain operations on the files.

Windows 8.1 and Windows Server 2012 R2

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

Notes
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.3.960 0.18 xxxWindows 8.1 and Windows Server 2012 R2RTMGDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
x86 Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Microsoft.activedirectory.management.dll6.3.9600.181161,194,49603-Nov-201504:53x86
x64 Windows 8.1 and Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Microsoft.activedirectory.management.dll6.3.9600.181161,194,49603-Nov-201505:46x86
Microsoft.activedirectory.management.dll6.3.9600.181161,194,49603-Nov-201504:53x86

Additional file information

x86 Windows 8.1
File propertyValue
File nameUpdate.mum
File versionNot applicable
File size1,602
Date (UTC)04-Nov-2015
Time (UTC)22:15
PlatformNot applicable
File nameX86_b9260dfc9aa784896f23893e0a08f600_31bf3856ad364e35_6.3.9600.18116_none_d400ce779a6ce43a.manifest
File versionNot applicable
File size706
Date (UTC)04-Nov-2015
Time (UTC)22:15
PlatformNot applicable
File nameX86_microsoft.activedirectory.management_31bf3856ad364e35_6.3.9600.18116_none_ad839613918295ce.manifest
File versionNot applicable
File size2,885
Date (UTC)03-Nov-2015
Time (UTC)05:09
PlatformNot applicable
x64 Windows 8.1 and Windows Server 2012 R2
File propertyValue
File nameAmd64_8a93926b6ec7ecd750724198fa79a8ad_31bf3856ad364e35_6.3.9600.18116_none_f881375f84bfecfd.manifest
File versionNot applicable
File size1,060
Date (UTC)04-Nov-2015
Time (UTC)22:15
PlatformNot applicable
File nameAmd64_microsoft.activedirectory.management_31bf3856ad364e35_6.3.9600.18116_none_09a2319749e00704.manifest
File versionNot applicable
File size2,889
Date (UTC)03-Nov-2015
Time (UTC)06:07
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,818
Date (UTC)04-Nov-2015
Time (UTC)22:15
PlatformNot applicable
File nameX86_microsoft.activedirectory.management_31bf3856ad364e35_6.3.9600.18116_none_ad839613918295ce.manifest
File versionNot applicable
File size2,885
Date (UTC)03-Nov-2015
Time (UTC)05:09
PlatformNot applicable
Properties

Article ID: 3092002 - Last Review: 10/25/2016 05:11:00 - Revision: 4.0

Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation, Windows 8.1 Enterprise, Windows 8.1 Pro, Windows 8.1

  • kbqfe kbsurveynew kbfix kbhotfixserver kbautohotfix kbexpertiseinter KB3092002
Feedback