Domain Admin can't delete or take ownership of file


I was trying to delete some old home directories on the file server, but I have come across some folders with a single small hidden file (ntuser.pol) that won't go away.  

I can see it, but I cannot open it, much less delete it.  When I try to take ownership of the file, the procedure seems to work, but as soon as I try to apply permissions to the file so I can delete it, I am denied.

In the security tab, I can see that the SYSTEM account has full control, but when I log in as SYSTEM (ala psexec), I still can't delete the file (access denied).

how kill these files?

Marketing_InsistsAsked:
Who is Participating?
 
krais99Connect With a Mentor Commented:
When you say that you're taking ownership, are you simply adding your domain admin account to the security tab with full control, or are you going into Advanced->Owner and clicking on the admin account under Change owner to: ?

I've ran into this in the past and gotten around it by replacing owner on subcontainers and objects as well.

Todd
0
 
Jay_Jay70Commented:
Hi Marketing_Insists,
>
don't delete that file

description:
An archive file on client computers that is updated each time the Administrative Templates CSE sets a policy setting. As processing completes, an Ntuser.pol containing the history of applied registry based policies in the Group Policy managed policies tree is written to the root of the user’s profile containing user policy settings and to the “all users” profile containing computer policy settings.(%Allusersprofile%\ntuser.pol for computer policy and %userprofile%\ntuser.pol for user policy.)
0
 
Marketing_InsistsAuthor Commented:
Ah, but these are home directories of roaming users who have left the company.  the remaining .pol file is the only existing file after a otherwize effective rd /s /q jdoe.

It dosn't happend all the time, just one out of every 10 previous users have this lingering element.

0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Jay_Jay70Commented:
Marketing_Insists,

ah i see i see, you can try from safe mode

or try this app
http://process.networktechs.com/KillBox.exe.php
0
 
Netman66Commented:
If Safe Mode doesn't work, then use the Recovery Console.

0
 
Marketing_InsistsAuthor Commented:
Bummer me, it was the sub-containers that were the issue
Thanks!
0
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.