Just to add to #11, it would be nice to specify many hosts on the same range

ex.: 192.168.1.20,25,30,35........not sure if I'm the only one that thinks it might be useful.....

1 & 2 ....  ill try to research it more.

3 ... We are a NetBIOS free zone (thank god) ... all fqdns were fed to OME ... the server inventories fine, it's just the displayname that is the problem

7 ... this was just feedback for you guys... considering OMSA is your product I expected a more seamless integration with the ability to apply OMSA updates much in the way I do system updates (not that those are working for me =) ). when I mentioned agentless is coming I meant in the sense that we would be getting servers with idrac6/7, but we don't have that now... I recognize OME 1.1 supports agentless.

Hi and thanks for the post.

Let's see if we can help out a bit here.

For 1 & 2, can you provide more detail?  It might be best for a new thread on the update trouble.  That way we can see what updates you are trying to apply, h/w, catalog version, etc.  Sometimes they drivers are waiting on a reboot, etc.  So if you can provide more background in a new post, we're happy to look at it.

For #3, are you using DNS or NetBios in your discovery preferences?

#4  I'll pass this feedback along...thanks.

For 6, 8, 9, 10, I will see if I can get a Support Assist person to reply to your specific questions.

For 7.  Again, if you can create a post on your OMSA deploy trouble I'll be happy to take a look.  BTW, agentless support _is_ in OME 1.1, so if you have an iDrac 6/7, you can discover it (WSMan protocol only) and get all of your inventory data without OMSA.

11.  Thanks for this feedback.  Again, I will share it with the team for consideration in a future release.

Regards,

Rob

#5. Thanks for feedback on SupportAssist. Manually running DSET is currently missing from SupportAssist UI. We are adding that feature in next release.

#8 This is a known issue that will be fixed in the next release.

#9The cases screen will get better with next releases where you can manually add DSET to a case from Support Assist UI.

#10. OME is a pre-requisite for SupportAssist so you will need to discover devices and configure SNMP moniotoring in OME if you are only interested on SupportAssist functionality.  

Basically, even though the updates were hidden, they are still selected ...

12. Under system update:

I select the non-compliant system tab, I then select *all* our dell servers in the "systems to update" pane.

In the "updates to apply" pane I filter the "component" column to be just the BMC firmware package. (There are only nine systems to which this update applies, so there should only be 9 packages going out)

I then select apply updates and set up the task ... I check the status and it says, "Copying 312 update packages" ... holy

... it just tried to push out every single update in the repository...

This is a dangerous bug ... I hope you guys step up your game and release bug fixes immediately rather than making us wait months for a new version. I am not out to insult or complain, but this software is by far the buggiest I have ever used.

Kroynava,

    We are unable to reproduce Item #12 in our lab.

Selected 5 servers under non-compliant systems tab and all the applicable updates were displayed (by default all checked/selected).

In the Component column filter, selected "Contains", typed "Broadcom" and hit "Filter". This filtered the results and only showed 5 Broadcom components.

Click "Apply Selected Updates" and the "System Update Task" window only showed 5 Broadcom components.

Entered the credentials and click "Finish". It started downloading only 5 Broadcom components.

Did you make sure to click "Filter" button in "Component" column filter, to apply the filter ? Otherwise the filter is not applied and rows are not filtered.

On clicking "Apply Selected Updates" did you ensure only 9 components were listed in "System Update" task ?

Are you using OME 1.0.1 or 1.1 ?

Thanks,

Raj Shresta