RE: FSMT Not Listing All Shares

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Hello,

Thanks for posting!

Yes,the RoboCopy is unable maintain the share properties and you may want
to recreate the share permission. 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.

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 Not Listing All Shares
| thread-index: AcYwk2byUPrULD9jRFmhU2TABPbRUg==
| X-WBNR-Posting-Host: 66.83.246.26
| From: "=?Utf-8?B?Sm9lIEhvZ2dvb2Q=?=" <jhoggood@xxxxxxxxxxxx>
| References: <27674012-CE25-49AC-8CD8-3830D4BD809E@xxxxxxxxxxxxx>
| Subject: RE: FSMT Not Listing All Shares
| Date: Mon, 13 Feb 2006 03:48:27 -0800
| Lines: 24
| Message-ID: <7586D96E-21D8-4642-8D69-939C2E85985C@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.0
| Newsgroups: microsoft.public.windows.server.migration
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:22444
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| I am copying shares from MachineA (D:\users...) to MachineB (C:\users..)
so
| just can't copy HKLM\CurrentControlSet\LanManServer\Shares\...
|
| I tried using Robocopy but it doesn't support share re-creation on the
| target machine it appears.
|
| --
| Joe Hoggood
|
|
| "Joe Hoggood" wrote:
|
| > I am using FSMT to migration from a Windows 2000 SP4 domain member
server to
| > a Windows 2003 domain member server. I am not using DFS Consolidation
Roots
| > as both machines run Windows Standard Edition not Enterprise so I am
only
| > using the FS Migration Wizard.
| >
| > When I use FS Migration Wizard and select my "Source" server to migrate
it
| > connects to that server but only shows a limited set of hidden shares
but not
| > 100+ of my other user hidden shares.
| >
| > Any ideas why this behavior?
| > --
| > Joe Hoggood
|

.



Relevant Pages

  • RE: issues authentication w/2003 server AND SP1, IIS 6, FPSE 2002
    ... Server 2003 with Service Pack 1. ... In Registry Editor, locate and then click the following registry key: ... > following article number to view the article in the Microsoft Knowledge Base: ...
    (microsoft.public.frontpage.extensions.windowsnt)
  • RE: I cant run the routing and remote access wizard
    ... Since i sent you the emails - hope you received them - I have run a registry ... http://localhost on the server box. ... Please enable IIS logging and reproduced the issue and collect IIS log ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote access to FP Administration fails
    ... This issue occurs if you install Microsoft ... IIS6 and 2002 extensions that shipped with 2003 server after the application ... Method 1: Disable the loopback check ... In Registry Editor, locate and then click the following registry key: ...
    (microsoft.public.frontpage.extensions.windowsnt)
  • issues authentication w/2003 server AND SP1, IIS 6, FPSE 2002
    ... This issue occurs if you install Microsoft ... IIS6 and 2002 extensions that shipped with 2003 server after the application ... In Registry Editor, locate and then click the following registry key: ... Quit Registry Editor, ...
    (microsoft.public.frontpage.extensions.windowsnt)
  • RE: FPSE on 2003 SP1
    ... This issue occurs if you install Microsoft ... IIS6 and 2002 extensions that shipped with 2003 server after the application ... In Registry Editor, locate and then click the following registry key: ... Quit Registry Editor, ...
    (microsoft.public.frontpage.extensions.windowsnt)