Best practice for migrating Shares and Permissions?

Question

We have a Windows 2008 R2 server which is replacing an old Windows Storage Server.

The datastore is attached via iSCSI so I do not need to transfer any data. The iSCSI connection is setup on the new machine, and now I'm wondering:

How should I transfer the shares and permissions?

Do I use PERMCOPY for permissions or is there something better as of Windows 2008 R2 (compared to Windows 2000):

PERMCOPY //SourceServer ShareName //DestinationServer ShareName

Is exporting/importing registry still a valid option? from:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares

Any help/tips would be greatly appreciated.

Solution

If your servers are part of an AD domain, you just have to enable the share on the new server. The acl will be kept. I had to do this once with the import/export registry, you will have to reboot the server.

Comments

[SpacemanSpiff]

How many shares?

[TryTryAgain]

@SpacemanSpiff ~28TB, 19 Shares, and ~10 departments, several ACLs, and quite a few individual/one-offs which would be nearly impossible to track down and take forever to move over manually.

[TryTryAgain]

"The datastore is attached via iSCSI so I do not need to transfer any data."

[TryTryAgain]

So exporting/importing the registry will carry over the actual Shares (names, paths, etc) and AD will take care of the ACLs? Am I following correctly? That's what I'm hoping for. That makes sense, That would be great!

[dunxd]

This would be a more useful answer if you gave some details on how you achieved this, or linked to some documentation.

[dje31]

@TryTryAgain: Yes you are correct. I do not have documentation, but i remember using the "reg" command line to add the registry key. But be carreful with the "Shares" registry key, you might not have the same shares on both servers.

[dje31]

support.microsoft.com/kb/125996/en-us - The procees will be: 1)stop the server service - 2) edit registry key 3) start service