Обновление сервера 2012 r2 до windows server 2019

• Remove From My Forums

All replies

• The simplest / safest thing to do is stand up the new Server 2019 on new host, patch it fully, add Hyper-V role and either export / import VMs or live migrate them. If you’re also upgrading VMs then I’d stand up new ones, join existing domain and migrate
  roles and applications over to new host.

  If using same host hardware then export them, do the rebuild with Server 2019, patch fully, add Hyper-V role and import.

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

• Hi and thanks. To me the easiest way to upgrade is run setup from ISO and upgrade as with other windows OSs (in place upgrade). Is there anything wrong with it?

•  Is there anything wrong with it?

  Very risky and existing corruption carry-forward. In-place upgrades are not recommeded.

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

• I can’t setup another physical host because it’s costly. It has only hyper v role installed. But I do take weekly full system backups including Hyper V stored on a separate HDD. What would you suggest?

• The second option. If using same host hardware then export VMs, do the rebuild with Server 2019, patch fully, add Hyper-V role and import VMs.

  I’d also check here and with server manufacturer about support for Server 2019

  https://www.windowsservercatalog.com/

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

  • Edited by
    Dave PatrickMVP
    Sunday, May 19, 2019 3:31 AM

• Rebuild meaning run setup from ISO and perform clean install? Another question about upgrading the whole environment, where to start the upgrade? Is it okay to upgrade another role without upgrading Active directory and domain controller?

• I’d do the host, import VMs, then for domain controller upgrade (assuming server 2019)

  Migrating sysvol replication from older FRS technology to DFSR is required. 
  https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405

  Also check the domain functional level is 2008 R2 or higher, then
  use dcdiag / repadmin tools to verify health
  correcting all errors found before starting. Then stand up the new 2019 guest, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional),
  transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one, and move one to next one.
  

  I’d ask experts here about upgrading an RDS deployment.

  https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverTS

  (please don’t forget to mark helpfu replies as answer)

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

• hi,
  there are some documents for your reference about upgrading your remote desktop services deployments to windows 2019.
  before we do in-place upgrade ,we need to backup and export vhdx files of all vms to external disk in order to restore them when in place upgrade fail.
  Upgrading your Remote Desktop Services deployments to Windows Server 2016
  https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/upgrade-to-rds

  Upgrading your Remote Desktop Session Host to Windows Server 2016
  https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/upgrade-to-rdsh

  Upgrade Windows Server 2012 R2 to Windows Server 2019
  https://www.microsoft.com/upgradecenter/scenario/WS2012R2-on-prem-to-WS2019

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

  • Edited by
    Andy YOUMicrosoft contingent staff
    Tuesday, May 21, 2019 3:59 PM

• Thank you so much for the prompt advice. I have the following VMs: 1-AD DC/ DHCP 2-subordinate enterprise CA 3-RD connection broker/RD Licence Manager 4-RD web access/RD Gateway 5-RD Session Host 6-CA (offline) All running windows server 2012 r2. I’m trying
  to figure out where to start. I’ve already setup a new VM with Server 2019 installed. I’ll be promoting this as DC to replace current DC. I need to know after doing this, will this affect all other servers for as long they still run 2012 r2 until upgraded?
  If I decide some roles to remain on 2012 r2, would I be able to raise domain and forest functional level to 2016? I’m planning to setup new VMs to replace 3,4 & 5; basically deploying a fresh RDS. I’m not sure whether to do an in-place upgrade or migrate roles
  to new VMs for 2&6 or don’t upgrade them at all. Regards .

• I’ll be promoting this as DC to replace current DC. I need to know after doing this, will this affect all other servers for as long they still run 2012 r2 until upgraded?

  The 2012 R2 DCs will be fine. I’d check that domain functional level is at least 2008 R2, also migrating sysvol replication from older FRS technology to DFSR is a prerequisite to adding a 2019 domain controller. I’d recommend use dcdiag / repadmin tools
  to verify health correcting all errors found before starting.

  https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405

  once done then use dcdiag / repadmin tools to verify health again, then stand up the new 2019, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over
  (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to verify health, when all is good you can decommission / demote old one (optional).

  If I decide some roles to remain on 2012 r2, would I be able to raise domain and forest functional level to 2016?

  You can raise level to the lowest existing domain controller OS. There is no new functional levels for 2019 (still 2016 is highest)

  I’m planning to setup new VMs to replace 3,4 & 5; basically deploying a fresh RDS. I’m not sure whether to do an in-place upgrade or migrate roles to new VMs for 2&6 or don’t upgrade them at all. Regards .

  I would not in-place upgrade any of them. 

  (please don’t forget to mark helpful replies as answer)

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

  • Edited by
    Dave PatrickMVP
    Tuesday, May 21, 2019 10:09 PM

• Remove From My Forums

All replies

• The simplest / safest thing to do is stand up the new Server 2019 on new host, patch it fully, add Hyper-V role and either export / import VMs or live migrate them. If you’re also upgrading VMs then I’d stand up new ones, join existing domain and migrate
  roles and applications over to new host.

  If using same host hardware then export them, do the rebuild with Server 2019, patch fully, add Hyper-V role and import.

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

• Hi and thanks. To me the easiest way to upgrade is run setup from ISO and upgrade as with other windows OSs (in place upgrade). Is there anything wrong with it?

•  Is there anything wrong with it?

  Very risky and existing corruption carry-forward. In-place upgrades are not recommeded.

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

• I can’t setup another physical host because it’s costly. It has only hyper v role installed. But I do take weekly full system backups including Hyper V stored on a separate HDD. What would you suggest?

• The second option. If using same host hardware then export VMs, do the rebuild with Server 2019, patch fully, add Hyper-V role and import VMs.

  I’d also check here and with server manufacturer about support for Server 2019

  https://www.windowsservercatalog.com/

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

  • Edited by
    Dave PatrickMVP
    Sunday, May 19, 2019 3:31 AM

• Rebuild meaning run setup from ISO and perform clean install? Another question about upgrading the whole environment, where to start the upgrade? Is it okay to upgrade another role without upgrading Active directory and domain controller?

• I’d do the host, import VMs, then for domain controller upgrade (assuming server 2019)

  Migrating sysvol replication from older FRS technology to DFSR is required. 
  https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405

  Also check the domain functional level is 2008 R2 or higher, then
  use dcdiag / repadmin tools to verify health
  correcting all errors found before starting. Then stand up the new 2019 guest, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional),
  transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one, and move one to next one.
  

  I’d ask experts here about upgrading an RDS deployment.

  https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverTS

  (please don’t forget to mark helpfu replies as answer)

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

