- Remove From My Forums
-
Вопрос
-
День добрый.
Поделитесь опытом как правильно перевести домен на windows server 2019,
На данный момент есть win 2003 котроллер домена и планируется его миграция на win 2019
Подскажите как это правильно сделать?
Ответы
-
Вот
пример обновления до 2016. Так как в 2019 почти никаких измений не было, то статья справделива и для 2019. Главное — перед обновлением сделать
бекап.-
Предложено в качестве ответа
16 апреля 2019 г. 10:29
-
Помечено в качестве ответа
Petko KrushevMicrosoft contingent staff, Owner
19 апреля 2019 г. 8:26
-
Предложено в качестве ответа
One of the fantastic new features of Windows Server 2019 is the Storage Migration service that allows easily migrating off an old server. Over the years Microsoft has introduced tools that allowed copying files and such, but there was always part of the desired functionality that you would want that was left out. Administrators have long wanted a tool that could fully automated the process of migrating off an old server over to a new server. This includes the ability to both move the files, shares, and permissions, but also assuming identity of the old server in cases where this is desired. The new Storage Migration tool found in the Windows Admin Center provides a powerful tool that allows this ability in an automated fashion. In this post, we will take a look at how to Migrate from Windows Server 2003 to Windows Server 2019 with Storage Migration.
Observations in Testing
So to begin with, I want to make a few observations of various things I noticed in testing. Keep in mind the testing I was able to perform involved the Windows Insider releases along with taking a look as well as the RTM code in Eval form. One of the interesting bits that I observed was the RTM code was missing the Storage Migration service and Proxy service. Additionally, the Datacenter release, in various forms in the Insider release did not have the Storage Migration Service.
The release and testing that I performed was in the form of the Windows Insider build 17744.1001 which is the latest version of the Windows insider release. Also, I noticed the Preview release of the Windows Admin center 1808 did not have the extension for the Storage Migration service by default. The test that I ran involved using the 1809 release of the Windows Admin Center on top of the Standard edition version of Windows Server 2019 17744 build. As you will see, I ran into some hurdles with testing Windows 2003 migration. Of course, everything is still so new with the Storage Migration service that it is very lightly documented if at all at this point.
In testing I had the following:
- Windows 2003 R2 x64 build – no patches installed
- Windows Server 2019 Standard – 17744 build
Let’s take a look at the process of running the storage migration service and the requirements and the outcome for me in the lab.
The first thing I needed to do is install the Storage Migration Service and Storage Migration Service Proxy on the 17744 build server.
You can see it from a different view here in PowerShell.
Add the required subfeatures needed…
Added and ready to install…
Feature installation is successful. Now back to Windows Admin Center.
You now see the Storage Migration Service listed in Windows Admin Center.
WAC displays the overview of the process including the steps:
- Inventory
- Transfer
- Cut over
Create a New job in the Storage Migration Service dashboard.
Name the new job.
The first of the three step process involves the Inventory devices step. Enter credentials here.
Add the source device to scan. Click the Add a device button.
Add the source device – here using the FQDN.
We need to scan the source device for shares, files, etc. Click the Start scan button.
The initial scan for me errored out. Just working on a theory I tried to simply connect to the admin share of the Windows 2003 server and received the following error, related to SMB 1.0.
Enabling SMB 1.0/CIFS File Sharing Support
Working on a hunch here this is why the Storage Migration Service failed to inventory the service. I decided to add the SMB 1.0/CIFS support for Storage Migration to see if it gets me further.
After adding SMB 1.0 you will need to restart.
After restarting, i tried again and was able to successfully connect to Windows 2003.
Now, the inventory process is successful.
Moving along to the Transfer data step, enter the credentials.
Enter the destination device name and scan the device.
After scanning, you will see the list of shares, path, type, size and you can choose to include the share or not. Also, you can map the destination server drive if different.
Adjust transfer settings including retries, etc.
Validate the settings by clicking the Validate button
Next, you are down to the Start the transfer step. Click the Start transfer button.
In trying multiple times to get this to work with Windows 2003, I ran into the error below: Couldn’t transfer storage on any of the endpoints. Things tried below:
- Enabled server component of SMB 1.0 (didn’t think this was necessary but tried it anyway)
- Disabled UAC in Windows Server 2019
- Rebooted Windows 2003 and Windows Server 2019 servers
- Tried different files inside the shares
- Added a new virtual disk and targeted this drive instead of the system drive.
The weird thing is the folders get created and files, but they are “0” file size.
The following error is displayed in event view for Windows Server 2019.
I am sure I am missing something required here with Windows 2003, however, there is literally no information out there at this point for this functionality so working on trial and error. I will keep this post updated as I continue to test.
So to feel good about at least getting to test the functionality, I tried Windows Server 2019 to Windows Server 2019. As you can see below, the transfer of the same files is successful, albeit on the Windows Server 2019 platform.
Shares are properly created and NTFS permissions are brought across as well.
Now, for the cutover stage. This allows actually assuming the identity of the old server if you need. Again, credentials.
Configure what you want to do with the network. You can assume IP as well if you want. Additionally, you can choose to generate a random computer name or specify what you want the old server to be renamed too after the new server assumes identity.
Adjust the cutover time.
Validate the source and destination.
Start the cutover process. This will reboot both servers a few times as each identity is changed.
After the cutover process is successful. I was able to verify that the old server was renamed and the new server assumed the identity of the old server. Very cool!
Takeaways
I generally don’t like to create posts showing things I couldn’t get to work, however, this is showing preview functionality at this point and I know I am missing something for Windows 2003 functionality. It is great to see that Microsoft is working on making this process to Migrate from Windows Server 2003 to Windows Server 2019 with Storage Migration as simple and easy as they can. There is a ton of Windows 2003 servers still out in production environments according to Microsoft! One documented and ironed out, this will eliminate all excuses to migrate off Windows 2003 up to Windows Server 2019 for file server platforms. More to come…again, stay tuned to the post as I will keep it updated with findings. Please comment if you have been experimenting with this also and have the key here that I am missing.
- Remove From My Forums
-
Question
-
Hi
I need to migrate 2003 server(DC) to 2019 server what is the best practice to do the same.
Thanks
Answers
-
Hi,
in order to migrate from 2003 to 2019 you have to meet the requirements for 2019:
- SYSVOL must be migrated from FRS (2003) to DFS-R
- Domain-Functional Level must be at least Windows Server 2008 R2
- AD-Forest Functional Level must be at least Windows Server 2008 R2
those are the basics. In Addition you need to check if your 3rd Party Tools as well as Exchange (if you have it On-Prem) already meet the requirements for a supported state.
If you have performed the above mentioned steps you can easily upgrade your DC´s. Here´s an article which may help you in upgrading domain controllers:
https://social.technet.microsoft.com/wiki/contents/articles/2903.active-directory-high-level-steps-to-upgrade.aspx
regards, pat
-
Proposed as answer by
Wednesday, October 2, 2019 1:06 PM
-
Marked as answer by
Kawaljit Singh
Wednesday, October 23, 2019 7:58 AM
- Remove From My Forums
-
Question
-
Hi
I need to migrate 2003 server(DC) to 2019 server what is the best practice to do the same.
Thanks
Answers
-
Hi,
in order to migrate from 2003 to 2019 you have to meet the requirements for 2019:
- SYSVOL must be migrated from FRS (2003) to DFS-R
- Domain-Functional Level must be at least Windows Server 2008 R2
- AD-Forest Functional Level must be at least Windows Server 2008 R2
those are the basics. In Addition you need to check if your 3rd Party Tools as well as Exchange (if you have it On-Prem) already meet the requirements for a supported state.
If you have performed the above mentioned steps you can easily upgrade your DC´s. Here´s an article which may help you in upgrading domain controllers:
https://social.technet.microsoft.com/wiki/contents/articles/2903.active-directory-high-level-steps-to-upgrade.aspx
regards, pat
-
Proposed as answer by
Wednesday, October 2, 2019 1:06 PM
-
Marked as answer by
Kawaljit Singh
Wednesday, October 23, 2019 7:58 AM
- Remove From My Forums
-
Question
-
Hi,
We have a domain with 8 domain controller windows 2003.
What’s the best practise to migrate this domain to windows 2019?
Answers
-
Hi,
You can’t migrate directly your domain controller from windows 2003 to windows 2019.
You have to start by migrate you domain controller to windows 2008 R2 or windows 2012 R2 or windows 2016. Then you raise the forest functional level to Windows 2008 R2 and the Sysvol replication from frs to DFS-R.
For your information, to promote the first domain controller on Windows 2019 , forest functional level must be Windows 2008 R2 or higher and the SYSVOL replication system must be DFS-R.
Please don’t forget to mark the correct answer, to help others who have the same issue. Thameur BOURBITA MCSE | MCSA My Blog : http://bourbitathameur.blogspot.fr/
-
Marked as answer by
Saturday, January 18, 2020 7:26 PM
-
Marked as answer by
-
Thank you for your answer.
We are looking to build new domain to simplify the migration process .
What’s the recommended migration process?
-
Marked as answer by
Mamadou.Coulibali
Saturday, January 18, 2020 7:25 PM
-
Marked as answer by
-
Thank you for your answer.
We are looking to build new domain to simplify the migration process .
What’s the recommended migration process?
If you create new domain , you have to migrate all object using ADMT tools and join existing server to new domain. This choice can impact users. For this reason I recommend you to choose the procedure mentioned on my first answer.
Please don’t forget to mark the correct answer, to help others who have the same issue. Thameur BOURBITA MCSE | MCSA My Blog : http://bourbitathameur.blogspot.fr/
-
Marked as answer by
Mamadou.Coulibali
Saturday, January 18, 2020 7:25 PM
-
Marked as answer by
-
You can — assuming you are using Windows Server 2016 LTSC.
Windows Server does not support FRS starting with version 1709 (Semi-Annual Channel)
More at http://patrickvandenborn.blogspot.com/2017/06/windows-server-2016-frs-deprecated-how.html and https://support.microsoft.com/en-us/help/4025991/windows-server-version-1709-no-longer-supports-frs
hth
Marcin
-
Edited by
Marcin PolichtMVP
Monday, January 13, 2020 8:34 PM -
Marked as answer by
Mamadou.Coulibali
Saturday, January 18, 2020 7:25 PM
-
Edited by
-
-
Marked as answer by
Mamadou.Coulibali
Saturday, January 18, 2020 7:25 PM
-
Marked as answer by
-
Agree with Dave .
Yes you can . You can start by upgrade your domain controllers to Windows 2016 before migrate FRS to DFS for sysvol replication and raise the functional level.
Please don’t forget to mark the correct answer, to help others who have the same issue. Thameur BOURBITA MCSE | MCSA My Blog : http://bourbitathameur.blogspot.fr/
-
Marked as answer by
Mamadou.Coulibali
Saturday, January 18, 2020 7:25 PM
-
Marked as answer by
-
Hello,
Thank you for posting in our TechNet forum.
Before we do any changes to our AD environment, we had better to check our AD environment health. So we can try the following steps:1.We need to check if all the DCs works fine, we can run Dcdiag /v on each DC to check.
2. Run Repadmin /showrepl and repadmin /replsum on all DCs to check AD replication status.Besides, I really agree with Mr Thameur and Mr Marcin. If you still have problems, please contact with us.
Best regards,
Jolin
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com.-
Marked as answer by
Mamadou.Coulibali
Saturday, January 18, 2020 7:25 PM
-
Marked as answer by
- Remove From My Forums
-
Question
-
Hi,
We have a domain with 8 domain controller windows 2003.
What’s the best practise to migrate this domain to windows 2019?
Answers
-
Hi,
You can’t migrate directly your domain controller from windows 2003 to windows 2019.
You have to start by migrate you domain controller to windows 2008 R2 or windows 2012 R2 or windows 2016. Then you raise the forest functional level to Windows 2008 R2 and the Sysvol replication from frs to DFS-R.
For your information, to promote the first domain controller on Windows 2019 , forest functional level must be Windows 2008 R2 or higher and the SYSVOL replication system must be DFS-R.
Please don’t forget to mark the correct answer, to help others who have the same issue. Thameur BOURBITA MCSE | MCSA My Blog : http://bourbitathameur.blogspot.fr/
-
Marked as answer by
Saturday, January 18, 2020 7:26 PM
-
Marked as answer by
-
Thank you for your answer.
We are looking to build new domain to simplify the migration process .
What’s the recommended migration process?
-
Marked as answer by
Mamadou.Coulibali
Saturday, January 18, 2020 7:25 PM
-
Marked as answer by
-
Thank you for your answer.
We are looking to build new domain to simplify the migration process .
What’s the recommended migration process?
If you create new domain , you have to migrate all object using ADMT tools and join existing server to new domain. This choice can impact users. For this reason I recommend you to choose the procedure mentioned on my first answer.
Please don’t forget to mark the correct answer, to help others who have the same issue. Thameur BOURBITA MCSE | MCSA My Blog : http://bourbitathameur.blogspot.fr/
-
Marked as answer by
Mamadou.Coulibali
Saturday, January 18, 2020 7:25 PM
-
Marked as answer by
-
You can — assuming you are using Windows Server 2016 LTSC.
Windows Server does not support FRS starting with version 1709 (Semi-Annual Channel)
More at http://patrickvandenborn.blogspot.com/2017/06/windows-server-2016-frs-deprecated-how.html and https://support.microsoft.com/en-us/help/4025991/windows-server-version-1709-no-longer-supports-frs
hth
Marcin
-
Edited by
Marcin PolichtMVP
Monday, January 13, 2020 8:34 PM -
Marked as answer by
Mamadou.Coulibali
Saturday, January 18, 2020 7:25 PM
-
Edited by
-
-
Marked as answer by
Mamadou.Coulibali
Saturday, January 18, 2020 7:25 PM
-
Marked as answer by
-
Agree with Dave .
Yes you can . You can start by upgrade your domain controllers to Windows 2016 before migrate FRS to DFS for sysvol replication and raise the functional level.
Please don’t forget to mark the correct answer, to help others who have the same issue. Thameur BOURBITA MCSE | MCSA My Blog : http://bourbitathameur.blogspot.fr/
-
Marked as answer by
Mamadou.Coulibali
Saturday, January 18, 2020 7:25 PM
-
Marked as answer by
-
Hello,
Thank you for posting in our TechNet forum.
Before we do any changes to our AD environment, we had better to check our AD environment health. So we can try the following steps:1.We need to check if all the DCs works fine, we can run Dcdiag /v on each DC to check.
2. Run Repadmin /showrepl and repadmin /replsum on all DCs to check AD replication status.Besides, I really agree with Mr Thameur and Mr Marcin. If you still have problems, please contact with us.
Best regards,
Jolin
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com.-
Marked as answer by
Mamadou.Coulibali
Saturday, January 18, 2020 7:25 PM
-
Marked as answer by
I have an old Server 2003 domain, and need to install a new server and move all to it. As far as I tried, there i no way to add a new domain controller to 2003 level domain (2008 or higher, only).
The new 2019 server added without issue to old domain, but as it seems there will be no transfer of users and roles to new server.
There is only about 20 users, so I can recreate them, but I am not sure about user’s profiles on their local workstations.
My current idea is to:
- disjoin the new server from domain
- recreate a new old domain
- unjoin users from one domain to the new one
Presumption is that if I use the same username that the old local profile will be pulled in that case?
Any suggestions welcome, I have to start solving this issue his week.
asked Oct 30, 2019 at 12:08
0
The easiest method is to use a in-between OS and do a first step migration, 2003 -> 2008R2, and after to 2019.
Don’t forget when you buy a operating system you have downright right, so yes it’s possible to execute what you are looking for with what you have in hands.
nb; Your method is a good plan if it’s a small domain/shop without Exchange, SQL or any advanced setup as you will break all your security sid by dooing so.
answered Oct 30, 2019 at 12:21
yagmoth555♦yagmoth555
16.5k4 gold badges28 silver badges49 bronze badges
6