What you’re seeing
- Files arrived on the new server, but users get "access denied" on folders they could open before.
- Every file now shows the administrator who ran the copy as its owner.
- Created or modified dates on the copied files show the date of the migration instead of the originals.
- Folders on the new server inherit broad permissions, so staff can see data that used to be restricted.
- Some files were skipped and the copy log lists access or permission errors.
Common causes
Every environment is different, but these are the causes our engineers find most often:
- The copy was run with default options, which bring over data and timestamps but not security permissions, owner or auditing information.
- Drag-and-drop copying in File Explorer applies the destination folder's permissions to new files instead of keeping the originals.
- The account performing the copy lacked the backup-level rights needed to read and write security information on every file.
- Permissions on the source referenced local accounts or groups that do not exist on the new server, so they could not be carried across.
- The destination file system or storage device does not support Windows-style NTFS permissions.
Why it matters
Permissions are what keep payroll, HR and client files away from the wrong people. A migration that loses them can do harm in two directions: staff are locked out of their own work on day one, or sensitive data becomes readable by everyone. The second is worse because it often goes unnoticed and can trigger compliance obligations under privacy or industry rules. Re-creating permissions by hand afterward is slow and error-prone, especially on large shares.
How AskTechGurus fixes it
Skip the trial and error. A certified engineer works on your actual system, finds the root cause, and fixes it properly.
Tell us what’s happening
Submit a ticket in about two minutes. Paste the error, describe what changed, and pick your tier. No charge to submit.
A certified engineer diagnoses it
A vetted, US-based systems engineer claims your ticket, usually within minutes during business hours, and investigates over a secure remote session you can watch and end at any time.
Fixed and verified with you
The engineer resolves the root cause and confirms with you that it’s working. You don’t just get a workaround, and you get a plain-English summary of what was wrong.
Pay only when it’s resolved
Fixed price from $99, invoiced only after you approve the fix. If it isn’t resolved, you don’t pay.
Frequently asked questions
Has anyone seen data they shouldn't have?
It depends on how long the new permissions have been in place and whether access auditing was turned on. An engineer can review the current permissions and any available logs to help you understand the exposure.
Do we have to redo the whole migration?
Not always. If the original server still exists, permissions can often be reapplied from it without copying all the data again.
Will users notice while this is corrected?
Usually very little. We confirm the plan with you before changing anything, and changes can be scheduled outside busy hours.