I apologize for the potential thread hijack, but perhaps you might be able to help me a bit.
I've just now begun messing with software updates this morning, downloaded an Update Package for Windows for the DRAC/ESM update for our 2650's. Up a task to test this but when I execute it I get the following error:
Device validation command failed with error message: The path of the executable Remote Server Administrator CLI is attempting to execute on the remote system is invalid. Make sure the executable omexec.exe is in the default path of the remote system. A reboot after installation of Server Administrator will ensure your path is correct.
I find this incredibly confusing as omexec.exe doesn't even exist on the target machine, nor does it exist on ANY of our OMSA installed servers that I can tell, including our ITA box.
If anyone has any insight into what I've missed, I would appreciate it. Thank you in advance.
Sandy, to potentially answer your question: I think the iso that you pulled down from dell only contains PowerEdge class chassis updates. I could be wrong, but that's my suspicion. I'm currently downloading it now.
Regarding the original thread about wanting to update client BIOS, you can do that via the OpenManage Client Connector 2.0 (released 3/30/2005). If you install it on the management station, and restart the services you get a new task type (Client Software Update) when creating a new software update task. You need Openmanage CLient Instrumentation 7.x on the target device for this to work.
You need to specify the BIOS hdr file in the CLI. Read the OMCC user's guide for additional information on troubleshooting and system security issues.
You can use IT Assistant's Manage Tasks option to create CLI commands.
In IT Assistant, select Manage® Tasks.
Right-click Command Line andclick New Task to display the Task Creation Wizard.
You can use the Task Creation Wizardto create a new task. Click Help in this wizard for more information.
In the Task Creation window, select Remote Client Instrumentation, which allows you to execute OMCC CLI commands remotely.
You must also specify a task name and, optionally, a brief description of your task in the Task Creation window.
enter the Argument below
system cim action=flashbios ipaddress=$IP username=$USERNAME password=$PASSWORD authenticationlevel=packet biosfile=\\servername\GX260A06.hdr
The BIOS image file must be accessible from the remote client system, which means that the biosfile argument must be presented as the full path to the image file as seen from the client. The user who runs the BIOS update must have read privileges to the location where the image is stored.
To make the .hdr file download the bios.exe from dell, in dos type GX260A06.ex -writehdrfile
SandyBryce, I failed to get this working until I read in one of the OMCC user or reference guide that UNC is not supported when referencing the BIOS hdr file.
Some people have all the luck! I failed to get it working until I read the following extract from Pg.18 of the User Guide. I tried both remote drive shares and UNC paths to no avail. All I can think is my UNC path I entered must have been wrong.
Since I changed to FTP all has been good and flashed all 90 clients with new BIOS revisions.
3
In the
BIOS IMAGE FILE
text entry box, enter the name of the file that contains the BIOS
image header file.
The image header file must be accessible from the client system, and the name entered must
be the full path to the file as seen by the client system in one of the following forms:
• http://...
• ftp://...
• A local path such as, C:\... , to a header file on the client system. Remote drive shares
dh_cts
18 Posts
0
April 11th, 2005 17:00
I find this incredibly confusing as omexec.exe doesn't even exist on the target machine, nor does it exist on ANY of our OMSA installed servers that I can tell, including our ITA box.
If anyone has any insight into what I've missed, I would appreciate it. Thank you in advance.
Sandy, to potentially answer your question: I think the iso that you pulled down from dell only contains PowerEdge class chassis updates. I could be wrong, but that's my suspicion. I'm currently downloading it now.
dh_cts
18 Posts
0
April 11th, 2005 18:00
svs
5 Posts
0
April 11th, 2005 22:00
Regarding the original thread about wanting to update client BIOS, you can do that via the OpenManage Client Connector 2.0 (released 3/30/2005). If you install it on the management station, and restart the services you get a new task type (Client Software Update) when creating a new software update task. You need Openmanage CLient Instrumentation 7.x on the target device for this to work.
You need to specify the BIOS hdr file in the CLI. Read the OMCC user's guide for additional information on troubleshooting and system security issues.
http://support.dell.com/support/edocs/software/smclicon/en/index.htm
SandyBryce
32 Posts
0
April 12th, 2005 13:00
Further Aurguments
System Restart
system cim action=restart ipaddress=$IP username=$USERNAME password=$PASSWORD authenticationlevel=packet
system cim action=setcim ipaddress=$IP username=$USERNAME password=$PASSWORD authenticationlevel=packet classpropertyvalue=dell_configuration::HDDPercentageThreshold:20
SandyBryce
32 Posts
0
April 12th, 2005 13:00
Remote BIOS Flash
You can use IT Assistant's Manage Tasks option to create CLI commands.
You must also specify a task name and, optionally, a brief description of your task in the Task Creation window.
enter the Argument below
system cim action=flashbios ipaddress=$IP username=$USERNAME password=$PASSWORD authenticationlevel=packet biosfile=\\servername\GX260A06.hdr
The BIOS image file must be accessible from the remote client system, which means that the biosfile argument must be presented as the full path to the image file as seen from the client. The user who runs the BIOS update must have read privileges to the location where the image is stored.
SGN
13 Posts
0
April 13th, 2005 03:00
SandyBryce
32 Posts
0
April 13th, 2005 07:00
UNC path seemed to work fine for me, updated the BIOS of half a dozen GX270 from A03 to A06
:smileytongue:
SGN
13 Posts
0
April 13th, 2005 21:00
image header file.
The image header file must be accessible from the client system, and the name entered must
be the full path to the file as seen by the client system in one of the following forms:
• http://...
• ftp://...
• A local path such as, C:\... , to a header file on the client system. Remote drive shares
are currently not supported by OMCI.