• hi,
  there are some documents for your reference about upgrading your remote desktop services deployments to windows 2019.
  before we do in-place upgrade ,we need to backup and export vhdx files of all vms to external disk in order to restore them when in place upgrade fail.
  Upgrading your Remote Desktop Services deployments to Windows Server 2016
  https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/upgrade-to-rds

  Upgrading your Remote Desktop Session Host to Windows Server 2016
  https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/upgrade-to-rdsh

  Upgrade Windows Server 2012 R2 to Windows Server 2019
  https://www.microsoft.com/upgradecenter/scenario/WS2012R2-on-prem-to-WS2019

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

  • Edited by
    Andy YOUMicrosoft contingent staff
    Tuesday, May 21, 2019 3:59 PM

• Thank you so much for the prompt advice. I have the following VMs: 1-AD DC/ DHCP 2-subordinate enterprise CA 3-RD connection broker/RD Licence Manager 4-RD web access/RD Gateway 5-RD Session Host 6-CA (offline) All running windows server 2012 r2. I’m trying
  to figure out where to start. I’ve already setup a new VM with Server 2019 installed. I’ll be promoting this as DC to replace current DC. I need to know after doing this, will this affect all other servers for as long they still run 2012 r2 until upgraded?
  If I decide some roles to remain on 2012 r2, would I be able to raise domain and forest functional level to 2016? I’m planning to setup new VMs to replace 3,4 & 5; basically deploying a fresh RDS. I’m not sure whether to do an in-place upgrade or migrate roles
  to new VMs for 2&6 or don’t upgrade them at all. Regards .

• I’ll be promoting this as DC to replace current DC. I need to know after doing this, will this affect all other servers for as long they still run 2012 r2 until upgraded?

  The 2012 R2 DCs will be fine. I’d check that domain functional level is at least 2008 R2, also migrating sysvol replication from older FRS technology to DFSR is a prerequisite to adding a 2019 domain controller. I’d recommend use dcdiag / repadmin tools
  to verify health correcting all errors found before starting.

  https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405

  once done then use dcdiag / repadmin tools to verify health again, then stand up the new 2019, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over
  (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to verify health, when all is good you can decommission / demote old one (optional).

  If I decide some roles to remain on 2012 r2, would I be able to raise domain and forest functional level to 2016?

  You can raise level to the lowest existing domain controller OS. There is no new functional levels for 2019 (still 2016 is highest)

  I’m planning to setup new VMs to replace 3,4 & 5; basically deploying a fresh RDS. I’m not sure whether to do an in-place upgrade or migrate roles to new VMs for 2&6 or don’t upgrade them at all. Regards .

  I would not in-place upgrade any of them. 

  (please don’t forget to mark helpful replies as answer)

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

  • Edited by
    Dave PatrickMVP
    Tuesday, May 21, 2019 10:09 PM

Answers

• Более подробно объясню данный кейс:

  В филиале банка уже имеется следующие лицензии: 

  • • Microsoft Windows Server 2012 Datacenter
    • Microsoft Exchange Server Standard 2013
    • Microsoft Lync Server 2013

  А также телефоны HP 4110 IP Phone и HP 4120 IP Phone которые подключены к Lync. К этой инфраструктуре нужно докупить новые оборудования и новые телефоны, при том сохряняя функционала старого Lync.

  Необходимо также: обновить Windows Server 2012 Datacenter и Exchange Server Standard 2013, Lync Server 2013 до последних версий.

  Возможно ли обновить докупив только Software Assurance? Какие есть варианты в целом?

  Конечно же SA нельзя «докупить» когда вам потребуется обновиться. SA должно быть активным с момента покупки ПО
   (кажется требуется покупка SA в течении месяца после покупки ПО) по меньшей мере до момента выхода ПО на которое вы собрались обновляться. Это форма подписки и она требует оплаты от и до…

  Таким образом если SA не была куплена много лет назад когда вы первоначально закупили ПО или же не была активной (то есть оплачивалась) на октябрь 2018 года (когда вышел Server 2019), то обновиться используя SA вы не сможете.

  В этом случае как я уже написал есть только один вариант — покупка ПО за полную стоимость. Я бы сказал что при это надо менять и оборудование, срок службы серверов и ПК типично составляет 3-5 лет. Это так же позволит избежать «обновления»
  серверных ОС которое типично не рекомендуется. Вместо этого новые сервера и ПО подключаются в существующий домен и заменяют их. Это так же значительно безопаснее в плане утраты данных и позволит избежать простоя.

  Еще один момент: Lync (с 2015 года — Skype for Business) является наследственным продуктом и заменяется Microsoft Teams.

  ---

  This posting is provided «AS IS» with no warranties, and confers no rights.

  • Marked as answer by

    Wednesday, February 10, 2021 9:40 AM

jrp78

5 found this helpful
thumb_up
thumb_down