RE: File Server Migration Toolkit - relocating shares
- From: v-jasont@xxxxxxxxxxxxxxxxxxxx (Jason Tan (MSFT))
- Date: Tue, 21 Mar 2006 09:04:12 GMT
Hello,
Thanks for posting!
Based on the current situation, we may use the Windows 2000 Resource Kit
tool robocopy.exe to copy the folders with their NTFS permissions.
Robocopy
<http://technet2.microsoft.com/WindowsServer/f/?en/Library/ed34eee3-7dbd-44c
6-8fb8-8b8b2c6f06dc1033.mspx>
Note: FSMT also will not migrate the shares. However, you can simply
migrate shares through registry key.
Windows stores all share information in the registry. This allows you to
export the information from one machine and import it into another. To
access the share information, open the Registry Editor by going to Start |
Run, typing regedt32.exe, and clicking OK. Then, navigate to the following
key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares
This registry key lists all shares. To move a share from one server to
another, follow these steps:
-In the Registry Editor, go to Registry | Export Registry File.
-Save the settings in a .reg file by selecting a location and clicking
Save.
-Close the Registry Editor.
-Copy the .reg file to the destination computer.
-Right-click the file, and select Merge.
-In order for the shares to show up, you'll need to restart the machine. Or
you can start and stop the server service (enter -Net Stop Server and then
Net Start Server at the command prompt) and other services that require
server service.
Note: Be aware that this procedure will migrate all of the shares from the
source machine. In addition, you must store the folders on the same drive
as before. For example, if you copied the C:\test share from one machine,
you must copy the folder to the same location (C:\test) on the destination
machine.
Note: Editing the registry is risky, so be sure you have a verified backup
before making any changes.
This response contains a reference to a third party World Wide Web site.
Microsoft is providing this information as a convenience to you. Microsoft
does not control these sites and has not tested any software or information
found on these sites; therefore, Microsoft cannot make any representations
regarding the quality, safety, or suitability of any software or
information found there. There are inherent dangers in the use of any
software found on the Internet, and Microsoft cautions you to make sure
that you completely understand the risk before retrieving any software from
the Internet.
Detailed information for you reference:
<http://techrepublic.com.com/5100-1035_11-5692540.html#>
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: File Server Migration Toolkit - relocating shares
| thread-index: AcZMLkX9Bwn989LrSayFix3lQKLHSg==
| X-WBNR-Posting-Host: 157.160.36.102
| From: =?Utf-8?B?cGFvdXRkb29yc21hbg==?=
<paoutdoorsman@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: File Server Migration Toolkit - relocating shares
| Date: Mon, 20 Mar 2006 06:55:05 -0800
| Lines: 23
| Message-ID: <27BCCB70-7B3E-4A0E-BF8B-A6655956BA32@xxxxxxxxxxxxx>
| 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.1830
| Newsgroups: microsoft.public.windows.server.migration
| Path: TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA03.phx.gbl
microsoft.public.windows.server.migration:22990
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| Hi all, I've been trying to relocate 1200 shares on a Windows 2003
Enterprise
| file server and I'm really struggling to make this happen.
|
| Here is my scenario; My shares are currently located on local drives on
the
| file server. I now have a fiber connection to a Hitachi SAN and need to
| relocate these shares to the SAN - preferably without having to recreate
| every share.
|
| When I test moving a smaller number of shares with the file server
migration
| wizard, a new top level folder is added equal to the file server name,
and
| each share name is appended with _file server name. I really do not want
| this to happen and this is the behavior I'd like to change.
|
| After reading the FAQ, I've tried numerous times to modify the .xml file
to
| eliminate the both the share name changes and the top level folder
addition,
| but is still adds them in regardless of the fact that I eliminated them
from
| the xml file.
|
| Link to FAQ
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_faqs
mspx
|
| I must really be missing something because I can't imagine this should be
a
| difficult task. Can anyone help?
|
.
- Prev by Date: RE: NT 4.0 and Server 2003 network configuration problems
- Next by Date: RE: Novell Migration
- Previous by thread: RE: In-place Upgrade & Join as a Child Domain
- Next by thread: RE: File Server Migration Toolkit - relocating shares
- Index(es):
Relevant Pages
|
