RE: FSMT on a BDC

From: Jason Tan (v-jasont_at_online.microsoft.com)
Date: 02/25/05 

Date: Fri, 25 Feb 2005 07:27:59 GMT

Hi Sam,

Thanks for posting!

>From your message, you want to know whether FSMT can be used to migrate all
shares and permissions on a "BDC" based on Windows NT 4.0 to Windows Server
2003 server.

Based on my research, the answer is positive. FSMT can run a BDC. However,
we don't run it on BDC. we install FSMT on the destination file server,
which should be a win2k3 server. NOTE: The source and destination domain
should have two-way trusts.

The File Server Migration Toolkit helps you copy files and folders from
servers running Microsoft Windows 2000 Server or Microsoft Windows NT
Server 4.0 operating systems to a server running Microsoft Windows Server
2003 operating systems or Microsoft Windows Storage Server 2003.

To ensure the security of files and folders after they are migrated to a
target file server, the File Server Migration Wizard applies permissions
that are the same as or more restrictive than they were on the source files
and folders, depending on the option you select. For example, if you do not
choose to copy security settings from the source to the target files and
folders, the wizard applies permissions to the target files, folders, and
shared folders by granting Full Control permission to the local
Administrators group of the target file server. If you select the Copy
security settings option, the File Server Migration Wizard copies all
security settings for files, folders, and shared folders, including NTFS
file system permissions, auditing, ownership, and shared folder
permissions. If you also select the Resolve invalid security descriptors
option, the wizard cleans up security descriptors whose security
identifiers (SIDs) cannot be resolved on the target file server.

For more information, please refer to the following article:

Microsoft File Server Migration Toolkit:
http://go.microsoft.com/fwlink/?LinkId=26396

FAQ on FSMT:
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_faqs
.mspx

White Paper:
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_over
view.mspx

I hope my information helps. If there is anything that is unclear, please
feel free to let me know.

Thanks & Regards,

Jason Tan

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: SBS 2003 Outoging Fax Problem w/Error 32028 (Cannot send - fatal error)
    ... 1.Reduce the baud rate of the incoming fax modem and see how it goes. ... Click Permissions and verify that the user attempting to fax has at ... 3.If you have configured the fax client on the Windows XP computer ... On the "Additional Server Types" page, ...
    (microsoft.public.windows.server.sbs)
  • RE: Userenv Error
    ... Microsoft Windows Small Business Server 2003 Service Pack 1 ... Please check both the Share Permissions of the Group folder, ...
    (microsoft.public.windows.server.sbs)
  • Re: Workgroup server to domain
    ... Microsoft MVP - Windows NT Server ... >>may have to add permissions for domain users to access ... >>Scott Harding ... >>Microsoft MVP - Windows NT Server ...
    (microsoft.public.windows.server.migration)
  • Re: login/logoff Report
    ... located both the cmd files in the correct place now. ... Make sure you have hotfix 842933 applied to the SBS server ... truncated" error message when you try to modify or to view GPOs in Windows ... Make sure the "logging folder" share has Share Permissions: ...
    (microsoft.public.windows.server.sbs)
  • Re: Log on Interactively
    ... The server is a Windows 2003 Enterprise Edition Server ... I added the Remote Desktop Users group to the permissions tab with the User ... I then added the Terminal Services User group that I had ...
    (microsoft.public.windows.terminal_services)