![]() I still decided to press forward with this and later found the second issue: takeown.exe would not reliably grant ownership completely down the tree of subfolders. Obviously this is an issue if I expect to have this used as part of my project for others to take ownership on profiles which would more than likely have more items than my profile. ![]() I kicked it off on my own profile (because it is always more fun to test on yourself than others) and found that it would take upwards of 10 minutes vs. Sure it wasn’t a PowerShell approach, but it met the requirements of what I wanted to do…or so I thought. This was actually my initial idea as I allows for recursive actions and lets me specify to grant ownership to Builtin\Administrators. This created issues with deleting accounts and troubleshooting profile related issues.īefore showing the solution that I came up with, I will run down a list of attempts which never quite met my requirements and why. ![]() Also, ownership of those objects were by the user account. The brief background on this is that roaming profiles sometimes would become inaccessible to our support staff in that only the user account and System would have access to the profile folder and its sub-folders and files. But the goal was to come up with a command line solution that not only worked quickly, but didn’t miss out on a file or folder. ![]() Typically, one could use Explorer to find the folder and then take ownership and be done with it. While working on a project recently, I needed to find an easy way to take ownership of a profile folder and its subfolders to allow our support staff to either delete the profile or be able to traverse the folder to help troubleshoot issues. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |