HP ILO - DL160 G6 - Missing Hardware Inventory & Monitoring Sensors

 

Intro:

Missing Hardware Inventory & Monitoring Sensors on the ILO page after an ILO firmware update? If you just upgraded the BMC ILO firmware and didn't boot the machine then the Hardware Inventory & Monitoring Sensors page will be blank.

• You'll also notice that under the ILO Summary page, the description will read as:

Description:

Proliant generic G6

instead of:

Description:

DL160 G6

Fix:

• To get this back simply boot the system.

• Look for the line..."New Generic BMC Detected, Pre-Install a BMC SDRR/CFG". It will automatically update the BMC and the description on the summary page will change and the Monitoring Sensors page will come back.

Monitoring Sensor Data

👽

HP ILO - com.serverengines.rdr.EndOfStream: EndOfStream

 

Intro:

Every so often this bug will arise when trying to connect to the KVM implementation on HP ILO servers. However as of 2017, all major modern browsers have dropped support for Java applets, which relied on the Java NPAPI (Netscape Plugin Application Programming Interface) plugin. Chrome dropped it in 2015 and FireFox in 2017.

*As long as 32-bit Java is installed you can run the standalone applet under Windows 10/11.

Fix:

    1. Point your browser to http://<IP_ADDRESS>/M2.JAR

• Make sure m2.jar is capitalized or it won't download the file.

    2. Run the M2.JAR file and input your IP, username, and password.

• As long as you have a 32-bit Java SE Runtime Environment that's either v202 or below, this will work.

👽

Windows 10/11 - Select the Target Feature Update Version

Intro:

In Windows 10 and Windows 11, you can select a Target Feature Update Version to control which specific version of the operating system your device installs. This is especially useful in enterprise environments or for individual users who want to delay upgrading to a newer version for stability, compatibility, or testing purposes.

How to Select the Target Feature Update Version:

Using Group Policy:

1. Open the Group Policy Editor:

   • Press Win + R, type gpedit.msc, and press Enter.

2. Navigate to:

   • Computer Configuration > Administrative Templates > Windows Components > Windows Update > Manage updates offered from Windows Updates.

3. Locate and configure the policy:

   • Find Select the target Feature Update version.
   • Double-click to open the policy settings.
   • Set it to Enabled.
   • Reference this link for the next bit of information: aka.ms/WindowsTargetVersioninfo
   • Enter "Windows 10" or "Windows 11" in the first box.
   • Enter the Target Version (e.g., 21H2 for Windows 10, or 22H2 for Windows 11).

4. Apply and save:

• Click OK to save the changes.

Using Registry Editor:

1. Open the Registry Editor:

   • Press Win + R, type regedit, and press Enter.

2. Navigate to:

   • HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate.

3. Create or modify the keys:

   • Right-click in the right pane and select New > DWORD (32-bit) Value.
   • Name the value: TargetReleaseVersion.
   • Set its data to 1.

4. Specify the target version:

   • Right-click again and create a new String Value.
   • Name it: TargetReleaseVersionInfo.
   • Set the data to your desired version (e.g., 21H2 or 22H2).

5. Close the editor and restart your system.

Using PowerShell:

For a more automated approach, use PowerShell to set the target version:

1. Open PowerShell as Administrator.
2. Run the following commands:

   powershell
   Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" -Name "TargetReleaseVersion" -Value 1
   Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" -Name "TargetReleaseVersionInfo" -Value "22H2"
   

Notes:

• TargetReleaseVersionInfo must match the official version names (e.g., 22H2 for the second half of 2022).
• This setting will prevent the device from installing a newer feature update than the specified version.
• Security updates and cumulative updates for the specified version will still be installed.

👽