Hi All,
I got Dell Chassis with 16 M620 Blades. I have installed ESXi 5.1 on one blade & successfully Inventoried into Dell Open-manage. But when i am navigating to System Update Tab then i see there is no system. Attaching the screenshot for the same. I have enabled IDRAC. But don't know why its not coming into that. Can someone help me on this to see what's going wrong ?.
Thanks & Regards
Ankit
Is it not possible? I have an update for one of my ESXi boxes but when I try to push the update it tells me that this is not available through the iDRAC. If it isn't then why inform me of said update?
Also on another ESXi box, there is a power supply firmware update that constantly fails, how can I get that to complete?
Hello,
we are from EMEA Region. How can we obtain hotfix HF1001.1.2?
Thank you!
Hi,
I want to know which is the latest versión of catalog to download for OME Now I have versión 8TVRY from 31/12/2013 i say this because i have iDRAC6 that i can´t upgrade to iDRAC7.
Thanks!
MY dell inspiron 5050 laptop has bug in the keyboard.
I have to press the spacebar with immense pressure to make it work. this has been going on or a while. How to make the spacebar work properly? DO i have to change the entire keyboard??
Please tell urgently
HI,
I used OME 1.3.0.1533 which was working relatively well with minor issues. Yesterday I have installed heartheart bleed hotfix HF1006.1.3 since than I am unable to detect any iDrac.
I have removed / deleted all RAC and Servers from device and re-run the discovery and inventory. I am able to detect the servers but not iDrac.
For discovery of both I use WS-MAN although split in a different inventory groups due to different username and password.
The servers I am detecting are VMware ESX hosts without OMSA installed , hence the extra iDrac discovery.
FYI: I am able to connect / detect and test the iDrac using the username and password I specified for discovery and also I am able to the same using the troubleshooting tool.
Would anybody be able to help?
thanks
Patrick
I am trying to install OME 1.3 to a Virtual Server running on VMWare VCenter Server 5.5. The VM is running Windows Server 2008R2 64 bit. When I try to run the excutable, I get the following message:
C:]Download\OpenManageEssentials_1_3_A01.exe is not a valid Win32 application
Any ideas what might be the problem?
Absolutely *love* support assist; The single best feature in OME.
However, we recent had a drive failure in our MD3620i and it wasn't picked up by support assist; I had manually phone dell for support!
Upon investigation, support assist isn't collecting logs, but whats odd is that apparently, it doesn't need any credentials to collect system logs from powervault devices, so I'm stumped as to why it's not working. OME has connectivity to the storage and it reports into OME itself.
Pointers?
sorry for my poor english language
dell 1950 2008 x64 standard no R2
5 try to install OME 1.3
result
AccessCheck(): Client Logon credentials not authorized: Administrateur (S-1-5-21-1347695079-2297496482-3104018470-500)
Des privilèges insuffisants sont associés aux références de connexion, il est donc impossible d'exécuter la console OME. Veuillez arrêter le navigateur, vous déconnecter du système d'exploitation et vous connecter à l'aide d'un compte doté des privilèges nécessaires pour exécuter la console OME. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Local Stack Trace:
SmartConsole.ErrorHandler >> Show Dell.OME.OMEProxyManager >> ShowError SmartConsole.DataCache >> LoadCheck SmartConsole.Help.HelpManager >> Load SmartConsole.DataServiceReference.DataServiceClient >> OnGetHelpCompleted System.Threading.QueueUserWorkItemCallback >> WaitCallback_Context System.Threading.ExecutionContext >> Run System.Threading.QueueUserWorkItemCallback >> System.Threading.IThreadPoolWorkItem.ExecuteWorkItem System.Threading.ThreadPoolWorkQueue >> Dispatch System.Threading._ThreadPoolWaitCallback >> PerformWaitCallback
i am crisis !!!!
the admin group was no created in active directory
( i am on domain controler)
i TRY TO CREATE IT MANUALLY BUT SAME PROBLEM
cannot logon to ome console
best regard
I am just trying to install OME and get the following Prerequisite error:
You must install MS Visual Studio Runtime before installing the Essentials component feature of the Management Station.
When I click on the provided link, it asks if I want to install. When I answer Yes, it appears to start installation, goes back to the prerequisites screen with the same error.
Help?
Trying to deploy SAS-Drive_Firmware_XJ1HM_WN32_FS66_A08.EXE via OME and directly.
Obtained from here:
http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=XJ1HM
Downloaded numerous times.
Install fails with "The operation failed due to an invalid image file.
OS Win2k12 Standard.
Any ideas?
Thanks...
Ok I tried to run a discovery and inventory on 100 idrac6 and idrac7
I have health status with gray icon on 7 servers and still don't know why. Here an example
microcontroller version is up-to-date
troubleshooting tools is OK with SNMP / WS-MAN / PING.
Server is in RAC group. I can see informations about software inventory
IDRAC6- poweredgeR710
I tried to run a soft reset of idrac
I tried rediscover and reinventory after deleting entry in OME with no succes.
Any ideas?
What is the procedure to direct OME to send the correct DUP's to the iDRAC6?
It keeps trying to send Windows .EXE updates and this does not work.
Thanks to all, Jeff
I have noticed a problem trying to set certain CSR settings whose values contain a space using racadm on iDRACs with the latest firmware. I have a script I use to automate the configuration of all of our new DRACs, and nothing has changed recently with my script or the config it applies. Before generating a CSR for each DRAC, my script applies the cfgRacSecCsr settings from a config file.
This morning I was getting errors from racadm when trying to apply settings from the config file. I ran racadm config -c -f D:\CSR_Settings.cfg to verify the configuration file and it returned:
ERROR: Invalid value in config file.
Group: cfgRacSecurity, Object: cfgRacSecCsrOrganizationName, Value: "Company Name With Spaces", Line [3]
Editing the cfg file to remove the spaces results in it returning "RAC configuration file is valid"
This is a problem when trying to set cfgRacSecCsrOrganizationName and cfgRacSecCsrOrganizationUnit with a value that has a space in it.
I found one server that somehow still has an old version of the iDRAC firmware (version 1.30.30) and values with spaces for these settings work fine with it.
What would cause some servers that have always shown correctly in device listing in a custom device group are suddenly listing in OEM Devices?
They have the same chassis type and DRAC firmware version and discovery protocol as servers that are listing correctly.
Sometimes I think OME is possessed as it does some really wacky things sometimes.
OME Version:
1.3.0.1533