new-omediscovery question

Hi there, thanks for choosing Dell. May we ask 1 which OME version you have and 2 was it always like this or this occurred later on? Have a great week ahead.

Hi,

could you please send us some Screenshots with step by step guide on how you do this?

regards Martin

We are running 3.5 enterprise.

And I cannot say for sure, as this is the first time attempting automation within ome.

It just doesnt make sense as to why, running a discovery within the Web interface vs running from powershell, gives 2 different results. Even when its the same discovery job.

I am running the following command via powershell

new-omediscovery    -name   $jobname   -devicetype   'server'   -hosts   @ ( $list )  -discoveryusername   "root"   -discoverypassword  $( convertto-securestring   $password   -asplaintext   -force )  -wait  

 

That works without issue, the job gets created in OME as a discovery and it runs and discovers the via idrac/wsman. 

In ome however it places these servers into OEM servers

As you can see, everything is a question mark.

However if I delete those nodes OUT of ome and run that same discovery job created via powershell, the servers will be placed into Dell IDrac servers group and then they will also be placed into the correct query group for subnet/make/model for each datacenter.

Its like running a discovery "within" the OME web site performs other actions that creating a discovery job via powershell does not initiate.

HI

So open a tech support case with dell and the openmanage team?

Bedwardo,

While researching and discussing this issue I determined I would advise you to call in to discuss with the OpenManage group, as they may want to test.

Let us know how it goes.

Hi bedwardo,

Scripting and automation isn't something we're able to support, unfortunately. The Systems Management team doesn't either, but may have some additional general suggestions for certain issues.

Are you referring to the GitHub resources located at the URL below?

https://dell.to/3nm866x

If so, I can take effort to get your feedback to the relevant groups, but there isn't a support path for those resources, as far as I am aware.

Dylan

Yes, those are the powershell modules I am working with.

This is kind of a big issue and I would like to take it as high as I can. 

Why would a discovery created by powershell not product the exact same results, if I were to then turn around and run that exact same powershell created discovery job within the web interface?

Same user account. Same idrac cred's. Nothing changes.

all help is appreciated.

Thanks for the clarification. I'm happy to pass this feedback along. There is no support path for these items, but I can make sure that the developers responsible for these scripts are aware of your report.

EDIT: I've heard back from one of my colleagues. He was able to test this internally, but was not able to replicate. Additionally, it's my understanding that the issue was related to script related and needed a pause added. Did that get it taken care of?