Arthur Posted November 13, 2018 Posted November 13, 2018 It's not on VLSC just yet though. https://blogs.technet.microsoft.com/virtualization/2018/11/13/windows-server-2019-now-available Windows Server 2019 is once again generally available. You can pull the new Windows Server 2019 images—including the new ‘Windows’ base image—via: docker pull mcr.microsoft.com/windows/servercore:1809 docker pull mcr.microsoft.com/windows/nanoserver:1809 docker pull mcr.microsoft.com/windows:1809 Just like the Windows Server 2016 release, the Windows Server Core container image is the only Windows base image in our Long-Term Servicing Channel. For this image we also have an ‘ltsc2019’ tag available to use: docker pull mcr.microsoft.com/windows/servercore:ltsc2019 The Nanoserver and Windows base images continue to be Semi-Annual Channel releases only. 1
CHiLL Posted November 13, 2018 Posted November 13, 2018 Thanks for the links. We're still a Server 2012 R2 house and looking to possible migrate some non essential servers to 2019. As I'm not up to speed on the server releases as I am with the desktop releases, have Microsoft taken the same approach to servers as they have with desktops? As in CB and LTSC? Obviously servers are meant to be much more stable, so would the CB version have two releases per year? What's the closest version to 2012 R2/2016 or is that method not recommended any more?
3s-gtech Posted November 13, 2018 Posted November 13, 2018 This will be a stable and bug-free release as soon as its available again. I will be deploying it onto every live server I run as soon as possible.
computer_expert Posted November 13, 2018 Posted November 13, 2018 And the blog article has disappeared (it was there earlier!)...
Michael Posted November 13, 2018 Posted November 13, 2018 An indication on how we can make sure you have the bug free version of Server 2019?
Arthur Posted November 13, 2018 Author Posted November 13, 2018 An indication on how we can make sure you have the bug free version of Server 2019? Did you download the ISO prior to today? If so, delete it and download the new one from VLSC.
Michael Posted November 13, 2018 Posted November 13, 2018 I didn't, but it just 'bugs' me in the back of my mind.
Arthur Posted November 13, 2018 Author Posted November 13, 2018 I didn't, but it just 'bugs' me in the back of my mind. It's definitely the fixed version. www.zdnet.com/article/microsoft-re-releases-windows-server-2019 After pulling its Windows 10 October 2018 Update (also known as 1809) and Windows Server 2019/1809 feature updates at the start of October, Microsoft is re-releasing them to mainstream users starting today, 13 November. The updated versions include fixes for data-loss problems and other issues discovered after Microsoft initially began rolling them out on 2 October. Starting today, customers can download the Windows Server 1809 and Windows Server 2019 media from the Volume Licensing Service Center (VLSC). Azure customers will see the Windows Server 2019 image available in the Azure Marketplace over the coming week, officials said. And Microsoft is working to make the Windows Server 2019 evaluation release available on the Microsoft Eval Center. (My ZDNet colleague Ed Bott has the details on the re-release of the client version, now build 17763.107. Microsoft also is re-releasing the October Update version of Windows 10 IoT today, as well).
Arthur Posted November 14, 2018 Author Posted November 14, 2018 ISO checksums. [b]SW_DVD9_Win_Server_STD_CORE_2019_64Bit_English_DC_STD_MLF_X21-96581.iso[/b] SHA-1: e1da51796746668fb36864a7c3c6460d01f7d0aa SHA-256: 61a391f0dc98e703da674df3c984ac2eb432ff757f949385360e68476c920478 SHA-512: 6eaf8b8e55b5ece6ea5ab6cd99e625de665e683c72f91405efd5c84b4167020251dacb0a7485682979241370cd24ab7ce3b3ed7b8d724ed5a41ec51e0ff0bb92
DJ-1701 Posted November 14, 2018 Posted November 14, 2018 Hope it's bug free! Yes, I am quite sure all the bugs are free. 4
Tefters Posted November 14, 2018 Posted November 14, 2018 #Sigh... KMS codes missing... Time to phone...
DJ-1701 Posted November 14, 2018 Posted November 14, 2018 #Sigh... KMS codes missing... Time to phone... Unfortunately you are always going to have to call for KMS keys. They have stopped giving them out automatically and you have to contact per product.
Tefters Posted November 14, 2018 Posted November 14, 2018 Unfortunately you are always going to have to call for KMS keys. They have stopped giving them out automatically and you have to contact per product. What was their retarded reasoning for this considering KMS is the preferred activation method in any serious enterprise?
DJ-1701 Posted November 14, 2018 Posted November 14, 2018 What was their reasoning for this considering KMS is the preferred activation method in any serious enterprise? I believe it was 'herb-a-derb'. Come on, this is Microsoft, they don't give any reasoning, just tell you you have to call up or e-mail them. It was hidden away on the VLSC site at some point in the FAQs.
Tefters Posted November 14, 2018 Posted November 14, 2018 I believe it was 'herb-a-derb'. Come on, this is Microsoft, they don't give any reasoning, just tell you you have to call up or e-mail them. It was hidden away on the VLSC site at some point in the FAQs. Its like 2 steps forward, 1 step back... I do love the Server 2019 description - Windows Server is the operating system that bridges on-premises environments with Azure services enabling hybrid scenarios and maximizing existing investments. Click here to learn more. They are hell bent on pushing Azure aren't they even though the cost still isn't friendly for education.
Arthur Posted November 14, 2018 Author Posted November 14, 2018 What was their retarded reasoning for this considering KMS is the preferred activation method in any serious enterprise? Is it to ensure Microsoft only gives out keys to customers with valid licenses/volume licensing agreements with software assurance? Every single time I contact Microsoft for a new KMS host key for Windows Server, they say they are unable to generate it because they can't find the license. I then have to explain to them that it's included in the Core Infrastructure Suite.
Tefters Posted November 14, 2018 Posted November 14, 2018 Is it to ensure Microsoft only gives out keys to customers with valid licenses/volume licensing agreements with software assurance? Every single time I contact Microsoft for a new KMS host key for Windows Server, they say they are unable to generate it because they can't find the license. I then have to explain to them that it's included in the Core Infrastructure Suite. I asked for 2019 keys and the lady on the phone gave me a Standard 2019 MAK key. I then asked for a KMS key and was questioned about it, anyways got the KMS key finally as well and then I questioned her as to Datacenter MAK key to which she further tried to argue that I didn't need it as I had the standard and KMS. Eventually I got that as well... Why they can't just give us all 3 sets of keys from a simple license check... Is it that hard to understand, KMS for enterprise domain licensing, MAK for offline servers.
supportman Posted November 14, 2018 Posted November 14, 2018 Tried with my MAK key but its not recognised, even tried with: Dism /online /Set-Edition: ServerDatacenter /AcceptEula /ProductKey: No luck, but I guess maybe I am trying to soon.
CHiLL Posted November 28, 2018 Posted November 28, 2018 Did anyone find a sucessful resolution to this? I've tried entering my KMS key from VLSC into Volume Activation Tools on my Server 2012 R2 server that also has VAMT 3.1 and RSAT 1809 installed. When I go through the wizard I get the to 'Activate online' section and then receive an 'Access Denied' message when attempting to activate it.
supportman Posted November 28, 2018 Posted November 28, 2018 Gave up in the end myself, might try another install at some point. Just kept getting activation errors immediately.
Tefters Posted November 28, 2018 Posted November 28, 2018 Mine works fine... Entered KMS key, gave it a name and saved. Servers been registering fine under AD activation.
CHiLL Posted November 29, 2018 Posted November 29, 2018 (edited) So I have fixed my issue. Turns out the KMS key on our relationship summary page is incorrect and doesn't match the KMS key that is listed when I look in Downloads and Keys. As soon as I activated that key from the Downloads and Keys page, my 2019 servers were able to activate sucessfully. So: 1) Have a Server 2019 machine or client machine with RSAT 1809 Volume Licensing Tools installed as a role. 2) Use Volume Activation Tools on Server 2019 / machine with RSAT and specify AD activation 3) Activate the key 4) Run the activation process on your servers Such a bizare issue. Edited November 29, 2018 by CHiLL
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now