A look at how to handle those 2012 installs we may still have. Please make sure to read the description for the chapters and key information about this video and others. ⚠ P L E A S E N O T E ⚠ 🔎 If you are looking for content on a particular topic search the channel. If I have something it will be there! 🕰 I don't discuss future content nor take requests for future content so please don't ask 😇 🤔 Due to the channel growth and number of people wanting help I no longer can answer or even read questions and they will just stay in the moderation queue never to be seen so please post questions to other sites like Reddit, Microsoft Community Hub etc. 👂 Translate the captions to your native language via the auto-translate feature in settings! ua-cam.com/video/v5b53-PgEmI/v-deo.html for a demo of using this feature. Thanks for watching! 🤙
Quick note on what about other clouds. You can still get ESU: SPLA Scenario: If you've acquired a Windows Server operating system from a SPLA partner, you can cover that OS with ESU licenses. BYOL Scenario: If you've brought your own Windows Server licenses to a cloud hosting provider via your Outsourcing policy or License Mobility, you can cover those licensed operating systems with ESU licenses. To summarize - if you are allowed to run the underlying software, you are allowed to apply the ESU.
My friend, you just saved me a ton of time. My issue with upgrading my servers are lazy devs who have no desire to reinstall and/or migrate their applications. Your explanation of how the modern in place upgrade gives me a viable option. I have been in IT for a long time and the in place upgrade was a gigantic "No No"... and often a resume generating move. Thank you so much for the info.
This was a great session - thanks! We've been upgrading our remaining 2012 R2 boxes over the last 9 months - 107 servers - some physical, most virtuals (on prem and in Azure). The majority have been in-place upgrades. Success rate has been refreshingly high - we've actually found going to 2019 rather 2016 has made the upgrade run smoother. In particular the 2016 upgrades hit you with a License 'Accept' button on first boot after the upgrade - if you're working remotely then you either need an ilo/rcb or someone on site to press Accept before you can get a remote session back up on it otherwise you're stuck. 2019 doesn't have that license blocker - so you can upgrade remotely without the need for a ilo/rcb/friendly on-premise staff member.
Great video. Thanks for sharing. There is the latest Oct patches release for W2012, without applying ESU license key still can install the patches. Is it unable to install the next month's patches if without applying the ESU license key?
A look at how to handle those 2012 installs we may still have. Please make sure to read the description for the chapters and key information about this video and others.
⚠ P L E A S E N O T E ⚠
🔎 If you are looking for content on a particular topic search the channel. If I have something it will be there!
🕰 I don't discuss future content nor take requests for future content so please don't ask 😇
🤔 Due to the channel growth and number of people wanting help I no longer can answer or even read questions and they will just stay in the moderation queue never to be seen so please post questions to other sites like Reddit, Microsoft Community Hub etc.
👂 Translate the captions to your native language via the auto-translate feature in settings! ua-cam.com/video/v5b53-PgEmI/v-deo.html for a demo of using this feature.
Thanks for watching!
🤙
Quick note on what about other clouds. You can still get ESU:
SPLA Scenario: If you've acquired a Windows Server operating system from a SPLA partner, you can cover that OS with ESU licenses.
BYOL Scenario: If you've brought your own Windows Server licenses to a cloud hosting provider via your Outsourcing policy or License Mobility, you can cover those licensed operating systems with ESU licenses.
To summarize - if you are allowed to run the underlying software, you are allowed to apply the ESU.
My friend, you just saved me a ton of time. My issue with upgrading my servers are lazy devs who have no desire to reinstall and/or migrate their applications. Your explanation of how the modern in place upgrade gives me a viable option. I have been in IT for a long time and the in place upgrade was a gigantic "No No"... and often a resume generating move. Thank you so much for the info.
Why are you holding a 'save button' at the start? :P
ROFL, OK that took me a second :-D
hahaha good one !
We managed to do an in-place upgrade on the last five 2012 R2 servers we had in Azure, thankfully everything went through smoothly!
nice!
Thanks John, your channel has heaps of invaluable contents that will take me years to learn.
I appreciate that!
Loved the crisp, concise and hugely impactful content and delivery, thank you!
Much appreciated!
Asked our MS reps today how Arc ESU activation is verified during the update process. You have answered for them! Very useful, thank you.
Glad I could save them some research :-D
This was a great session - thanks!
We've been upgrading our remaining 2012 R2 boxes over the last 9 months - 107 servers - some physical, most virtuals (on prem and in Azure).
The majority have been in-place upgrades. Success rate has been refreshingly high - we've actually found going to 2019 rather 2016 has made the upgrade run smoother.
In particular the 2016 upgrades hit you with a License 'Accept' button on first boot after the upgrade - if you're working remotely then you either need an ilo/rcb or someone on site to press Accept before you can get a remote session back up on it otherwise you're stuck.
2019 doesn't have that license blocker - so you can upgrade remotely without the need for a ilo/rcb/friendly on-premise staff member.
Wait an ilo? You're running windows server on bare metal? Why no hypervisor?
Awesome! Been waiting for this refreshing your feed!
Hope you enjoyed it!
Excellent video John! Thank you for sharing..
Very welcome
Timely and informative video. Tks John.
Very welcome
John, Thank you so much for this video, excellent explination you have saved mne hours of reading.
Glad it helped!
Great video. Thanks for sharing. There is the latest Oct patches release for W2012, without applying ESU license key still can install the patches. Is it unable to install the next month's patches if without applying the ESU license key?
November is first ESU required patch
Very informative. thank you!
Glad it was helpful!
Very good video John thanks !!
As it is easy to find the ESU yearly prices, do you know where we can find monthly ESU prices payed by Azure Arc ?
They are linked in this video description
@@NTFAQGuy my bad thanks !
No problem
Thanks John! Quick question - is licensing a VMware host possible or would it have to be Hyper V for physical core licensing?
can absolutely cover the pcores on a host or the vcores for the VMs.
Thanks for confirming dude
Are you sure that you cannot create a 48 vCore license and use it on say 6 4 vCPU VMs? Understanding that there has to be 8 cores per vm minimum.
They are actually changing the guidance to now allow this based on customer feedback but yes as you said still need 8 minimum per VM.
Can we leverage Azure ARC for SQL 2012 ESU support as well?
It’s covered in the video
Wow, free ESU if in Azure. What better way to force people into Azure.
‘encourage’
So glad we skipped Server 2016 🤢