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

Moving Shared directories in 2003

I would like to move a couple directories in 2003.  They are currently shared and I would like to move them without having to reshare the permissions.



move to


I've looked into robocopy and FSM, but can't seem to get them to work.

what else can I try?
1 Solution
Jason WatkinsIT Project LeaderCommented:

Unshare the directory, move the contents, re-share in the new location.

As long as you have the correct Share and NTFS permissions noted, what is the difficulty in moving?

Perhaps this could be a time to set up a DFS?  http://technet.microsoft.com/en-us/library/cc782417%28WS.10%29.aspx
All your shares are defined under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer
you can export this hive and import it on new machine. It will re-share your folders with old ACLs. Of course you can edit your file after export and before import. This can change your paths and remains share ACLs intact.

In some scenarios you can also use file server migration toolkit from http://www.microsoft.com/downloads/details.aspx?FamilyID=d00e3eae-930a-42b0-b595-66f462f5d87b&DisplayLang=en
Joseph DalyCommented:
I would also reccomend doing what the others have mentioned. If you move/copy to your data you can simply recreate the shares with the correct permissions. All the matters is that the full unc path is the same for example \\server\group1.

But if you are looking for a program that will automatically move/copy EVERYTHING including shares and ntfs permissions. Take a look at securecopy by scriptlogic.


I have used this in the past to do server migrations where there are many many shares and individually recreating them is not feasable. Very fast copy and very robust tool to allow you to do pretty much any data migration you may need.
Along the lines of xxdcmast's comment, there are scripts that can copy/recreate share permissions but you would need to copy the files.

You have to perform some alteration either manually or by use of scripts.

If these shares may move again, you may wish to consider using DFS and set the share as a domain share rather than a server share.  i.e. accessible as \\domain\sharename versus \\server\sharename.

The benefit is should you need to move the share again presumably because of space constraint, it is simpler and the client systems will not need to do a thing i.e. reconfigure/remap.
ksuchewieAuthor Commented:
Not the answer I was hoping for, but this is what I ended up having to do.

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

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