During Robocopy from old to new server, there were Access Denied errors that hung up the process. I included the switches /R:0 and /W:0 to skip the files causing errors.
Now I'd like to run Robocopy and get a list of the files and folders that are causing the errors so I can determine whether they need to be moved or can be left behind. I've searched but have not found a way to get just this list of errors. Is there a way to do this?
Thanks.
--Art
It is strange that you get Access Denied errors that hangs Robocopy. That should never happen if you run it elevated.
Hey Mariette - I'm getting the same issue on robocopy-ing files from the FolderDirections folder. I'm using elevated permissions. Can I take ownership of the files or will that cause issues? Is there another way if not?
No, do not take ownership because that will create more problems. What kind of files have these problems? If you are certain that the problem is permissions (I doubt that) you should do this How the administrator can gain access to redirected folders owned by domain users and which are created by a policy using ‘grant the user exclusive rights’.
Sometimes robocopy fails on temp files and if that is the case you need to exclude them, see
# Exclude a folder /XD "C:\source\folder\path\to\exclude-folder" # Exclude a file /XF "C:\source\folder\path\to\folder\filename.extension"
In both cases you can also wildcards. If you have files with somefile123 as the name and you want to skip all of them use somefile*
Sounds good - thank you for the quick reply!
I kind of think that permissions have been messed up at some point over the last 10 years though. It wasn't just temp files that were having issues on the copy-over.
If I was to first correct them on that root share (FolderRedirections), would you recommend the article below for reestablishing the correct permissions? If I don't, will that just bring bad permissions into 2019? Or should I just try your article for giving access to administrators without taking ownership?
https://docs.microsoft.com/en-us/archive/blogs/migreene/ntfs-permissions-for-redirected-folders-or-home-directories
Changing NTFS permissions once the folders and files have been created to their normal behavior is not possible with that document. Owner is owner. That can only be changed if the 'owner' is logged on to a workstation and then right click My Documents and change ownership from there.
Gotcha. Last question (I think!): would it be safer/easier then to just remove folder redirection from those handful of users, allow the files to be moved to their client machines, then set it back up once 2019 is totally set up? Or am I over-thinking it?
Well, it depends. If the permissions were changed in a non supported way, read ownership was changed the path you want to take will fail also.