Windows Server 2016 – HP iLO PowerShell and more…

November 9, 2018

image

image

HPE Integrated Lights-Out (iLO),

HPE Onboard Administrator (OA) for HPE BladeSystem Enclosures and

System BIOS of HPE ProLiant servers, this set of PowerShell utilities

image

We will only use iLO at this moment, because this is the most valuable.

It is a proprietary embedded server management technology of HP.

iLO makes it possible to perform activities on an server from a remote location. Even if the server OS is not responding.

1. Download the PowerShell Module

See here at the moment we are at version 2.1

image

2. Load the PS Module

Check the version

ClS

import-module "C:\Program Files (x86)\Hewlett Packard Enterprise\PowerShell\Modules\HPEiLOCmdlets\HPEiLOCmdlets.psd1"

Get-Module -ListAvailable "HPEiLO*"


image

List the Cmdlets

Get-Command -Module "HPEiLOCmdlets"

image

Update the PS Module if needed

Update-HPEiLOModuleVersion

Search for iLO servers in your network using a range or subnet

$IPRange = Read-host " Enter the IP Range of HPOA ( 10.0.0.1-25) "

Find-HPEiLO $IPRange

image

Now you are ready to run some cmdlets.

Let’s check the power of the server:

Get-HPEiLOServerPower -Connection $connection

image

Let’s check the Temperature Sensors

$Ret = Get-HPEiLOTemperature -Connection $connection

$Ret.Temperature | Out-GridView

image

3. iLO commandline Tools

The HP management utillity called hponcfg.exe is installed here.

image

iLO config Export Example :

Command :

clip_image002

hponcfg.exe /w c:\Temp\iloconfig.txt

image

You can use the is config file to make changes to your iLO configuration, like resetting your Password etc.

hponcfg /f your_script_name.txt

Enjoy !

Advertisements

Windows Server 2016 – Volsnap Error Event ID 27 & Event ID 153

November 7, 2018

Accidently I noticed some Disk Warnings Event ID 153. Together with a VSS error Volsnap Event ID 27.

All at the time we had scheduled a backup to run.

image

The message was :

The shadow copies of volume \\?\Volume{xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} were aborted during detection because a critical control file could not be opened.

SOLUTION :

First recommendation is to resize the VSS Storage Area.

Or even put the settings to No Limit

image

For more info see here : http://hyper-v-backup.backupchain.com/how-to-fix-volsnap-error-a-critical-control-file-could-not-be-opened/

At the link you can also download a small Free Utility called VSSDiag.

image

This can help you debug further issues.

PS : This is also linked to Event ID 3, see here for more info

 

 

Enjoy !


Windows Server 2016 – Application Errors after a P2V conversion Event ID 1000 Error

October 30, 2018

After converting a Physical server to a VM, I got a lot of Application Errors 1000.

Looking at the details it was relating to, amongst others, HP related drivers and software

Example : This error shows it is trying to reach a Tape device which is not present in a VM…

image

SOLUTION :

First uninstall all hardware drivers that are not needed in the new VM.

1. Open CMD with admin privileges and run this command

set devmgr_show_nonpresent_devices=1

2. Next run this command

devmgmt.msc

And go to VIEW, select SHOW HIDDEN DEVICES

image


3. Make backup of your VM

Before going to next step MAKE SURE you have a good backup of the current SYSTEM STATE

4. Expanded list

Look at all the GREYED out devices and UNINSTALL these Software and Drives

image

5. Uninstall COM Objects

From the Event Viewer Error I could see we where dealing with a COM related DLL

Use WBEMTest.exe to investigate if the COM Object is still in use.

image

In my case I was sure it would not be needed since the HW was not available anymore

Look for the COM DLL : HPWMITape.dll


image

Run the uninstall command :

regsvr32 /u HPWMITape.dll

Enjoy !


Windows Server 2016 – Random Reboot Issue

August 28, 2018

We encounter 1 Windows server 2016 that suffers from a RANDOM REBOOT issue…

image

Very annoying if it happens during the working hours.

SOLUTION :

Open the Group Policy Editor : GPEdit.msc

image

Go to Administrative Templates \ Windows Components \ Windows Update \ Configure Automatic Updates 

Enable : 3 Auto Download and Notify for Install

Check the setting using  Powershell :

get-ChildItem  HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

 

image

You can run it in Powershell : sconfig

image

To check the windows update config

You can run it as well as a cmdline : sconfig

image

Run GPUPDATE using admin credentials …

image

Enjoy!


Windows Server 2016 – Memory Leak Event ID 11 Error

August 28, 2018

Encountering Event ID 11 Memory Leak in MMC ?

image

This can be safely ignore according to Microsoft

See here for more details

image

Enjoy!


Windows Server 2016 – VSSAdmin Event ID 7001 Error

August 27, 2018

Event ID 7001 relating to VSSAdmin unable to create Shadow Copy

image

Solution :

Go to task manager and check the job configurations GUID.

If you find the similar compared to the Event Viewer details. You can delete them.

Reason :

This might happen after convert a Physical machine to a VM.

Success !


Windows – WBADMIN RESTORE using the correct version IDENTIFIER

August 23, 2018

When you are going to do a restore using the WBADMIN command line.  It might be hard to find the correct backup set and location ?

These are steps that will help you to get what you need.

1. Run the command wbadmin get versions

image

Check you backup time and VERSION IDENTIFIER.

As you can see the backup time is NOT equal to the identifier date and time …

Backup ran at 7 PM and the identifier says 11:00

image

You can also see the date & time in the folder name

image

So in order to getting the correct backup data to restore you need to take the WBADMIN IDENTIFIER details.