FYI, I have just installed Windows Server 2019 Standard (Desktop Experience) using the latest (WS2016) HP AMD chipset & VGA driver. Everything is recognised in Device Manager and stable.
Well, I finally did it and got a 4K monitor and have attached it to my MicroServer.
Here is my list of devices that I worked with:
4K LG Monitor
· LG32UD59-B 32” 4K UHD LED Monitor, 3840x2160, HDCP 2.2, HDMI, DisplayPort, AMD FreeSync, On-Screen Control
HPE ProLiant MicroServer Gen10 X3421
· 8GB RAM - Stock
· Windows 10 Pro x64
· OS Drive: SATA Port 1 – Samsung 840 Pro 256GB loaded in Icy Dock’s EZConvert in Drive Bay 1
· 4K LG Monitor attached with DP cable – NOTE: 4K LG Monitor was also attached with HDMI cable via: “Active DisplayPort to HDMI 4K Adapter, Benfei DP to HDMI Ultra HD Converter” -- both attachments seemed to work well.
· SYBA SD-CM-UAUD USB 2.0 External Stereo Audio Adapter
· External speakers with subwoofer
· Logitech K120 Keyboard with mouse
· Pioneer slim external USB 3.0 Blu-Ray BDR-XD05S
· CyberLink PowerDVD 18 Ultra
The monitor seems to work well in 4K mode with both the DP cable connected directly to the MS as well as the HDMI cable using a DP to HDMI converter that I used last year when working on the Beta unit. So far so good.
Here's a video of my experience
I also posted this on the HPE forums.
Just bought my first HP Microserver and got a decent deal on a Gen10 x3421. I am using a USB key to try and install either CentOS or RHEL 7 on it and neither install sees any of the disks in the front slots. I am using 1TB WD Caviar Green drives. I have also tried a Seagate drive but nothing seems to work.
I have gone back and forth between EUFI and Legacy hoping that would help. Nothing.
I am currently installing on a 500B USB drive and hope to see if the drives are visible when I fully boot.
I also looked through the drivers and firmware and did not see anything directly related to my problem. I was going to download the SPP but couldn't igure out how to register my system manually to allow me to download the SPP.
Am I missing anything obvious or does the system not yet support RHEL 7 or CentOS 7?
Thanks for any information.
I am hoping that you can help with an issue I am having with my new HP Microserver Gen 10. Apologies if I am posting in the wrong place.
The microserver CPU is constantly running at 100%. It occasionally dips but normally is maxed out. I have build the server from new using Samsung SSD drives in a Raid 1 configuration initially. I have also tried the following.
1. Single SSD with windows 10 Pro
2. Single SDD with Server 2016
3. Raid 1 with Server 2016.
4. Single SATA with Windows 10 pro.
I have updated the firmware. I have downloaded all the latest drivers from HP's portal.
I have tried to get support from HP but they are providing one excuse after another to explain why they cant support the server. Currently the server is about a month or so old.
HP Support responses..
1. Windows 10 isn't supported.. ( Despite having windows 10 drivers for this server on their portal)
2. SSD drives are not supported
3. SATA drives are not supported unless they have HP branding. ( The Gen 10 is being sold on Amazon with Western Digital drives included)
We have tried killing of several services in Windows 10 as per articles that we have found online. We have set the Virtual Memory to refresh on reboot.
None of the above have achieved anything.
As a result of the CPU running constantly at 100% the system is unbearably slow and cant be used to run even the most basic of tasks.
It looks like we have been left holding an expensive tin box.
I have attached a screen dump showing the CPU utilization.
Any help or advice at this point would be greatly appreciated.
As in screenshot the Network cards of the Gen10 are shown in the removable list... As you can see I have the latest drivers and firmware for the two cards. This is a very annoying issue since you can accidentally lose network connectivity while ejecting an external USB device.
FYI the four disks installed at the front bays (Marvell controller) had the same issue but I fixed it by following MS's article: