Once the data copy is done and all files and subfolders with their permissions have been mirrored and verified to be matching, network folder share information might needed to be applied from the Source server to the Target server.
However, the share information is actually stored in the Windows Registry not on files or folders. To copy share information from a server to another server, a key in the Windows Registry needs to be exported and imported in the new server.
The simple method below will show you how to copy all the shares and share security from one server to another. It involves exporting a Windows Registry key to a file and then importing this file into the new server.
If possible, try to keep the drive letter the same on your new server compared to where the shares were on your old server. If you cannot, this can be changed later with an extra step.
Step 1
On your old server, export the following Windows Registry key to a file using the program Regedit.
HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>
Services>LanmanServer>Shares
This registry key lists all the shares that are present. Right click the Shares key and select �Export� in Regedit. Give it any name you like and save it to an area accessible from your new server.
Step 2
Now go to your new server and right click the registry file you have exported in Step 1 and select �Merge�. All the share information will be imported in your new server. If the new server uses the same drive letter, then just restart the server (or you can start and stop the Server service: enter Net Stop Server and then Net Start Server at the command prompt).
Step 3
If the drive on the new server where the Shares are has a different drive letter compared to the old server, then you need to do the following. On the new server, navigate to the same key using Regedit:
HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>
Services>LanmanServer>Shares
Now on the right hand side you can see the Shares. To change the drive letter of a share simply double click the share in question and then locate the section labelled �path� and change the drive letter to the drive letter of your new file server.
Migrating or copying files to another server and retaining the permissions is a common task when migrating a file server.
If all permissions are successfully retained it will make the migration seamless and nobody will ever notice that a migration has taken place.
If there are shared folders and with different permissions, re-sharing the folder by scratch is just time consuming and giving access denied to users will be inevitable.
But how to copy files and folders, like it was exactly done on the old server?
In Windows environment, just 3 steps are needed. 3 steps sound easy and quick.
Steps below will work for NTFS permissions and folder access rights solely depends on it.
a. Copy the files to the new server and retaining its permissions while files and folders are being copied
b. Export the shares registry (old server)
c. Import the shares registry (new server)
The link below from Microsoft website shows how xcopy can copy folder and retain the permissions.
//support.microsoft.com/en-sg/help/323007/how-to-copy-a-folder-to-another-folder-and-retain-its-permissions
Copy folder and retain permissions:
At command prompt:
Type: xcopy source destination /O /X /E /H /K
Example:
Type: xcopy c:\olddocs c:\newdocs /O /X /E /H /K, and then press ENTER, where olddocs is the source folder and newdocs is the destination folder.
Xcopy switches have the following effects:
/E - Copies folders and subfolders, including empty ones.
/H - Copies hidden and system files also.
/K - Copies attributes. Typically, Xcopy resets read-only attributes.
/O - Copies file ownership and ACL information.
/X - Copies file audit settings (implies /O).
Aside from Xcopy, robocopy will come in handy to copy files and folders and retaining the permissions.
Robocopy syntax:
robocopy “source address” “destination address” *.* /mir /sec /log:migrate.log
Technet link below shows how to export the share registry:
//social.technet.microsoft.com/wiki/contents/articles/408.how-to-back-up-and-restore-ntfs-and-share-permissions.aspx
To be done on the old server:
reg export HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares shareperms.reg
To be done on the new server:
reg import HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares shareperms.reg
After importing the registry, restart the server and check whether folders are shared or not. If everything goes well, shared folders will automatically appear and it will be ready for everyone to access.
To successfully migrate and automatically share the folder exactly as it was on the old server, drive letter and parent folder name should be the same or else it won’t match the imported registry settings.
================================
Free Android Apps:
Click links below to find out more:
Excel Keyboard guide:
//play.google.com/store/apps/details?id=chrisjoms.myexcelapplicationguide
Heaven's Dew Fall Prayer app for Android :
//play.google.com/store/apps/details?id=soulrefresh.beautiful.prayer
Catholic Rosary Guide for Android:
Pray the Rosary every day, countless blessings will be showered upon your life if you recite the Rosary faithfully.
//play.google.com/store/apps/details?id=com.myrosaryapp
Divine Mercy Chaplet Guide (A Powerful prayer) BFF = Be Filled Faith:
//play.google.com/store/apps/details?id=com.dmercyapp
Share
Labels
Batch File Elevated CMD Robocopy Windows Registry Windows ServerLabels: Batch File Elevated CMD Robocopy Windows Registry Windows Server
Share
How to check office version from command line
April 26, 2020
The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find /i "Directory of" Above command assumes that program files is on C: drive. Sample Outpu
Share
Post a CommentRead more
WMIC get computer name
October 30, 2013
WMIC get computer model, manufacturer, computer name and username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type: wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A
Share
Post a CommentRead more