Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I have a policy set where the contents of a user's "My Documents" folder is redirected to their home folder (\\server\home\%username%). When a new user logs into the domain for the first time, the "My Pictures" folder is also created and re-directed to their home folder on the server.
Up until a few weeks ago, if the user left the company, I would be able to remain logged into the domain with Admin rights, and take ownership of that user's My Pictures folder so it can be deleted or moved. Post SP4, I am not able to do ANYTHING with this doggone folder. I can access and move all other files within the user's home folder, but My Pics seems unaccessible unless I login as that user (kind of time consuming).What I've tried so far:
In Domain Security Policy on the domain controller, under "Local Policies" and "User Rights", I added the administrators group to the "take ownership of objects" setting.
Also I've tried to reset permissions from the parent folder, but I get an error when it hits the "My Pictures" folder.
I've disabled virus scanning while trying to get into the folder. NOTHING IS WORKING.Is my GPO not setup correctly? Did something happen when SP4 was installed?
Thanks for any input.

It sounds like one or more of the pictures in that folder are write-protected. I would try to move the pictures one at a time (cut and paste) to a different location, and then when try to move that folder.
Or see if something is actually using one of the images and turn that program off prior to attempting the move.

Thanks--I figured it out.
It was the Domain Controller Security Policy for taking ownership of files/folders (I gave the Administrators rights). I think it just took a good 20 minutes to replicate the new security changes.
SP4 changed this setting, along with a few other security policy settings on the domain controllers.

![]() |
win2k boot failure
|
Usb Pen Drive
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |