OpenManage Enterprise says I need iSM LC DUP 5.0.1.0

Thanks Joey. We are running Windows Server 2019, so I guess that's why I don't see it in the list of available software.

Hi Guys 

I'm having the same issue on a few linux hosts, idrac 6.10.00.00 deployed fine, however I have a big red cross in OME as I guess the catalogue thinks my hosts requires iSM LC DUP 5.0.1.0, I'm guessing this will be fixes in the next catalogue sync?? 

Cheers & Happy New
Mox

Hi Mox, happy new year! I agree with you. So I think this could be fixed in a catalog update. I looked to see if I could see a date and information, but frankly, I couldn't see a release document regarding it.

Also seen this issue on at least one of my systems with inability to update and it fails this morning. 

This isn't correct since it does it on all our systems for esxi, windows and linux.

We are having the same issues, I posted another topic before I saw this.  All our servers, Windows, ESXi, Linux are having this problem with iSM.

75+ servers

Dell has been famous for putting updates in Consoles (Essentials and now Enterprise) that don't work or in this case, are not needed for Windows Servers. I can't tell you how many times I've run across something like this. And so now we are stuck w/ waiting for them to put out a Catalog update or fix, which won't be quick. So frustrating. 

PS-What is your Community Accepted Solution stamp of approval all about. This isn't solved. 

Agreed, not sure why they said this was solved when its not.

I talked to Dell Pro Support and they have a case open for me currently and they are aware of the issue.  They will have to update the Catalog to fix it, but basically said its an update that was sent for a certain server, but someone selected all servers when adding it to the catalog.  No timeline given however, and my work expects Critical to be resolved immediately.  I am having to let my management know this is a false positive due to an error on Dell side.

The problem isn't solved, but my question is answered. I am running Windows, therefore I don't need to worry about it!

Thanks all.

Richard.

Hi all,

I have the same problem of Solo: I have to immediately react to critical issues, but it's the fifth day now and this catalog bug is still there !
I don't blame mistakes, nobody is perfect and everyone can make mistakes, but everybody can be efficient and promptly fix his mistakes. It's only a matter of willingness, and basically respect towards customers.

I think I've found a long way around, temp solution, I used DRM (Dells Repository Manager) to create a new local catalogue with only my servers models within, I then edited out the iSM from the catalogue.xml file, a real pain, however have me back a green under firmware compliance rather than a sea of red. 

HTH

Mox

Update, just got an email from Dell saying the following.

"The upcoming Enterprise catalog is set for release tomorrow, 1/6/2023 and there are indications some of the related issues will be addressed in that release. "

Wouldn't you think, even though someone selected "All" servers, that they'd at least TEST it in a Lab?