RE: NT 4 domain migration to new domain name in win2k3

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Dear Customer,

Thanks for posting here.

According to the description, my understanding is that:

You deployed a new domain and then migrated all the users and groups from
old Windows NT 4.0 domain to the new Windows 2003 domain. Then you migrated
all the share folders to the new domain with FSMT. You also use robocopy to
copy all the changed files and folders.

Your concern is that after migrating all users and groups and share folder
to the new domain, you find that the new domain users can't access the
share folder directory copied over from the old_domain to the new_domain,
however the users of old_domain had full rights to all the share folders
which were copied over to the new_domain.

Analysis:
=============

Since after you migrated the users and groups from old_domain to new_domain
with ADMT, new users and groups will be created with new SIDs in the new
domain. However, after the share folders were migrated to the new_domain
with File Server Migration Toolkit, FSMT remains the share and NTFS
security settings for share folders.

As a result, the old domain users and groups should still be able to access
the shares. However, the new domain's users and groups should have not
necessary permissions on the share, because they are not defined in the
share folders' permission configurations.

Suggestion:
==========

1. Migrate these share folders from the old file server to the new file
server with FSMT firstly.

2. Then please migrate the users and groups from old domain to new domain
with ADMT and keep the membership information during the migration.

3. Afterwards, run ADMT - security translation wizard to translate the
security settings on the new file server.

4. After the security translation, please check if the users and groups of
the new domain can access the share folders.

For more reference:
==============

Download: Microsoft File Server Migration Toolkit
http://www.microsoft.com/downloads/details.aspx?FamilyID=d00e3eae-930a-42b0-
b595-66f462f5d87b&DisplayLang=en

File Server Migration Toolkit Whitepaper
http://download.microsoft.com/download/9/6/3/963f5b22-6304-4f15-a2af-35e0b81
046af/FSMT%20Whitepaper.doc

Download: Active Directory Migration Tool v3.0
http://www.microsoft.com/downloads/details.aspx?FamilyID=6f86937b-533a-466d-
a8e8-aff85ad3d212&DisplayLang=en

ADMT v3 Migration Guide
http://www.microsoft.com/downloads/details.aspx?familyid=D99EF770-3BBB-4B9E-
A8BC-01E9F7EF7342&displaylang=en

Hope all the information will be helpful for you. I'm looking forward to
your reply.

Thanks for your time.


Thanks a lot.

David Shen
Microsoft Online Partner Support

.

Relevant Pages

  • RE: File system migration tool question
    ... try this very nice tutorial for migration ... If the files and folders are replicated to the new file server through DFS, ... Please unselect the checkbox of "Resolve invalid Security descriptors" ...
    (microsoft.public.windows.server.migration)
  • RE: File system migration tool question
    ... If the files and folders are replicated to the new file server through DFS, ... You may install File Server Migration Tool on the new file server. ... Please unselect the checkbox of "Resolve invalid Security descriptors" ...
    (microsoft.public.windows.server.migration)
  • Re: how to deal with security permission on folders
    ... "Exchange Migration Wizard". ... you may use ADMT to migrate user account and password and ... |> hosting hundreds of users folders, with each folder having permission ...
    (microsoft.public.windows.server.migration)
  • RE: Moving Permissions for Local Users
    ... the issue seems to be related to File server ... You have used the third party "winzero server migration tool" to migrate ... We can copy the files and folders by using Robocopy.exe. ... the tool will also copy NTFS permissions when copying files. ...
    (microsoft.public.windows.server.migration)
  • RE: Moving home folders still have old permissions
    ... resource domain migration to Windows Server 2003 ... Moving home folders still have old permissions ... Now I wanted to move some folders from an old file-sharing NT BDC ...
    (microsoft.public.windows.server.migration)