Start a Conversation

Unsolved

This post is more than 5 years old

23692

August 26th, 2013 13:00

OME Non Compliant Issues

OME 1.2.1 running on Wndows 2008 R2 SP1 STD.

I have discovered my servers with out issues (both OMSA and drac). One is running 2003 ENT 64B SP2 and the other is running 2008 R2 STD SP1. OME is showing both servers as non compliant. I have looked at the install packages that OME is trying push out. One package is a 32B driver and the other driver is not for my OS version (non 2003 64B). I can obvioulsy uncheck those updates so that OME does not try to push them out. This still is flagging my servers as non compliant. Does anyone know of a way to tell fix this non-compliant issue?

 

Community Manager

 • 

711 Posts

August 26th, 2013 14:00

Hi,

Thanks for your post. These issues typically result from an update being marked as applicable in the catalog for an OS where it is not really applicable. OME uses the information from catalog and compares it with gathered inventory to show the compliance. If you tell us the specific update names, we can check in the catalog and get the entries updated.

You can also use Repository Manager to create your own catalog, exclude these updates and import that catalog in OME.

Regards

Abhijit 

6 Posts

August 26th, 2013 14:00

Network_Driver_CYKKJ_WN_17.6.0.0_17.6.0.12.EXE (http://www.dell.com/support/drivers/us/en/04/DriverDetails?driverId=CYKKJ)

 This is for MS Windows 2008 x64, MS Windows Server 2012 and MS Windows 2008 R2. 2003 x64 is not listed as a supported OS.

  Network_Driver_PYKJH_WN_17.6.0.0_17.6.0.12.EXE ( http://www.dell.com/support/drivers/us/en/04/DriverDetails?driverId=PYKJH)

This is a 32B driver (listed twice under Non Complinace) that OME is picking up for both my 2003 x64 and 2008 R2 servers

Community Manager

 • 

711 Posts

August 26th, 2013 14:00

Thanks for the update. We'll send this information along to catalog team.

Regards

Abhijit

5 Posts

August 30th, 2013 15:00

It appears a new catalog was released and this issue is still not resolved.  I installed OME 1.2.0.3441 in the middle of July, and its infuriating at how poor the support for this program is.

-OME trying to install x86 drivers on a x64 machine

-OME unable to push updates, but I'm able to install them manually

-Incorrect driver version comparisons in the catalog

-Showing 90% of my servers as non-compliant due to one of the above issues. 

When will this Broadcom driver issue in the catalog be resolved?  Everything I read said that the information would be forwarded to the catalog team and be fixed in the next release.  Well, the new catalog is out and the issue remains.  Can this issue please be expedited?

Community Manager

 • 

711 Posts

September 3rd, 2013 07:00

Hi,

Thanks for your post.

The last catalog was released in mid-August (releaseID="1VFYJ") and new catalog will be released in mid Septemeber. The issues listed above are reported in August catalog which can only be resolved in the next catalog in mid-September.

OME uses catalog data for compliance comparison and once the catalog data is corrected, OME compliance reports will automatically get updated.

Regards

Abhijit

5 Posts

September 13th, 2013 12:00

I just updated to the September catalog.  This issue persists.

2 Intern

 • 

2.8K Posts

September 16th, 2013 15:00

Thanks for the follow up.  You might consider opening a ticket at 800-945-3355.

I think this has been reported to the catalog team.

Best regards,

Rob

No Events found!

Top