RE: NT4 File Server to 2000

From: Daniel404 (Daniel404_at_discussions.microsoft.com)
Date: 01/24/05 

Date: Mon, 24 Jan 2005 11:43:05 -0800

Is there a way to rename the W2K server and maintain the users connectivity
to the shares? Thanks for all of your assistance you have been of great help
so far.

"Frances [MSFT]" wrote:

> Hello Daniel,
>
> Yes, you can use Robocopy to copy the files to the SMS server. In this way,
> the NTFS permission of the files will retain. As for the share permissions,
> I think you can copy the registry keys from the old files server.
>
> More details are offered below.
>
> We can migrate the shares' NTFS permissions and share permissions
> separately. For NTFS permissions, we can use the Windows 2000 Resource Kit
> tool robocopy.exe with the "/SEC" switch to copy the folders with their
> NTFS permissions. For share permissions, we can backup and restore them by
> saving and restoring the following registry key:
>
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\Shares]
>
> Commonly-Used Steps:
>
> 1. Copy all the data from the old file server to target file server.
>
> Note: Please ensure that both the target file server and the source file
> server have the same folder scheme (the shares' folder paths on the target
> file server are the same as the ones on the source file server). This is
> necessary for us to migrate the share information.
>
> If both the source and destination directories reside on NTFS volumes, we
> can use Robocopy with the /SEC switch to copy NTFS permissions when copying
> files to the same location on the target file server. This will ensure that
> both the folder structures and their NTFS permissions are fully copied the
> target file server.
>
> Note: To refresh security information for existing destination files and
> directories without copying file data, we can use the /SECFIX switch.
> /SECFIX copies permissions for newly copied files and refreshes security
> information for existing destination files and directories.
>
> 2. Copy the share permissions from the source file server
>
> Actually, the share definitions are saved in the following registry key:
>
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\Shares]
>
> Therefore, our steps in this section are:
>
> 2.1) Back up the above key on the target file server (for recovery
> purposes).
>
> 2.2) Back up the key on the source file server in to a reg file.
>
> 2.3) Merge the reg file to the target file server.
>
> 3. Check if all of the share permissions have been successfully migrated to
> the new file server. If not, we can try Permcopy.exe to copy share
> permissions (Full Control, Read, and Change) from one existing share to
> another.
>
> permcopy \\SourceComputer SourceShare \\TargetComputer TargetShare
>
> Reference:
>
> 141589 How to Restore Share Definitions To Another Server
> http://support.microsoft.com/?id=141589
>
> Hope it helps!
>
> Best regards,
>
> Frances He
>
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> =====================================================
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Relevant Pages

  • Re: finding folders with "write" permission
    ... If you prefer to copy the NTFS and Share permissions to the new server, ... Copy all the data from the old file server to target file server. ...
    (microsoft.public.windows.server.migration)
  • Best way to assign NTFS permission in order to migrate to AD on W2K3
    ... the main file server is a W2K member server and ... most of its permissions are assigned to groups like Domain Users. ... If I use a Global Group then I cannot include other GGs (that is ... to move the files to a different file server in the future. ...
    (microsoft.public.windows.server.migration)
  • RE: NT4 File Server to 2000
    ... I think you can copy the registry keys from the old files server. ... We can migrate the shares' NTFS permissions and share permissions ... For NTFS permissions, we can use the Windows 2000 Resource Kit ... Copy all the data from the old file server to target file server. ...
    (microsoft.public.windows.server.migration)
  • Re: Thoughts on removing Everyone:F from root?
    ... > NTFS permissions should be set. ... I've been in the mind set ... and NTFS permissions alone isn't enough to ... prevent a compromise of an insecure server. ...
    (microsoft.public.win2000.security)
  • Re: DFS/AD Migration
    ... Its best practice for the permissions to be assign to local groups on the file server box and then put domain groups in these. ... When the DFS teams move the folders/files to DFS the ...
    (microsoft.public.windows.server.active_directory)
Quantcast