General discussion

Locked

Moving Shared Folders toNew File Server

By Technohoe ·
Best way or any way to copy shared files from old server to new server that will preserve the shares and permissions.Hopefully freeware, shareware , or some Windows utility . The old server is almost dead but will run for a few hours before needs to be restarted. I'm moving 200 GB of file shares to a new Compaq DL380(WIN2003Server) from an old HP Netserver LH3000R(WIN2KServer).

Any suggestions appreciated.

This conversation is currently closed to new comments.

10 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by Technohoe In reply to Moving Shared Folders toN ...

I'm desperate, Please HELP

Collapse -

by BFilmFan In reply to Moving Shared Folders toN ...

For the Shares themselves, you can use this tool:

http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/Resources/Documentation/windowsserv/2003/all/techref/en-us/w2k3tr_randp_tools.asp

NTFS File Permissions

When you copy or move a file or folder to another volume, the object inherits the permissions of its new folder. This setting allows you to force Windows to preserve the current permissions instead.

Open your registry and find or create the key below.
Create a new DWORD value, or modify the existing value, called "ForceCopyAclwithFile" and set it according to the value data below.

Exit your registry, you may need to restart or log out of Windows for the change to take effect.


Note: By default, an object inherits permissions from its parent object, either at the time of creation or when it is copied or moved to its parent folder. The only exception to this rule occurs when you move an object to a different folder on the same volume. In this case, the original permissions are retained.

The registry key you want to add/or modify is:
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer]ForceCopyAclwithFile
REG_DWORD (DWORD Value)
Value Data: (0 = default, 1 = preserve original permissions)

Best of luck with that issue.

Collapse -

by Technohoe In reply to

Thanks for the response, good info, but I'm looking for a solution that can move all the shared folders to the new server .

Collapse -

by sgt_shultz In reply to Moving Shared Folders toN ...

steady, man! you are gonna live thru this and go on to many more servers that work better after you leave. the utility you seek is called permcopy.exe and it is indeed a microsoft utility and it is one that you have to buy with the win2003 server resource kit. if they have win2k resource kit around, that will probably have it also. i did not find it on their site for free download. why don't you email them and see if they will help you out else get the resource kit. bet you could download it...give bfilm his points because that is the link he gave you: to permcopy.exe
wonder if cacls would help you out here...

Collapse -

by sgt_shultz In reply to

ps would you possibly consider changing your handle?

Collapse -

by Technohoe In reply to

Thanks Sarge, Yes I agree after checking it out. I wound up using Robocopy for the copying of files and ACL's. Now I'm gonna play with permcopy. I have also considered setting up DFS , or a load balancing cluster to copy the file and share info over . Then getting rid of cluster. Looking for a way to automate the share creation cause there are 638 shares to duplicate. Oh I contacted bfilm to resubmit his answer so I can give him the points as suggested.

Thanks

Collapse -

by curlergirl In reply to Moving Shared Folders toN ...

I'm not familiar with permcopy, but robocopy.exe, which is also a resource kit utility, will do it as well. Look up the Win2K or Win2K3 resource kit tools on the Microsoft downloads website, and you should be able to find one or both of these. Good luck!

Collapse -

by BFilmFan In reply to Moving Shared Folders toN ...

Sorry I didn't get back with you right away. Been busy blowing up the client's infrastructure! haha.

If you're going to set up DFS, note that you can place the root of the DFS on a member server, which I highly recommend. I've seen a number of clients have issues where a box is a FSMO role holder/Global Catalog/DFS Root and a single intensive LDAP query causes this scenario:

LSASS hits 100%.
CPU utilization hits 100%.
RPC, not being able to get resources, crashes.

Once RPC crashes, there is no network connectivity and users can't access resources.

I have seen this happen at small companies sometimes, but far more often at large orgnizations that are heavily utilizing AD's LDAP capabilities. I would recommend that everyone memorize this scenario as it happens very frequently.

Collapse -

by Technohoe In reply to

Poster rated this answer.

Collapse -

by Technohoe In reply to Moving Shared Folders toN ...

This question was closed by the author

Back to Windows Forum
10 total posts (Page 1 of 1)  

Related Discussions

Related Forums