If you need to complete any of the following procedures, you can save the share names that exist on the original Windows installation, including any permissions assigned to those shares:
Windows Server 2012 is now available!
It offers businesses and service providers a scalable, dynamic, and multitenant-aware cloud-optimized infrastructure.
Windows Server 2012 helps organizations connect securely across premises and helps IT Professionals to respond to business needs faster and more efficiently.
-
Reinstall Windows over an existing installation (a clean install, not an upgrade).
-
Move all of your data drives from one server to another.
-
Install Windows to another folder or drive on a computer that already has Windows installed.
To save only the existing share names and their permissions on Windows NT4.0/W2K/XP/2003 follow these steps.
Method #1
-
On the existing Windows installation that contains the share names and permissions that you want to save, start Registry Editor (Regedt32.exe or Regedit.exe).
-
Go to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares |
-
Click Save Key on the Registry menu.
-
Type a new file name (a file extension is not necessary), and then save the file to a floppy disk.
-
Reinstall Windows (if you have to, don't do it just because I said so...).
-
Run Registry Editor (Regedt32.exe or Regedit.exe).
-
Go to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares |
-
Click Restore on the Registry menu.
-
Type the path and file name of the file that you saved in steps 3 and 4.
Caution: This step overrides the shares that already exist on the Windows computer with the share names and permissions that exist in the file you are restoring. You are warned about this before you restore the key.
Note: You can also do the trick by double-clicking the registry file you've created in step 3, if you've used Regedit and if the file extension is .REG.
-
Restart the server.
Note: After you complete this procedure, if you decide that you should not have restored the Shares key, restart the computer and press the SPACEBAR to use the last known good configuration. After you restore the shares key, the shares can be used by network clients. If you run the net shares command on the server, the server displays the shares; however, File Manager does not display the shares. To make File Manager aware of the newly restored shares, create any new share on the server. File Manager displays all of the other shares after you restart the server or stop and restart the Server service.
Only permissions for domain users are restored. If a local user was created in the previous Windows NT installation, that local user's unique security identifier (SID) is lost. NTFS permissions on folders and files are not affected when you save and restore the shares key.
Method #2
Use the NET SHARE program to create the new share structure, then use the PERMCOPY program found in the Windows 2000 Resource Kit to copy share permissions. The syntax is quite easy:
PERMCOPY //SourceServer ShareName //DestinationServer ShareName
