Windows Server 2019 Datacenter 1809 End Of Life

2 views
Skip to first unread message
Message has been deleted

Leana Eckes

unread,
Jul 8, 2024, 2:53:45 AM7/8/24
to cattaraport

Windows Server 2019 is the twelfth version of the Windows Server operating system by Microsoft, as part of the Windows NT family of operating systems. It is the second version of the server operating system based on the Windows 10 platform, after Windows Server 2016. It was announced on March 20, 2018 for the first Windows Insider preview release, and was released internationally on October 2, 2018, the same release date of Windows 10 version 1809. It was succeeded by Windows Server 2022 on August 18, 2021.[4]

windows server 2019 datacenter 1809 end of life


Descargar archivo https://tinurli.com/2yP0DP



Windows Server 2019 was announced on March 20, 2018, and the first Windows Insider preview version was released on the same day.[5] It was released for general availability on October 2 of the same year.[1]

On October 6, 2018, distribution of Windows 10 version 1809 (build 17763[6]) was paused while Microsoft investigated an issue with user data being deleted during an in-place upgrade.[7] It affected systems where a user profile folder (e.g. Documents, Music or Pictures) had been moved to another location, but data was left in the original location.[8] As Windows Server 2019 is based on the Windows version 1809 codebase, it too was removed from distribution at the time,[9] but was re-released on November 13, 2018.[10] The software product life cycle for Server 2019 was reset in accordance with the new release date.[9]

Microsoft Edge did not support Server 2019 at release. Microsoft considers Internet Explorer 11 a "compatibility layer," not a browser. Edge added support in January 2020, but Server 2019 does not install it by default. Microsoft encourages server and enterprise users to install Edge.[18]

I'm trying to install Windows Server 2019 (1809) Datacenter on a brand new server, but when it reboots after going through the IP settings it shows a gray bar in the bottom saying "Loading files . . ." (like when starting a windows installation) and then it just hangs at "Hewlett Packard Enterprise" logo.

Windows is an ISO stored on a USB key formatted with exFAT. I can select it fine doing the IP setup. Then i can see it copying data in the "job viewer" and finally it says that it needs to reboot to continue the installation. And this is where it then gets stuck at the HP logo.

After 2 days trying to configure 2 new G10 servers, and having run into the SAME GD problem on every HP G9 or G10 I've deployed, I have actually bothered to login and post a message that no one will read or do anything about. YOUR "INTELLIGENT PROVISION" TOOL IS BROKEN. HAS BEEN FOR AT LEAST THE LAST TWO YEARS, WHY DON'T YOU FIX IT?!?!? I started recommending HP DL servers to my clients in 2007, primarily because of ILO, but also reliability. At this point, it takes so much farting around with your idiotic provisioning tool that NEVER works, that I'm just going to look for another solution. In 2018 and 2019, at LEAST I could work around your broken tool by using the Quick Start or whatever your generic "Hey I'll take a wild stab at what you want to do and you can fix it later" option is called. Now, even THAT doesn't work. This time around, I have a couple of 32 core Epyc processors. Fail. Read. Oh, disable the IOMUU bios option, great, get a little further, OK, here comes the windows screen. Awwwwwww, can't proceed I don't know how to find my own hard drive controller even though I'm an intelligent provisioner. One of my drive bays is bad, can't get any of my drives to recognize as Geeeeeen-yooooo-ine HP (like THAT means something). Had to move all of my drives down to another bay because I couldn't stand the sight of one drive out of 8 sitting in a different bay and virtually stabbing me in the eyeballs. I CANNOT BELIEVE YOU HAEVN'T FIXED THIS IN THE 18 MONTHS SINCE I LAST INSTALLED ONE OF YOUR SERVERS. You guys are pulling out of Sillycon Valley and heading for Texas? Advice, don't sell any servers locally, those guys are armed. Well, I'm behind an additional day and after Indiana Jones-like exploration and attempting every option you have in that faulty, garbage provision utility, I'm now down to EDITING MY ISO! WooHoo! I LOOOOOOOVE editing ISOs to manually insert drivers, its so fun and 5-8GB files are just so easy and fast to manipulate. Do me a favor, walk to the other side of campus, find the team that works on your "Intelligent" provisioning tool and start smacking each member of the team repeatedly until the swear to do ther f'ing job. Use heavy objects if necessary. Tell them an end-user told you to. I am so beyond po'd right now I'm of half a mind to box these things up and just return them. Oh yeah AND the power supply that shipped with the server is throwing a 224 error, yes, I reseated it and swapped it with another unit, I suspect that bay is bad as well. Nice quality control. I think instead of Austin, maybe Shenzen would be a more appropriate location for you to move to. I would guess that whatever company is building your servers for you would probably do a better job of QC. Instead of forcing all of us jerks dumb enough to cling to the Proliant reputation to comb through forums and "customer advisories" FIX YOUR SOFTWARE. Stop putting it back on us, we don't like it.

d3342ee215
Reply all
Reply to author
Forward
0 new messages