Hello,
Thanks for response!
You may run Run the DFS Consolidation Root Wizard on the cluster which has
installed the FSMT and then run FSMT.
I would like to provide you with the following example for your reference:
1. Install the FSMT on one of the cluster nodes. The detailed download
information
can be acquired from the following link:
Microsoft File Server Migration Toolkit
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfsc.mspx
2. Change the computer name of the original file server prior to the
following
action.
3. Please open the cluster administrator on the cluster node and create one
group
for DFS root resources. After creating the group, we should create physical
disk,
IP address and Network name resources in it.
4. Run the DFS Consolidation Root Wizard on the cluster, which has
installed the
FSMT (It will be installed automatically after installing FSMT).
5. Filled in the DFS root server as the IP address of local machine.
6. In the ¡°DFS Root Folders Location, please fill in the local path of the
folder
as the drive letter of the share disk (for example G:\roots), which is
planned to
maintain the DFS Root folder.
7. In the ¡°Server to Consolidate¡±, click Add Server:
a. In the original name, fill in the original computer name of the file
server
before changing the name.
b. In the current name, fill in the current computer name of the file
server.
c. Click Next until it is finished.
8. Open cluster administrator and create another group to hold the file
share
resources. Please also create physical disk (this share disk is used for
holding
share data), IP address and Network name resources in this group.
9. Start FSMT.
10. Click New in the ¡°Welcome to File Server Migration Wizard¡± and click
Next.
11. In the project name and location, click Next if we do not need to
change the
location of the project file.
12. In the DFS Consolidation Root server¡±, fill in the Server as the
server name
of the local machine and click Next.
13. In the Default Location for Migrated Shared Folders¡±, fill in the
location as
the share disk drive letter and click Next. This share disk is used for
holding the
share data.
14. Click Finish to complete the configuration.
15. In the setup phase, please choose the share data, we are planning to
migrate.
16. Click Continue until all the phases are finished.
17. Test whether we can access the files share with the original UNC path.
18. Repeat the steps from 3 to 17 for the other file servers, which need
to
migrate.
Hope the information helps.
Best 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.
--------------------
| Thread-Topic: FSMT Question
| thread-index: AcYrHbqjNhjtMhozSgWR1QXO92Pl5Q==
| X-WBNR-Posting-Host: 65.40.43.165
| From: =?Utf-8?B?Y3Rjb25saW5l?= <***@discussions.microsoft.com>
| References: <C1D1EF5A-0608-4B47-AE10-***@microsoft.com>
<***@TK2MSFTNGXA02.phx.gbl>
| Subject: RE: FSMT Question
| Date: Mon, 6 Feb 2006 05:03:31 -0800
| Lines: 105
| Message-ID: <6F63531F-BAA8-41EE-B860-***@microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.windows.server.migration
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.windows.server.migration:22325
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| Thank you for the information. I have actually already read these
articles,
| but I was looking for something more specific. I guess my main question
is
| which tool should I use first? Do I run the Consildation Root Wizard and
| then run the File Server Migration tool?
|
| Can someone please provide me very specific instructions? Thanks.
|
| "Jason Tan (MSFT)" wrote:
|
| > Hello,
| >
| > Thanks for posting!
| >
| > I suggest you atttempt to use FSMT to achieve the goal. FSMT helps the
| > system administrator configure new functionality in Distributed File
System
| > (DFS) to maintain the original Universal Naming Convention (UNC) path
of
| > files after they are moved to a new server. This reduces the impact of
file
| > server consolidation and migration, saves end users time spent
searching
| > for files, and ensures that line-of-business applications keep running.
| >
| > For more information please refer to the following article:
| >
| > Microsoft File Server Migration Toolkit
| >
<http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfsc.msp
| > x>
| >
| > FAQ on FSMT:
| >
<http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_faq
| > s.mspx>
| >
| > White Paper:
| >
<http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_ove
| > rview.mspx>
| >
| > Hope the information helps.
| >
| > Best 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.
| >
| >
| >
| > --------------------
| > | Thread-Topic: FSMT Question
| > | thread-index: AcYqYYu3MyxBa0H2QWCre9AXQ770aA==
| > | X-WBNR-Posting-Host: 65.40.43.165
| > | From: =?Utf-8?B?Y3Rjb25saW5l?= <***@discussions.microsoft.com>
| > | Subject: FSMT Question
| > | Date: Sun, 5 Feb 2006 06:36:27 -0800
| > | Lines: 16
| > | Message-ID: <C1D1EF5A-0608-4B47-AE10-***@microsoft.com>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | charset="Utf-8"
| > | Content-Transfer-Encoding: 7bit
| > | X-Newsreader: Microsoft CDO for Windows 2000
| > | Content-Class: urn:content-classes:message
| > | Importance: normal
| > | Priority: normal
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| > | Newsgroups: microsoft.public.windows.server.migration
| > | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| > | Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| > | Xref: TK2MSFTNGXA02.phx.gbl
| > microsoft.public.windows.server.migration:22310
| > | X-Tomcat-NG: microsoft.public.windows.server.migration
| > |
| > | I have a project where I need to move data from several seperate
Windows
| > 2000
| > | file servers to a couple of NAS units. We are not currently using
dfs
| > and we
| > | would like to use dfs on the new NAS units. I know that in order to
| > minimize
| > | the impact on end users, we need to use the FSMT and Consolidation
Root
| > | Wizard.
| > |
| > | Can someone provide me step by step instructions on how to proceed?
Or
| > if
| > | you know of an article that provides step by step instructions, that
| > would be
| > | great. My first question is which tool do I run first (FSMT or CRW)?
| > |
| > | The desired end result is to have all data on the two 1.6TB NAS units
| > which
| > | will be redundant to each other using dfs. The NAS units are running
| > Windows
| > | 2003 Storage Server Standard. I also setup another server running
| > Windows
| > | 2003 Enterprise because I read that this was a prerequisite for the
CRW.
| > |
| > | Any help would be greatly appreciated.
| > |
| >
| >
|