Unsolved

This post is more than 5 years old

4 Posts

38868

February 2nd, 2015 02:00

Running cli in OME

HI,

I would like to automate discovery in OME.

It seems that I have to use embededed CLI (LaunchOMEPowerShell.exe). But when I run this command, it opens a new PS windows, and I don't know how to pass command in this new windows like Add-DiscoveryRange.

I tried to run LaunchOMEPowerShell.exe  -Command {Add-DiscoveryRange ...}, but doesn't work. Seems that LaunchOMEPowerShell.exe doesn't accept any parameter.

Any idea how to do that ?

Regards,

Marc

2 Intern

 • 

685 Posts

February 2nd, 2015 02:00

Hi Marc,

Thanks for the query.

There is a white paper made available here: en.community.dell.com/.../20218169

Utilize it to perform various operations in OME which are not limited to just discovering devices.

Please let us know if you face any issues.

96 Posts

February 2nd, 2015 02:00

Hi Marc,

Thanks for the post!

To make "LaunchOMEPowerShell.exe" work, you just need to re-direct to "C:\Program Files\Dell\SysMgt\Essentials\bin" folder and from there LaunchOMEPowerShell.exe and then try running the command Add-DiscoveryRange.

Here are the steps:

1. From PowershellCLI, browse to C:\Program Files\Dell\SysMgt\Essentials\bin

2. LaunchOMEPowerShell.exe

3. Create CLI based discovery, i.e. Add-DiscoveryRange.

Hope this helps!

Regards

Ranveer

4 Posts

February 2nd, 2015 03:00

thank's Ranveer

But this procedure requires to manually first launch the LaunchOMEPowerShell.exe then type the command.
My goal is to do that using a simple script that can directly launch the OME command.

Problem if I launch by a script LaunchOMEPowerShell.exe, it open a new windows and as this exe seems not accept any parameter, I don't know how to automatically launch OME command in this new windows.

Regards,

Marc

96 Posts

February 2nd, 2015 23:00

Hi Marc,

I understood your requirement and i did tried to simulate the same in my setup.

My batch file just carries this:

"C:\Program Files\Dell\SysMgt\Essentials\bin\LaunchOMEPowerShell.exe"

So when i double clicked on batch file copied to folder location(C:\Program Files\Dell\SysMgt\Essentials\Tools\CLI) it re-directs to OME Command Line and from there i was able to perform CLI based operations(Ex. AddDevicesToCustomGroup) as supported in OME.

Hope this is what you are looking for!

Regards

Ranveer

4 Posts

February 3rd, 2015 00:00

Thank's Ranveer,

In fact my problem is how to combine the LaunchOMEPowerShell.exe and OME commands into a single script that can be launched by Vtom for instance.

If I understand you, I create a batch to launch LaunchOMEPowerShell.exe then if I click on it it opens a new powershell windows but I'm not able to pass to this new window OME commands I'd like to except if I manully type these commands in that powershell windows.

My goal is really to automate the discovery managed by vtom as DOM is connected to a CMDB.

The script should automatically open the DOM extended powershell and run as many DOM commands I want

At the moment, the only workaround I found until I can use OME command is to directly insert new value in the DOM database, but I would prefere to use native OME commands of course.

Regards,

Marc

4 Posts

February 9th, 2015 00:00

Hi Wayne,

That's exaclty what I was looking for.

Thank's a lot.

Marc

2 Posts

August 26th, 2016 08:00

Gentlemen, I've run into a similar problem but with remote execution of the powershell script.

In my case the powershell script is executed form a remote system/tool (HPSA). The sad part is other native commands are executed properly but the command mentioned below.

The script locally works fins, but with remote execution fails.

Any help is appreciated.

//Script

import-module "D:\Program Files\Dell\SysMgt\Essentials\Tools\CLI\Dell.OME.CLI.dll"
import-module "D:\Program Files\Dell\SysMgt\Essentials\Tools\CLI\Dell.OME.Web.Net.ServiceReference.dll"
import-module "D:\Program Files\Dell\SysMgt\Essentials\Tools\CLI\Helpers.Extensions.Cli.dll"
import-module "D:\Program Files\Dell\SysMgt\Essentials\Tools\CLI\Dell.OME.CLI.Utils.dll"
Remove-Device -DeviceName abc.**********.com

No Events found!

Top