31:31 You should answer that lol This is a fantastic video! I have to do exactly this tomorrow, migrate from an old bare metal SBS2011 server to a ESXi Server 2019. Cheers!~
Vikas, this is one of the best Migration videos I have seen. Thank you very much for posting this. Migration is such a critical part when moving things from the old to the new but you made it a lot less painful :-).
This was a good step-by-step. One thing missing is the migration of the DOMAIN (not local) user profiles folder. It is often on the same drive as the OS, but not necessarily. Aside from that, this video seems to cover all the bases.
Hi Vikas, thanks for the video but you didn't do the schema upgrade. So must tell everyone that schema upgrade is very essential. Else its still 2008 R2 schema.
Hi Vikas, Overall the video is good but my question is that you didnt Prepare the AD Schema for Server 2012 R2 by using adprep /forestprep on Server 2008?
Thanks a lot for this very informative video. I have a couple of questions if you don't mind: We have 2 2008 r2 domain controllers, one is primary - DC01 (has all FSMO roles and DHCP server) and another one is secondary - DC02 (not a global catalog). Would this be a proper procedure to move to 2019 DC and to keep the same IP addresses of the old domain controllers? 1) Promote new server 2019 DC and transfer all FSMO roles to it 2) Move DHCP server from DC01 to a freshly promoted 2019 DC 3) Demote DC01 and shut it down 4) Change IP on the new 2019 DC to be the same as DC01 had 5) Promote secondary new 2019 DC 6) Demote DC02 and shut it down 7) Assign IP from DC02 to a new secondary 2019 DC Does this sound correct? I am wondering if this is going to be transparent for the clients or not, and it should not affect our Exchange server? Thanks
Great Tutorial ! 2 things .. 1. After moving dc to new one anything happens in client current login profile ? 2. Can I do this procedure in my running environment ?any impact for the connected clients ??
Thanks Vikas, just two questions: 1. So we have to put the old server's IP for DNS server of new one then change it to itself after joining the domain? 2.Some say to enable SMB 1 in new server first, do we need to do that?
Hi, Thanks for sharing. Just want to know why you don't use the adprep when doing these migrations? Is it necessary to use the adprep or should one just migrate without using the adprep. Thanks, regards, Rakesh
Nice video, but i have to ask why would you disable IPV6 on the new server, per Microsoft over the past recent years you should NOT disable IPV6,a and why would you use a 192.168.01 secondary DNS in the setting, which is why you got the error the 1st time trying to promote the new server. Its also a little misleading when run dcdiag and say everything passed, when clearly some have failed. I know the failed ones dont affect the promotion, but to say everything passed is i bit misleading.
Thank you, but in you missed the First step is to backup the server 2008 . Because in production is accounted as an important step. What do you suggest to do this backup?
Great video!!! Beautiful job. I need to migrate from SBS2011 to Server 2019. I don't want to migrate Exchange mailboxes in SBS2011 to 2019, just users and computers. After migration, I will instal Exchange 2019, and I will recreate mailboxes. Do you think there are some issues? Can you give some suggestions? Thank you in advance!
Hi Vikas - this video is great - I have to do just this to a server later this week. Can you tell me the best way to deal with the logon scripts? Obviosuly the mapped drives batch files will no longer work...obviously i have to copy the data to the new server, will the permissions automatically get copied accross? Do i then have to create new batch files?
Sir this is grade and details to help me migrate new AD server, just got some question hope can get your answer. if after demoted old server and i need to set new server IP to previous old server IP, will it got any problem affect?
Not every device on our network is DHCP. So some will have static IP configurations including static DNS entries on the NIC. Is there a clean way to keep the same IP addresses of the old domain controllers for the new ones?
@@LabsHandsOn I'm so sorry. I have worded that very poorly. What I mean is that my domain controllers are also handling DNS. My DHCP server options specify the DCs as the DNS server addresses. So when a PC joins the network it will be assigned its IP address from the DHCP server but also it will be assigned its DNS servers from the DHCP server as well. The problem is that some PCs (and other devices on the network) are not using DHCP. They are using statically assigned IP addresses (and therefore statically assigned DNS addresses). So this presents a problem in that if I am making new 2019 DCs with different IP addresses then this will only be okay for PCs using DHCP (because I can change the DHCP options). I suppose I could stage the introduction of new 2019 DCs to the network. Once I have built one 2019 DC, I could shut down one of the 2008 DCs and change the IP on the 2019 DC. Is that possible?
Hello, thank you for video. Its very helpful. Can you make video about File Server Migration from 2008R2 to 2019? (I heard something about the File Server Migration Tool.)
@@LabsHandsOn Thank you Sing - as Kezer reference for the file migration is very important if you you will make a video that will be great. 2nd when I am migration from 2008 R2 Enterprise service pack 1 to Standard 2019, Installing AD+DNS on 2019, select (add a domain controller to an existing domain) it giving me an error "Verification of replica failed. The specified domain abc.local is still using FRS file replication service, to replicate the SYSVOL share FRS is deprecated. The server being promoted does not support FRS and cannot be promoted as a replica into specific domain, You must migrate the specific doain to use DFS replication using DFSRMiG command . . . ."
If you also had the DHCP role on the 2008r2 server and would also like that migrated to the new server, would you first migrate DHCP, or after migrating the AD/DNS roles?
Hi! Big thanks for this video! Q1: In the video you go from SBS 2008 R2 to WS Standard 2019, right? We have a Windows Server 2008 without "R2", do we need to do some preperations before we migrate? Q2: In one place in the video it asks for "DS RM password" … are you using the same credentials everywhere, i.e. Administrator and its password, or did you use Another one at that login? Q3: We have about 30 users and have bought lics for them, do we need to add them to the new server in some way before we migrate or is that done afterwards? Are they added at all or is it just a paper with licenses numbers to keep safe? Q4: On the old server we have Azure AD Connect, we will turn it off before migrating. If we install it on the new server afterwards, will it work and match the existing accounts in cloud/O365? Thanks for answers! br /Marcus
I have same questions. I am going to migrate Server 2008 (without R2) to Server 2019. We just haven´t got O365, so Q4 isn´t important to me. If there are answers or if I can send email to anyone, it would be really helpfull. Thank you very much. I know, there is an email address of Vikas, but I don´t want to bother him or write him without his permission. Thanks again.
Hi! Vikas, I did send you a mail, maybe it ended up in junk mail? Anyhow. I had to upgrade/prepare some things on the old server but all error messages gave good indications on what to Google for and old server is now retired! Big thanks for that. Your video was a really good help! Q2/Q3: It was the same password and I have not added any licenses to new server, I just have them on a paper. Br Marcus
Hi, I have successfully migrated my Physical Windows 2008 R2 to Windows 2019 Server to a Hyper-V virtual machine. The only issue I encountered was when I was decommissioning the Physical Windows 2008 R2 DC it gave me an error "Active Directory Domain Services could not transfer remaining data in directory partition" "The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles." I have managed to resolve this issue and my Virtual Domain Controller in running smoothly and wanted to share this to people who are experiencing similar issues on how to resolve this problem. The correct setting for the Infrastructure master FSMO role holder can be found by doing the following from the domain controller that you are trying to demote. 1. The correct setting can be found by going to start>run and typing adsiedit.msc 2. Then right click on ASDI Edit and click Connect to. 3. Select the radio button to Select a well known Naming Context. Then select the Default naming context and click OK. 4. Click on DC=YOURDOMAIN,DC=Local. 5. Find CN=Infrastructure which should be separate entry at the bottom, then double click on it. 6. Double click on the fSMORoleOwner attribute and copy the contents. 7. Click Cancel and Cancel again. Change the incorrect setting Again the below should be done from the domain controller that you are trying to demote. 1. Go to start>run and type adsiedit.msc 2. Then right click on ASDI Edit and click Connect to. 3. It is important that you perform the next few steps accurately or you will see the wrong setting (there is more than one Infrastructure record!). Click ‘Select or type a Distinguished Name or Naming Context’. 4. In the box type: DC=DomainDNSZones,DC=Domain,DC=Local where DC=Domain,DC=Local is the distinguished name for your domain. Then click OK. 5. Click on DC=YOURDOMAIN,DC=Local. 6. Find CN=Infrastructure which should be separate entry at the bottom, then double click on it. 7. Then find the attribute fSMORoleOwner and double click on it. Paste the contents from the correct entry that you just copied above. 8. Then click OK and OK again. 9. Repeat steps 1-8 but instead of connecting to DC=DomainDNSZones,DC=Domain,DC=Local connect to: DC=ForestDNSZones,DC=Domain,DC=Local Thanks again for a great video that you posted.
Hi Vikas, thanks for the video. I have done the migration, but having issue on new DC server 2019, where the network shows private network instead domain.local Can you please suggest how to fix it or why its happening?
Hello Vikas, I have as VM Windows server 2008 R2 as DC runing on host over ESxi software. I would like to migrate this VM to physical server with Windows Server 2019 standard. Is there any difference in procedure from you're video? Thanks
wether don't need to set the adprep in the first settings for all migrating DC? i try on lab and see you video migrating form 2008 to 2016. but im 2008 to 2012. but failed. error demoted and etc. i dnt know why
hello vikas - thanks for the awesome tutorial - i've successfully upgraded my domain from on-prem to vms sitting on azure, - what is the best next step to migrate on-prem exchange to 0365? - also is it good idea to have 2nd dc and 2nd dns on prem? - my current domain have 500 users and mailboxes - thanks
Thanks.. Glad to know you like it. for On-Prem to O365.. Raise case with O365 support team... They will check your infra and give you plan for migration as well.
@@LabsHandsOn hi I really need your help. I want to transfer a 2008 server to another new 2019 . The person that did it before idk what he did .none of the pcs in the office belongs to a domain. When I try adprep / forest don't work. Is there any way to clone it to the new server?
I have a doubt here before migration we need to prepare the 2008 AD for 2019 AD migration right? I mean schema version upgrade from 47 to 88, forest prep, domain prep and gpprep. Please anyone clarify here
31:31 You should answer that lol
This is a fantastic video! I have to do exactly this tomorrow, migrate from an old bare metal SBS2011 server to a ESXi Server 2019. Cheers!~
Vikas, this is one of the best Migration videos I have seen. Thank you very much for posting this. Migration is such a critical part when moving things from the old to the new but you made it a lot less painful :-).
This was a good step-by-step. One thing missing is the migration of the DOMAIN (not local) user profiles folder. It is often on the same drive as the OS, but not necessarily. Aside from that, this video seems to cover all the bases.
I'm from Brazil and your video helped me a lot
Very God !!
Glad it helped!
Great video!!! Worked flawlessly like a charm!
Glad it helped!
Currently planning on migrating this is so helpful thank you
Thanks, Glad to know you like this video.
To verify DNS post DC-promotion it's also important you check the DC is listed as a Name Server.
Thank you for sharing.Good to have you
Thanks Glad to know you like it
was the domain function level of your AD set at 2008 prior to introducing the 2019 DC into the domain? Great video by the way, very informative.
Yes, AD and Forest Level was Server 2008R2
Excellent video bud! Keep up the great work!!
Thanks for the visit
Hi Vikas, thanks for the video but you didn't do the schema upgrade. So must tell everyone that schema upgrade is very essential. Else its still 2008 R2 schema.
Thanks, Glad to know you like this video. Thanks for your suggestion.
Hi Vikas,
Overall the video is good but my question is that you didnt Prepare the AD Schema for Server 2012 R2 by using adprep /forestprep on Server 2008?
Thanks
Does not required.... Follow my videos. You can will during adding new DC its doing the same.
Thanks a lot for this very informative video. I have a couple of questions if you don't mind:
We have 2 2008 r2 domain controllers, one is primary - DC01 (has all FSMO roles and DHCP server) and another one is secondary - DC02 (not a global catalog).
Would this be a proper procedure to move to 2019 DC and to keep the same IP addresses of the old domain controllers?
1) Promote new server 2019 DC and transfer all FSMO roles to it
2) Move DHCP server from DC01 to a freshly promoted 2019 DC
3) Demote DC01 and shut it down
4) Change IP on the new 2019 DC to be the same as DC01 had
5) Promote secondary new 2019 DC
6) Demote DC02 and shut it down
7) Assign IP from DC02 to a new secondary 2019 DC
Does this sound correct? I am wondering if this is going to be transparent for the clients or not, and it should not affect our Exchange server?
Thanks
Thanks Glad to know you like it. Yes you can follow these steps
Perfect video , Thanks
You are welcome!
Nice
Thanks glad to know you like it
Great Tutorial ! 2 things .. 1. After moving dc to new one anything happens in client current login profile ? 2. Can I do this procedure in my running environment ?any impact for the connected clients ??
Yes you can!, No issue on client end if you follow all steps correct and no error.
Thanks Vikas, just two questions: 1. So we have to put the old server's IP for DNS server of new one then change it to itself after joining the domain? 2.Some say to enable SMB 1 in new server first, do we need to do that?
Thank you so much for this How To.
Thanks glad to know you like it
Thanks for the video sir, could you also please explain what is the difference between Inplace and siste by site migration.
Hi, Thanks for sharing. Just want to know why you don't use the adprep when doing these migrations? Is it necessary to use the adprep or should one just migrate without using the adprep. Thanks, regards, Rakesh
Its always recommended to to adprep.... But new Server OS can take this process automatically as well.
@@LabsHandsOn thanks for your response..
Nice video, but i have to ask why would you disable IPV6 on the new server, per Microsoft over the past recent years you should NOT disable IPV6,a and why would you use a 192.168.01 secondary DNS in the setting, which is why you got the error the 1st time trying to promote the new server. Its also a little misleading when run dcdiag and say everything passed, when clearly some have failed. I know the failed ones dont affect the promotion, but to say everything passed is i bit misleading.
Thank you, but in you missed the First step is to backup the server 2008 . Because in production is accounted as an important step. What do you suggest to do this backup?
This is awesome instructional video and thank you. If Windows 2008 r2 has DHCP service, you have instruction how-to migrate DHCP to Windows 2019 too?
Thanks glad to know you like it. You can below for DHCP Migration.
ruclips.net/video/x9cYLvn7sBs/видео.html
Thanks for this Video.
Thanks Glad to know you like it
Great video!!! Beautiful job. I need to migrate from SBS2011 to Server 2019. I don't want to migrate Exchange mailboxes in SBS2011 to 2019, just users and computers. After migration, I will instal Exchange 2019, and I will recreate mailboxes. Do you think there are some issues? Can you give some suggestions? Thank you in advance!
Thanks. great job ! it works fine in my testing environment. Does it work with DHCP and printer server roles ?
Thanks Glad to know you like it
Thank you for sharing Sir.
Thank you very much for your feedback, Glad to know you like it..
That worked great, thank you Sir!
Thanks, Glad to know you like this video.
Hi Vikas - this video is great - I have to do just this to a server later this week.
Can you tell me the best way to deal with the logon scripts? Obviosuly the mapped drives batch files will no longer work...obviously i have to copy the data to the new server, will the permissions automatically get copied accross? Do i then have to create new batch files?
Sir this is grade and details to help me migrate new AD server, just got some question hope can get your answer. if after demoted old server and i need to set new server IP to previous old server IP, will it got any problem affect?
You can change IP Address for you New AD Server, Once old server is demoted and out of network.
Not every device on our network is DHCP. So some will have static IP configurations including static DNS entries on the NIC. Is there a clean way to keep the same IP addresses of the old domain controllers for the new ones?
Drop me email on vikas.9452@gmail.com, Your question is not clear to me.
@@LabsHandsOn I'm so sorry. I have worded that very poorly. What I mean is that my domain controllers are also handling DNS. My DHCP server options specify the DCs as the DNS server addresses. So when a PC joins the network it will be assigned its IP address from the DHCP server but also it will be assigned its DNS servers from the DHCP server as well. The problem is that some PCs (and other devices on the network) are not using DHCP. They are using statically assigned IP addresses (and therefore statically assigned DNS addresses).
So this presents a problem in that if I am making new 2019 DCs with different IP addresses then this will only be okay for PCs using DHCP (because I can change the DHCP options).
I suppose I could stage the introduction of new 2019 DCs to the network. Once I have built one 2019 DC, I could shut down one of the 2008 DCs and change the IP on the 2019 DC. Is that possible?
Hello, thank you for video. Its very helpful. Can you make video about File Server Migration from 2008R2 to 2019? (I heard something about the File Server Migration Tool.)
Thank you very much for your feedback, Glad to know you like it..
Sure i will create video on that. Yes you can use File Server Migration Tool
@@LabsHandsOn Thank you Sing - as Kezer reference for the file migration is very important if you you will make a video that will be great. 2nd when I am migration from 2008 R2 Enterprise service pack 1 to Standard 2019, Installing AD+DNS on 2019, select (add a domain controller to an existing domain) it giving me an error "Verification of replica failed. The specified domain abc.local is still using FRS file replication service, to replicate the SYSVOL share FRS is deprecated. The server being promoted does not support FRS and cannot be promoted as a replica into specific domain, You must migrate the specific doain to use DFS replication using DFSRMiG command . . . ."
What command do you type? 22:32
Thank you very much for this great video
thank you
If you also had the DHCP role on the 2008r2 server and would also like that migrated to the new server, would you first migrate DHCP, or after migrating the AD/DNS roles?
Hi! Big thanks for this video! Q1: In the video you go from SBS 2008 R2 to WS Standard 2019, right? We have a Windows Server 2008 without "R2", do we need to do some preperations before we migrate? Q2: In one place in the video it asks for "DS RM password" … are you using the same credentials everywhere, i.e. Administrator and its password, or did you use Another one at that login? Q3: We have about 30 users and have bought lics for them, do we need to add them to the new server in some way before we migrate or is that done afterwards? Are they added at all or is it just a paper with licenses numbers to keep safe? Q4: On the old server we have Azure AD Connect, we will turn it off before migrating. If we install it on the new server afterwards, will it work and match the existing accounts in cloud/O365? Thanks for answers! br /Marcus
Please connect me on vikas.9452@gmail.com... for such query and help.
I have same questions. I am going to migrate Server 2008 (without R2) to Server 2019. We just haven´t got O365, so Q4 isn´t important to me. If there are answers or if I can send email to anyone, it would be really helpfull. Thank you very much. I know, there is an email address of Vikas, but I don´t want to bother him or write him without his permission. Thanks again.
Hi! Vikas, I did send you a mail, maybe it ended up in junk mail? Anyhow. I had to upgrade/prepare some things on the old server but all error messages gave good indications on what to Google for and old server is now retired! Big thanks for that. Your video was a really good help! Q2/Q3: It was the same password and I have not added any licenses to new server, I just have them on a paper. Br Marcus
Wil this work the same way for SBS2011 to WS2019? if i am right SBS2011 is pretty much WS2008 R2.
Yes you can use.
Hi, would you use the ADMT to migrate security groups and user accounts AFTER following this guide or before, or use the ADMT for the entire process?
You can do it using the video strategy or ADMT, its the same result.
Would the process be similar whether going to 2019 Essentials instead of Standard?
Yes, you can follow the same.
Hi, I have successfully migrated my Physical Windows 2008 R2 to Windows 2019 Server to a Hyper-V virtual machine. The only issue I encountered was when I was decommissioning the Physical Windows 2008 R2 DC it gave me an error "Active Directory Domain Services could not transfer remaining data in directory partition" "The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles." I have managed to resolve this issue and my Virtual Domain Controller in running smoothly and wanted to share this to people who are experiencing similar issues on how to resolve this problem.
The correct setting for the Infrastructure master FSMO role holder can be found by doing the following from the domain controller that you are trying to demote.
1. The correct setting can be found by going to start>run and typing adsiedit.msc
2. Then right click on ASDI Edit and click Connect to.
3. Select the radio button to Select a well known Naming Context. Then select the Default naming context and click OK.
4. Click on DC=YOURDOMAIN,DC=Local.
5. Find CN=Infrastructure which should be separate entry at the bottom, then double click on it.
6. Double click on the fSMORoleOwner attribute and copy the contents.
7. Click Cancel and Cancel again.
Change the incorrect setting
Again the below should be done from the domain controller that you are trying to demote.
1. Go to start>run and type adsiedit.msc
2. Then right click on ASDI Edit and click Connect to.
3. It is important that you perform the next few steps accurately or you will see the wrong setting (there is more than one Infrastructure record!). Click ‘Select or type a Distinguished Name or Naming Context’.
4. In the box type:
DC=DomainDNSZones,DC=Domain,DC=Local
where DC=Domain,DC=Local is the distinguished name for your domain. Then click OK.
5. Click on DC=YOURDOMAIN,DC=Local.
6. Find CN=Infrastructure which should be separate entry at the bottom, then double click on it.
7. Then find the attribute fSMORoleOwner and double click on it. Paste the contents from the correct entry that you just copied above.
8. Then click OK and OK again.
9. Repeat steps 1-8 but instead of connecting to DC=DomainDNSZones,DC=Domain,DC=Local connect to:
DC=ForestDNSZones,DC=Domain,DC=Local
Thanks again for a great video that you posted.
You can shutdown old server for few days once you sure everything good. You can do ad meta data clean up and you good then
@@LabsHandsOn thanks hey... i will do that
What software do you use to make the presentation on the video?
I use Auto Screen recorder.
Hi Vikas, thanks for the video. I have done the migration, but having issue on new DC server 2019, where the network shows private network instead domain.local Can you please suggest how to fix it or why its happening?
Sir grade job. traying to upload azure new series vedio.
Thank you very much for your feedback, Glad to know you like it..
Thank you very much for the video. Can I keep the old server as a secondary domain controller?
yes you can just transfer FSMO roles to new server
Hello Vikas, I have as VM Windows server 2008 R2 as DC runing on host over ESxi software. I would like to migrate this VM to physical server with Windows Server 2019 standard. Is there any difference in procedure from you're video? Thanks
Are you using the notes (in youtube) as tags? why not use the notes for the commands you used?
Thanks for suggestion... I will follow you.
What is the purpose of putting in your router as a DNS server address? I was always told this was a bad practice.
wether don't need to set the adprep in the first settings for all migrating DC? i try on lab and see you video migrating form 2008 to 2016. but im 2008 to 2012. but failed. error demoted and etc. i dnt know why
hello vikas - thanks for the awesome tutorial - i've successfully upgraded my domain from on-prem to vms sitting on azure, - what is the best next step to migrate on-prem exchange to 0365? - also is it good idea to have 2nd dc and 2nd dns on prem? - my current domain have 500 users and mailboxes - thanks
Thanks.. Glad to know you like it.
for On-Prem to O365.. Raise case with O365 support team... They will check your infra and give you plan for migration as well.
Hi , thks for the video. I wanted to know what password you enter @14:26
the same password for the old server or you creating a new one?
You can set new password new issue
@@LabsHandsOn hi I really need your help.
I want to transfer a 2008 server to another new 2019 . The person that did it before idk what he did .none of the pcs in the office belongs to a domain.
When I try adprep / forest don't work.
Is there any way to clone it to the new server?
Hi ! Thank you for your work really helpful !! Is it possible to migrate dfs services ?
Yes you can!
After that all activity can I use old IP Address for new domain server
i have sql server 2000 on windows server 2008..its can possible to run with old databse to new server new windows 2019-sql server 2012 ?
Can you give the specifications of the physical host or is this in the cloud?
Can you please do a video on how to migrate a Windows 2008 R2 Server Core with AD, DNS, CA to Windows 2019 Server Core?
Thanks for your suggestion... I will try to create soon on this topics.
It is the same procedure except that you have to run the GUI tools on a client machine.
@@chrisbarber7291 I would still prefer to follow a video since I have never done it before.
I have a doubt here before migration we need to prepare the 2008 AD for 2019 AD migration right?
I mean schema version upgrade from 47 to 88, forest prep, domain prep and gpprep.
Please anyone clarify here
Yes.. He did not confirm if Forest and Domain prep versions by raising Forest and Domain levels. I feel like he missed those steps.
does this migration work from windows sbs server 2011 standard to windows server 2019 essential?
Yes
I migrated from 2008R2 to 2019
Thanks, Glad to know you like this video.
What is the cmd for health check
Dear sir Is it possible upgrading server 2008 standard r2 to server 2012 r2 ?
Yes, you can find video for same on my channel
why you don't use adprep ?
work that for windows server2008 r2 foundation to 2019 Standard? tx
Should work
Will this work for 2008 to 2022?
How to migrate server without changing host name and IP address
You can change ip and hostname after complete migration.
If I am not wrong may be ip address and host gave some problems in infra
Sorry but you talk to much and no dircet step to follow!!