Implementing Microsoft Windows Server 2012 Essentials on HP ProLiant servers
Integration note

RAM per processor (socket)*


Minimum: 2 GB

Maximum: 64 GB

Recommended: 18 GB

There’s no way Essentials needs 18 gigs of ram. That’s way way way too much for this box.


Known issues and workarounds

This section outlines a few potential issues that you may encounter with the Windows Server 2012 Essentials OS and ProLiant servers. We are actively working to resolve all the issues. We will update this paper as additional information becomes available.




Table 5 lists known issues with ProLiant servers and Windows Server 2012 Essentials.



After installing Windows Server 2012 Essentials, the Device Manager displays a yellow bang for a PS/2 keyboard or PS/2 mouse.





After installing the OS, a yellow bang displays in Device Manager for the PS/2 keyboard or a PS/2 mouse.






Install the “Headless Server Registry Update for Windows” component from the Windows Server 2012 Service Pack for ProLiant.



You cannot change the Windows Server 2012 Essentials screen resolution





After the installation of Windows Server 2012, you will not be able to change the screen resolution.






We are working with Microsoft to resolve this issue. To work around this issue, you can set the screen resolution by completing the following steps:



Access the Advanced setting in the Display Control Panel.



List All Modes in the Adapter tab.



Uncheck the Hide modes that this monitor cannot display checkbox in the Monitor tab.

You should now be able to change the resolution.



After installing Windows Server 2012 Essentials, the Event Viewer displays errors in the Windows Event Log showing that the license activation failed after providing the Product Key





After installing Windows Server 2012, the Event Viewer displays the following errors in the Windows Event Log:


The System information displays a message “Boot-start or system start drivers fail to load.”


Application information displays a message “License Activation Failed.”

This issue occurs because the services start in an order that differs from what the OS expects.






For details about this issue, see the Microsoft Support Blogs at



Event ID 46 occurs upon restarting the server





The default dump file is the pagefile. This issue may occur if the computer boots without a configured dump file. For example, after installing Windows Server 2012, the very first boot results in this issue because the pagefile has not been set up yet.






To avoid this error, configure the paging file.



You can ignore this event if it occurs after the OS installation or if you do not want to set up the dump file. For details on this issue, see the Microsoft Knowledge Base at


One Response to HP docs on Windows 2012 Server Essentials

  1. Joe_Miner says:

    Thanks for the posting!