• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 467
  • Last Modified:

Move files first and permissions later (NTFS)


I am about to migrate a Windows Server 2003 fileserver to a Windows Server 2008 fileserver.

I am using Robocopy with theese switches:
robocopy S:\ \\\S$ /e /sec /copyall /xd S:\Inst /log:c:\RobocopyLogs\S-drev.txt /tee /r:0

On a lot of files and folder I get Access Denied 0x00000005. My guess is that it is because of some write restrictions that has been set on all files and folders.

My question is, can I export all file/folder permissions, then set the appropriate permissions whitch allows me to migrate the files and the at last import the file/folder permissions that I exported earlier?

Or should I go about it completely differently?

Kasper K
Kasper Katzmann
Kasper Katzmann
2 Solutions
Darius GhassemCommented:
Usually this points to attributes being copied.

Try using this switch /COPY:DT

Here is something else to take a look at since you are copying to Windows 2008 Server.

yo_beeDirector of Information TechnologyCommented:
The files could be open or for some reason the Admin does not have rights to that file.

I know you can use NTBACKUP to backup the 2003 files and copy the 3 files needed to run NTBACKUP on server 2008.


This will at least get your files over with the proper permissioning and not receive errors.
Darius GhassemCommented:
If you are using Windows 2008 Server you can download the Ntbackup restore utitlity


If you are using Windows 2008 Server R2 then you can't use that tool but MS was suppose to create one so, it can be restored.

Leon FesterSenior Solutions ArchitectCommented:
It wouldn't be a write permissions issue, most likely a read permissions issue.
Check you log file for the file that was last copied or which contains the error.

You're migrating a fileserver, so I'm guessing somewhere along the line somebody broke inheritance and there are some folder that your account does not have permissions to view.

Even if you are an admin on the box, broken inheritance can lead to you not having permission to read some files/folders.
Kasper KatzmannSeniorkonsulentAuthor Commented:
It was due to broken enharitance. I had to make some adjustments to the permissions and then let them propagate.<br /><br />Thanks for all the suggestions.
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.

Join & Write a Comment

Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now