| Author |
Message |
John
Guest
|
Posted:
Tue Jan 11, 2005 4:53 pm Post subject:
File server Migration |
|
|
As part of our migration form nt 4.0 to 2003 AD we need to migrate the
file server containing the users home drives. What is the easiest way
of doing this while keeping all permissions intact. And ensuring the
tool doesn't hang by damaged data(or other errors). Rather saves the
details in a log file.
John |
|
| Back to top |
|
 |
Frances [MSFT]
Guest
|
Posted:
Wed Jan 12, 2005 9:43 am Post subject:
RE: File server Migration |
|
|
Hello John,
FSMT is commonly used for file server migration. You can have more
information in the following articles.
Microsoft File Server Migration Toolkit FSMT Site:
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfsc.mspx
Overview of the Microsoft File Server Migration Toolkit white paper of FSMT
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_over
view.mspx
Frequently Asked Questions About File Server Migration
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_faqs
.mspx
in addition, I am not quite sure your meaning of " containing the users
home drives", do you use roaming profile for users and you want to move all
the user home folder? If so, ADMT can help you migrate roaming profile.
Please refer to the following document with the part of ADMT Features:
Options to suit you.
Active Directory Migration Tool Overview
http://www.microsoft.com/windows2000/techinfo/planning/activedirectory/admt.
asp
A kind reminder, when you migrate users with ADMT, SID history is kept by
default. Then the folder permissions which you grant to users needn't to be
changed.
Hope it helps. Any update, let us get in touch!
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. |
|
| Back to top |
|
 |
jackson_140@hotmail.com
Guest
|
Posted:
Wed Jan 12, 2005 1:49 pm Post subject:
Re: File server Migration |
|
|
Thanx
I tried the fsmt but wasn't that happy with it. Will try to have
another go at it.
I was thinking of using robocopy. with the /mir /copyall syntax but it
seems the copyall sysntax is not compatible with nt.
Yes we are talking about roaming profiles. But what we are currently
looking at is. Building a nt 4.0 bdc taking it offline promoting to pdc
do a os upgrade. Then take the old pdc offline and rename the new 2003
AD machine to the same name and IP adress. And just put it online. This
means we won't be using
ADMT tool. And we would like for the moment to keep the folder
permissions as they are.
But thanx for the imput will go trough it again
john |
|
| Back to top |
|
 |
jackson_140@hotmail.com
Guest
|
Posted:
Wed Jan 12, 2005 1:52 pm Post subject:
Re: File server Migration |
|
|
Sorry on the first part of the meaning of home drives. It is where the
roaming profiles are stored and the user's own data on the server
(rather then on each indivdual pc, for a large part). |
|
| Back to top |
|
 |
Frances [MSFT]
Guest
|
Posted:
Thu Jan 13, 2005 4:12 pm Post subject:
Re: File server Migration |
|
|
Hello John,
According to your description, you did a not-in-place upgrade, which means
the domain has not changed. In this scenario, I believe you do not need to
do a file migration, since everything has not changed. Please check that
the roaming profiles can work in the win 2003 domain.
If the old PDC holds the roaming profile, you have to change the profile
server to another server.
Since the old PDC has the same name as the win2k3 server currently running,
you cannot directly copy all roaming profile folders from NT to win2k3, you
need to use an interim server; otherwise, you need to use xcopy command to
copy the folders to a storage, then copy the information from the storage
to the win2k3 and reconfigure the roaming profile.
Xcopy syntax
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/p
roddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/stan
dard/proddocs/en-us/xcopy.asp
Command Line Switches for the XCOPY Command
http://support.microsoft.com/default.aspx?scid=kb;en-us;128756
Note: Please use /s ,/e ,/t to copy the files in subdirectory; use /h to
copy files with hidden and system file attributes; use /x to copy file
audit settings and system access control list (SACL) information (implies
/o).
robocopy.exe is not recommended since the robocopy.exe for the Windows 2003
can't be used at the Windows NT 4 server.
You can follow the steps below to change the profile server to another
server.
1. On the profileserver, right click the Profile folder and select
Properties
2. Go to the Security tab
3. Click the Ownership button
4. Click the "Take Ownership" button
5. You will got the "One or more of the items selected is a directory. Do
you want to take ownership of all the files and subdirectories contained in
the selected directories?" window
6. Click Yes. This will take the ownership of all user profile folder to
the administrator. The administrator by default don''t have the permission
to access the user profile folder.
7. Use the xcopy.exe to copy the data to the interim server, and then from
the interim server to the new profile server. In this way, we can avoid the
conflicts that may arise because the source and target server have the same
name.
8. In the new profile server, you can manually re-configure the folder
security of the profile folder. You also need to re-share the profile
folder.
9. Re-configure the user roaming profile path in the Active Directory Users
and Computers.
You can refer to the article below to have more information.
How to configure a user account to use a roaming user profile in Windows
Server 2003, Windows 2000 Server, or Windows NT 4.0
http://support.microsoft.com/default.aspx?scid=kb;en-us;316353
Hope it helps! Any updates, let us get in touch!
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. |
|
| Back to top |
|
 |
jackson_140@hotmail.com
Guest
|
Posted:
Thu Jan 13, 2005 5:37 pm Post subject:
Re: File server Migration |
|
|
Hi thankx for the reply what we were thinking of was. Copying the whole
file system onto the nt box while it is still configured as a bdc. The
question was how to do that with keeping all the security settings
intact. And the do a os upgrade. Retire the old pdc. And then just boot
up the AD system
regards
john |
|
| Back to top |
|
 |
Frances [MSFT]
Guest
|
Posted:
Fri Jan 14, 2005 12:40 pm Post subject:
Re: File server Migration |
|
|
Hello John,
According to your description, you have a plan to upgrade you domain from
NT to windows 2003. You are now concerning the file migration since you
need to keep the security settings intact.
I have some suggestions regarding your plan. Please follow the steps below.
They are slightly different from your original plan.
1.Install BDC on the new box.
2.Promote the new Windows NT 4.0 BDC to the PDC, which demotes the PDC to a
BDC.
3.Change the profile server from the former PDC to the new PDC by using
Xcopy.
Xcopy syntax
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/p
roddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/stan
dard/proddocs/en-us/xcopy.asp
Command Line Switches for the XCOPY Command
http://support.microsoft.com/default.aspx?scid=kb;en-us;128756
Note: Please use /x, /o switches to copy security related information. Also
use /s ,/e ,/t to copy the files in subdirectory; use /h to copy files
with hidden and system file attributes;
robocopy.exe is not recommended since the robocopy.exe for the Windows 2003
can't be used at the Windows NT 4 server.
The specific process to change the profile server between two servers is
shown in the last mail.
4.Do a full backup of the former PDC and remove it from the network.
5.Upgrade the new PDC to Windows Server 2003.
If you want to expand the boot partition, please refer to the following KB:
325857 How To Expand the Boot Partition During a Windows Server 2003 Upgrade
http://support.microsoft.com/?id=325857
6.Rename the win 2003 member server with the old PDC's name and IP adress.
7.Promote the win 2003 member server to DC.
Hope it helps. Any update, let us get in touch!
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. |
|
| Back to top |
|
 |
|
|
|
|