How can I seize ownership of a directory using Powershell?

I have a script that I utilized to correct errant security permissions on users home directories. The script eroors on folders where I don't have explicit permissions, however. Looking at a sampling of them, the only way I can get permission on them is to seize ownership of them, then modify the permissions appropriately, and set the Owner to the correct one. Is there a way to seize ownership via Powershell? Attached is the script that I have been using.

Thanks in advance for any help!
### This script will change the permissions on the immediate subfolders of \\chstor1\home 
### to give the following (By inheriting thge first 3, and explicitly setting the 4th):
### Domain Administrators: Full Control
### IT - - Helpdesk 2 : Full Control
### SVC_DataBackup : Read
### End User: Modify
$ErrorActionPreference = "Continue"
Set-Location e:\Data\Home
$Mismatches = "e:\data\home\Mismatches.txt"
$Inherit = [System.Security.AccessControl.InheritanceFlags]"ContainerInherit, ObjectInherit"
$propogation = [System.Security.AccessControl.PropagationFlags]"None"
if (Test-Path $Mismatches) {
Clear-Content $Mismatches
else {
New-Item $Mismatches -Type File
$Foldername = Get-ChildItem * | Where-Object {$_.attributes -match "Directory"}
foreach ($Fullpath in $Foldername) {
$ACLBase = Get-Acl e:\Data\Home\
### Uncomment the following line to verify default permissions during step debugging
#Set-Acl -Path $Fullpath -AclObject $ACLBase
$username = $Fullpath.Name
$AddACL = "advocatesinc\$username", "Modify", $Inherit, $propogation, "Allow"
$AccessRule = New-Object System.Security.AccessControl.FileSystemAccessRule $AddACL
### Error Handling for directories that don't have a matching username
Trap [Exception] {
  Write-Host "Error occurred, ignoring it"
  Add-Content $Mismatches "Missing account $username"
$ACLBase | Set-Acl $Fullpath 

Open in new window

Who is Participating?

Improve company productivity with a Business Account.Sign Up

Chris DentConnect With a Mentor PowerShell DeveloperCommented:

We'd could trap it like this.

Set-Variable -Name "Unauthorised" -Value $False -Scope Script
Trap [System.UnauthorizedAccessException] { 
  $Script:Unauthorised = $True; Continue;
Get-ACL $Fullpath.FullName
If ($Script:Unauthorised) {
  # Reset Ownership Here 
# Otherwise carry on with setting the permissions

Open in new window

Chris DentPowerShell DeveloperCommented:

There's a SetOwner Method of the $ACLBase object above. To use that you need to construct an IdentityReference.

Something like the below.

You should be able to happily change between possible owners as listed when you look at  the same option in the GUI.

# Create an Identity Reference for the Local Administrators Group
$LocalAdminGroup = `
  New-Object System.Security.Principal.NTAccount("BUILTIN", "Administrators")
# Call SetOwner on the current ACL
# Apply the updated ACL
Set-ACL $FullPath -AclObject $ACLBase

Open in new window

tilbardAuthor Commented:
After adding that it still generates the same error regarding an Unauthorized action. After doing a bit of browsing, I found some workarounds though. Specifically by calling takeown.exe (referenced here: While obviously not the best way to do it (it just rubs me wrong calling an external program for what should work), I'm a bit time constrained, so had to go with that for now. I'll leave the question open for now, and add the exact error it generates after it finishes with the takeown.exe method, as I still want to figure out WHY it wouldn't work (for personal knowledge if nothing else).
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Chris DentPowerShell DeveloperCommented:

Hmmm sorry I neglected to strip my read permission prior to changing the owner. It's rather disappointing, it seems overriding ownership when you have no access is a bit of a back door, something that PowerShell seems unable to utilise.

I'll keep looking, but it's not looking all that promising.

tilbardAuthor Commented:
One last question before I assign points (You'll get them either way though, don't worry. ;) ). When running the script, the unauthorized action error isn't being caught by the trap. Is there anyway to trap that so that I don't have to run takeown.exe against directories that don't have any trouble? As you can imagine, it adds quite a bit of time to the script if it runs it against every folder, since it has to recurse through each one. Being able to call it within the trap would speed things up quite a bit, and make the output a bit more readable.
tilbardAuthor Commented:
Worked great, thanks!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.