This post is more than 5 years old

5133

June 15th, 2020 01:00

Drivers Update in OME

Hello !

I updated OpenManage to 3.4.0 (Build 55) but I still don't have the drivers updates that are available (only firmwares).

Is that also your case?

 

 

1 Rookie

 • 

52 Posts

June 15th, 2020 01:00

@Michael LTD 

 

Please discover windows OS through In-Band and then run Driver Inventory from the Inventory tab and then select the option Run Driver Inventory.

Once we have driver inventory collected, Open Manage Enterprise would be able to get the driver inventory of the target device.

Compliance Report should be displayed for both Drivers and Firmware.

Note: We support only Windows OS with 64 Bits only.

 

Thanks,

Anil Kumar V K R

I Work For Dell

June 15th, 2020 06:00

Thank you !

I thought that the idrac discovery brought up drivers informations.

Everything is ok now 

Moderator

 • 

4K Posts

June 15th, 2020 06:00

Hello,

I can confirm the Anil answer.

Thanks

Marco

1 Rookie

 • 

97 Posts

 • 

8 Points

June 16th, 2020 06:00

What do you mean with "In-band"-discovery? Coudn't find this in the documentation and there is no such option in OM Enterprise.

June 16th, 2020 07:00

"In-band"-discovery = Windows Host Discovery with SSH

Different from Idrac discovery

1 Rookie

 • 

97 Posts

 • 

8 Points

June 16th, 2020 07:00

This is found under Device Type = "Multiple", correct?

Sorry guys, but your documentation is not the best one...

1 Rookie

 • 

52 Posts

June 16th, 2020 07:00

Hi @MdmBarbarella ,

Create Discovery task and choose Device Type = Server

 

anilkumarvkr_2-1592318677061.png

 

Choose the protocol as Windows to discover Windows Host OS

 

anilkumarvkr_0-1592318591239.png

Input the credentials (OS Credentials)

Make sure to have OpenSSH enabled in Host OS and Port 22 should be opened.

Thanks,

Anil Kumar V K R

I work for Dell

1 Rookie

 • 

97 Posts

 • 

8 Points

June 16th, 2020 08:00

That was the point I doesn't understand! This "Hyper-V" is irritating to me, because the most servers are no Hyper-V-servers of course. I thought, this means only this very special version of Windows Server called "Microsoft Hyper-V Server".

But now I got it.

Thank you.

9 Posts

October 2nd, 2020 06:00

I am trying this too, but getting this error and can't get it to work? 

: ========== EEMI Code: CJOB4068 ==========
Message: Unable to discover the device because the protocol SSH used for discovering this target is not supported.
Recommended actions: Enter a valid and supported protocol, and then retry the operation. For information about supported protocols, see the OpenManage Enterprise-Modular User's Guide available on the support site.
=======================================
Task Failed. Completed With Errors.

 

4 Posts

February 5th, 2021 19:00

You need to install OpenSSH on the server in order for it to discover it. The issue I've encountered is that even though it's discovered, it cannot see the drivers.

Here's a powershell script to do that.

https://pastebin.com/Hs9Z1RuK 

Run this on your server then run the discovery again.

 

 

No Events found!

Top