I want to switch from the old file server to a new file server for the success of my business, but I don't know how to use file server migration toolkit.
What is a file server?
Every person or business wants to store important data for years. When talking about companies, they create a lot of data each day for which you need to maintain a digital record of data and need to store it as well.
So, the companies used on-premises file servers or cloud storage to keep the data safe for the long term. This is what is known as a file server. From time to time, due to advancements in technology and changes in the operating system, you may need to migrate file server from one source to other.
File server migration is not a difficult task, but if you are new to this, you may find it a bit tricky and may feel it is impossible within a production environment. In this article, we will help you with how to use the file migration toolkit. Also, we will discuss the top three file server migration tool kit.
Take a look!
There are many file server migration tools, but here we have listed the top three file server migration toolkit. You can use any of the following to migrate file server from 2008 R2 to 2012 R2, windows 2003 to 2012, and more.
Among many other file server migration tools, EaseUSTodoPCTransis at our top list for its easiness and excellence. This file server transfer tool can meet your needs and can help you with everything in between file selection to account settings.
What's more, this file server migration tool allows you to transfer settings, applications, and even user profiles. The best part is that it supports the most common applications/programs, such as MS Office, Photoshop, Adobe software, Dropbox, etc.
ZinstallWinServis another file server transfer tool that can migrate applications, settings, profiles, data, and more from one Server to another. This tool is compatible with Windows Server 2019, 2016, 2012, 2008, and 2003.
Third, on our list is Microsoft's Storage Migration Service. It can migrate file servers from Windows Server 2008/R2. This is a type of graphical tool that inventories data on Windows as well as Linux servers and then transfer it to the newer servers.
With it, you are able to create a new server, either physical or virtual.
When dealing with the installation of windows server migration tools, both the destination and source server devices need a copy of the tools to act on migration. Here are the steps wise techniques to follow to install the windows server migration tools on the destination and source server.
When you want to migrate file server 2008 R2 to 2016, you will need to follow the below steps. First of all, you need to install the file server migration toolkit on your source and destination.
Make sure, when installing the windows server migration tools, both the destination, as well as source server devices should have a similar copy of the tool.
Once you have installed the migration tool, a deployment folder is created on the device. This folder will help with the complete process of data migration.
Below are the steps to create a deployment folder on the destination device:
Once you created the deployment folder on the destination device, copy it to the source device's local drive. You have to ensure that the architecture of the deployment folder is compatible with the operating system of the source.
Following are the steps that you should follow for this.
So this is how you are able to migrate file servers from 2008 R2 to 2016
As of January 2020, Windows Server 2008 and Windows Server 2008 R2 are out of support. Therefore, you need to migrate the file server from 2008 R2 to 2012 R2. Here are the steps that you can follow to migrate the file server from 2008 R2 to 2012 R2.
Step 1: Prepare Windows Server 2012 R2
First, you will need to prepare Windows Server 2012 R12. For this, open a PowerShell prompt as an administrator, and type Install-WindowsFeature Migration –ComputerName
With this, you are able to install the necessary feature on your Windows Server 2012 R2.
Step 2: Create a Deployment Folder pt1
Now, you can use the smigdeploy.exe tool to create your deployment share on the Server 2012 R2 that will be used by server 2008.
For this, open a command prompt as administrator, and type in: cd%Windir%\System32\ServerMigrationTools\
Step 3: Create a Deployment Folder pt2
Open a command prompt and type: SmigDeploy.exe /package /architecture amd64 /os WS08 /path
Step 4: Run SMIGDEPLOY.EXE on 200 8 server
Open a command prompt on the Windows 8 server as an admin. And, type: \smigdeploy.exe to change the CD to the directory
Step 5: Back to 2012 R2 Server
On your Server 2012 R2, open PowerShell and receive the smigdeploy.exe data from the source machine.
First, import the migration snappin: add-pssnapinmicrosoft.windows.servermanager.migration and then press enter.
Step 6: Setup Recieve-SmigServerData
First, it wouldn't hurt for you to set up your folder structure to be the same as what's on the source server. So go ahead and create those if you want. After that's done, on the Server 2012 R2 type: Receive-SmigServerData.
After this, when you tap enter, this will activate the server to receive data.
Step 7: Setup Send-SmigServerData
On the 2008 R2 server, in the window that opened after you ran smigdeploy.exe, and type: Send-SmigServerData -ComputerName
Enter admin account password and press enter.
In the end, you can now see the file server sharing. Once done, check the W12 R2 server by typing in the PowerShell prompt: get-smbshare.
In the case that you want to migrate some confidential files from PC to PC, it is strongly recommended that you use Wondershare UBackit. It is backup software with secure file migration features. The software is compatible with Windows 10/8/8.1/7. You can check for the file migration guide.
We hope that from the above article, you have gained knowledge on how to migrate file server from one server to other. For file server migration, all you need to do is to install the file server migration toolkit on your source and destination. You can also use third-party tool like AOMEI backupper for file data migration between two servers.