1.Install 

1.Q: Can I upgrade my OME 1.0 Open Evaluation installation to the new OME 1.0.1 version?
A: Yes.  When OME 1.0.1 ships, you will be able to easily install it over your 1.0 Open Evaluation instance.

2.Q: I cannot install OpenManage Essentials using a remote SQL Database Named instance?
A: SQL Server with named instances requires ‘SQL Server Browser’ service to be running to connect remotely.

3.Q: Will OpenManage Essentials support SQL Server ‘evaluation’ edition?
A: No, SQL Server ‘evaluation’ edition is not supported because this is a prerelease version.

4.Q:  What if I see this error when I launch the console – “HTTP Error 500.19 - Internal Server Error the requested page cannot be accessed because the related configuration data for the page is invalid.”
A:  Remove/Disable the XPress compression scheme from the configuration using the command below:

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']

OR

Add an attribute of "precondition= "64bitness" for this module entry so that it loads only in 64bit application pools.

5.Q: What if IPMI is disabled after installing BMC Utility?
A: Try restarting DSM Essentials Network Monitor Service, DSM Essentials Task Manager service and restart IIS.

6. Q: How do I change OME web service/console port after OME installation?
A: After OME installation, follow these steps:

- From Start->Run, type "regedit" and hit "Enter" to open Windows      registry.

- Navigate to HKEY_LOCAL_MACHINE->SOFTWARE->Wow6432Node->Dell Computer  Corporation->Dell OpenManage Essentials->Connection Service

- Update "ConsolePort" on the right hand side.

- Launch Start->Administrative Tools->Internet Information Services  (IIS) Manager

- Navigate to <SystemName>->Sites->OpenManage Essentials

- Right click on "OpenManage Essentials" and click "Edit Bindings".

- Edit https port number "2607".

- Restart OME Netmon, Task manager and IIS services

Note: Please do not modify http port number either in registry or IIS.

7. Q: Installation of OME takes longer on Windows 2008 SP2 X64bit. Why?
A: Installation of IIS roles services takes longer to install on Windows 2008 SP2 X64bit which causes OME installation time to increase.

2.Tasks

1.Q: What troubleshooting can I do if a software update task or remote task fails to be created or executed?
A: Make sure DSM Essentials Task Manager service is running in Windows services.

2.Q: Why am I not receiving emails after setting up email alert action?
A:  If you have an Antivirus Client installed on your system, you will need to configure it to allow emails.

3.Q: Does OME support Power control options for 8G servers?
A: Yes, Power ON (option available in Server Power Options Task), and Power OFF (option available when used in IPMI command line task, in Arguments field use: chassis power off) works on 8G servers with BMC. 

Note: If the 8G server has a DRAC4 over BMC, make sure the DRAC4 IP is pingable in Troubleshoot tool using IPMI protocol. If the RMCP ping fails, the power tasks will likely be failing. This simple check will also help to know if the connection to the RAC devices for any generation server is passed. 

4.Q: Why does the update using iDRAC taking a long time?
A:  Check your credentials. Wrong credentials may cause OME to wait for communication timeout which will result in failed task after the timeout period. If you are updating 10+ devices with wrong credentials it may take up to 2-3 hours before reporting failure.

5.Q: How can I stop command Line task with single target? 
A: A task with only one device cannot be stopped once the execution has started.

6. Q: Why does the OME Task Manager crash when the username used has a \p in remote tasks. For example: veggie\pizza.
A: This is a limitation in OME parsing logic. The workaround is to create and use a username that does not have a \p in it.

3.Discovery

1.Q: What troubleshooting can I do if a discovery task fails to be created or executed?
A: Make sure DSM Essentials Task Manager service is running in Windows services

2.Q: Why are devices discovered with WMI getting classified as Unknown?
A: WMI discovery will classify a device as unknown when the credentials for a user account in the Administrators group (not Administrator) are supplied for the discovery range in some cases.If you are seeing this issue, read the following KB article and apply the registry work around described therein.

So far, this applies to managed nodes with Windows Server 2008 R2.http://support.microsoft.com/?scid=kb;en-us;951016

3.Q. My ESXi servers are getting classified as unknowns.
A: If you are using ESXi 5.0 update 1, please install OM 7.0 VIB available at 

http://www.dell.com/support/drivers/us/en/555/DriverDetails/DriverFileFormats?DriverId=VPTVV.

You can also try increasing the timeout (setting to 10) and retry (setting to 4) values in the WS-MAN page for discovery wizard.

4.Q. My ESXi servers after few days of monitoring, becomes unknown
A:  VMware has identified an issue affecting VMware ESXi 5.0x and 5.1x where CIM monitoring applications fail to authenticate with “No space left on device” error in /var/log/syslog.log:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2043464.

This issue can cause previously discovered systems to move to an unknown status, fail to discover, or not show in both OpenManage Essentials (OME) and Dell Management Plugin for VMware vCenter (DMPVV).

The current workaround is to issue “/etc/init.d/wsman restart” on the ESXi host shell.While a permanent solution to this issue has not been identified by VMware as of 13 March 2013, the following steps can be followed to create a persistent cron job to restart the wsman service once a day.

Add the following to /etc/rc.local (for ESXi 5.1 systems edit: /etc/rc.local.d/local.sh):

# Added by Dell to add cronjob for restarting wsman 12:15 AM/PM

/bin/kill $(cat /var/run/crond.pid)

/bin/echo '15   0,12 *   *   *   /etc/init.d/wsman restart' >> /var/spool/cron/crontabs/root

/bin/busybox crond

Execute auto-backup.sh (sh /sbin/auto-backup.sh) after making edits.

Reboot the system.

On reboot “cat /var/spool/cron/crontabs/root” should show:

#min hour day mon dow command

1    1    *   *   *   /sbin/tmpwatch.py

1    *    *   *   *   /sbin/auto-backup.sh

0    *    *   *   *   /usr/lib/vmware/vmksummary/log-heartbeat.py

*/5  *    *   *   *   /sbin/hostd-probe

15   0,12 *   *   *   /etc/init.d/wsman restart

NOTE: In previous releases of ESXi, you could add custom commands in /etc/rc.local which would automatically execute after all startup scripts have finished. With the latest release of ESXi 5.1, this functionality has been moved to /etc/rc.local.d/local.sh.

5.Q: What is the most important thing to know about Discovery?
A: You must install Dell OpenManage Server Administrator (aka OMSA) on all of the PowerEdge Servers that you want to discover and manage using SNMP protocol.  OMSA can be installed from the OME console.

You can also discover PowerEdge Servers using WMI without OMSA installed. Your servers will not be classified as a "Dell Computer", but rather, "Unknown" or just "Computer".  Management capabilities in OpenManage Essentials are limited if OMSA is not installed.

6.Q: Why do my Servers appear under the "Unknown" node in the device tree?
A: Systems discovered with SNMP only, and without OMSA installed on them, will be classified as "Unknown" and displayed under the "Unknown" device group.  If you have confirmed that OMSA is correctly installed on the managed node, then check the SNMP settings.  

Note: SNMP community strings are *case sensitive*.

Bring up services.msc on the managed node and go to the properties page for "SNMP Service".

On the Security tab, there is a radio button for "Accept SNMP Packets from any host" and "...packets from these hosts". You need to be sure and specify your OME server here, or select the radio button for "any host".  

If you select "any host" consult the Microsoft documentation for any security implications.

For Linux machines, make sure to run '/etc/init.d/dataeng enablesnmp' followed by '/etc/init.d/dataeng restart'

Finally, the Dell Troubleshooting Tool, installed as part of OME, is very useful in helping with Discovery problems.

Run the "Services" test as well from the Troubleshooting tool and see if you are finding the following entry in the test result
dsm_sa_datamgrd
dsm_sa_eventmgr
dsm_sa_snmpd
dsm_om_shrsvcd
dsm_om_connsvcd
These are OMSA services running on the remote box. If these entries are present in the result and if you are allowed to restart these services on that remote production system, Please do. Services can restarted from the service manager (Service names are prefixed with "DSM SA")

7.Q: Are there any considerations when trying to discover servers that have Windows 2008 as the operating system?
A: When using SNMP, in order to discover a system that is running Windows Server 2008, the "Network discovery" feature must be enabled.

Perform the following steps to enable "Network discovery" on the target Server:

-Navigate to the target system's Control Panel

-Select "Network and Sharing Center"

-In the "Sharing and Discovery" section, set "Network discovery" to "On"

8.Q: Looking at my systems, I see "System Is Down" for a server - can you tell me how this is determined? And also, how often is it re-checked?
A: The connection state shows 'ON or 'OFF' under device summary table in the LHS. When the system /device is removed from the network either power off or NIC cable removed then the state for the system is shown as 'system is down'. Basically when the server is not pingable we see server as down. By default polling for connection state is 1 hour. User has option to configure the frequency of polling.

9.Q: What troubleshooting can I do if a server is showing up as unknown or not returning inventory data even after SNMP is enabled and OMSA is installed on the target server?
A: Make sure DSM SA Data Manager Service is running in Windows services on the target server.  If it is stopped, restart the service and re-run the inventory task. 

10.Q: How should I discover my EqualLogic storage array?
A: EqualLogic arrays are discovered with the SNMP v2 protocol.  So in your OME discovery wizard, choose SNMP along with the appropriate ‘read’ community string.  Also, you should include the IP address of the EqualLogic Group and IP addresses for all the members in the discovery range.

11.Q: Why is the iDRAC 6 IP address shown as 0.0.0.0 in OME?
A: If the iDRAC firmware version on the Rack/Tower servers is <= 1.70 and on Modular servers is <= 3.30, the IP address is returned as 0.0.0.0.

Please update the iDRAC firmware on Rack/Tower servers to 1.80 and on modular servers to 3.30, to resolve this issue.

12.Q: I have VRTX devices discovered in OME versions prior to 1.2, but when upgrading to version 1.2 they do not show up under VRTX group in the device tree. How can I fix this?
A: Delete the devices from the device tree and then re-run discovery/inventory on the proper ranges to appropriately classify the VRTX devices in the VRTX device group.

13.Q: Why is my EqualLogic blade device not classified under the Modular group?
A: Make sure the chassis service tag in EqualLogic is populated for that to be classified under Modular group.

14.Q: Why does the discovery of PC 8132 with FW version: 5.0.0.4 take more than 2 minutes?
A: This is a known issue with this firmware.  Please update to the latest firmware if available.

15. Q: Why is KVM 4332DS not getting classified under KVM?
A: Update the KVM to the latest firmware (version 1.16 or later ) to classify it correctly.

16. Q: Why are my iDRACs are being deleted and re-added during a long discovery and inventory?
A: To enable the DNS iDRAC<>Server name correlation, the discovery name resolution was changed from DNS to NetBIOS. As a result servers and iDRACs that are initially discovered correctly, upon subsequent inventory and discovery, are removed and re-added to the GUI. There is no other impact to the device list. When discovery completes, all iDRACs are correctly re-added.

17. Q: DSA (LASSO) collection of logs from EqualLogic group upon receiving an event is either not proper, or, is incomplete. Why?
A: Discover EqualLogic storage groups using the Group Management or Storage Group IP address only, and not include any of the member IP addresses in the discovery range configuration.

18. Q: What troubleshooting can I do if tasks such as OMSA deployment, iDRAC Service Module deployment, or system update fail with an "invalid package signature" error?
A: Install the VeriSign Class 3 Public Primary Certification Authority - G5 certificate on the server running OpenManage Essentials.

4.Inventory

1.Q: What troubleshooting can I do if an inventory task fails to be created or executed?
A: Make sure DSM Essentials Task Manager service is running in Windows services.

2.Q:  What do I need to do if I do not see any inventory data for a Dell Server running ESXi 5.0?
A: To properly discover, inventory and classify a Dell Server running ESXi 5.0 you must install OpenManage Offline Bundle and VIB 6.5 A02 from support.dell.com which will be available in Q4 2011.

3.Q: How do I update the inconsistent data seen in the device details and Modular Enclosure Information report for a PowerEdge VRTX CMC (chassis management controller), after performing discovery and inventory using WS-Man when all the server slots of the chassis are empty?
A: PowerEdge VRTX only reports data for server slots with a modular server present and does not report any data for empty server slots.

OME does not update the inventory of a device if no changes are seen in the existing data for the device. Since empty server slots in the VRTX chassis are not reported, OME does not see any updated data for the VRTX CMC inventory and thus does not update the device inventory details.

This behavior is not seen if the PowerEdge VRTX chassis has at least one modular server present at the time of inventory.The Modular Enclosure Information report may show a row with empty values for Slot Number, Slot Name columns and "Unknown" value for the Slot Availability column when the PowerEdge VRTX chassis is discovered and inventoried while all the server slots are empty.  

In order to show the most current device inventory details of an empty PowerEdge VRTX chassis, you must remove the instance of the device from the device tree and re-discover and inventory the IP address or hostname of the CMC in question. 

4.Q: Why does the PCIe Information and Virtual Adapter Information table in the PowerEdge VRTX device details page continue to show the server name of a modular server that has been removed from the VRTX chassis, after the CMC has been re-inventoried?
A: The device details of a PowerEdge VRTX modular chassis will not update successfully if the VRTX Chassis Management Controller is re-inventoried when all the chassis server slots are empty.  

This behavior will impact data tables which show association of the modular server slots to the PowerEdge VRTX chassis resources, such as the PCIe Information, Virtual Adapter Information and Virtual Disk Access Policy Information tables.  To update these tables to reflect the correct data, in this scenario, the instance of the VRTX CMC must be removed from the device tree and re-discovered and inventoried.

5. Q: Why is the output power supply shown as 0 watts in the PowerSupply info table for my server with a cabled PSU?
A: For servers with cabled PSU, the output power supply info will be shown as 0 watts. E.g.: T430 server.

5.Health

1.Q: Does OMSA need to be installed on a server to retrieve health status?
A: For servers discovered via WMI where OMSA is not installed and running, health status will only be what the OS provides.  For maximum hardware health status you should install OMSA.

2.Q: Why does OME show power supply health as Normal when the redundant power supply has lost an AC power source?
A: This is the issue with Server Administrator version 6.x. To avoid this issue, please install/upgrade to Server Administrator version 7.0 or higher.

3. Q: Why is Device count and Rollup health showing 0 when REST API command is used for a group marked hidden in the OpenManage Essentials Console?

A: The REST API used to return information about a Device Group ( <base-uri>/DeviceGroups/{deviceGroupId} ) should not be used on device groups that are marked hidden in the OpenManage Essentials console.The information returned using this command is not correct since the data for a hidden device group is inaccessible.

4. Q: Why is my PowerConnect W series switch not showing device health?
A: The health attribute is only available if the PowerConnect W switch is in the master role.

6.System Update

1.Q: I can’t load a Dell catalog for software update or am getting errors when trying to run software update tasks, what might be the problem?
A:  First, try downloading the catalog to the OpenManage Essentials system directly or use an SUU DVD in the local system drive.

-Browse for catalog.xml file on the local system or DVD (not on a file share.  

It is possible to use a file share, but for troubleshooting, do not use file share)

-Load catalog and verify it shows as loaded in OpenManage Essentials. You may also wish to try using the FTP download to get the latest catalog for troubleshooting purposes if you can’t load other catalogs.

-Now create software update tasks.  If tasks fail, more information can be found in the task details.

-Try setting all internet explorer security settings to LOW if tasks will not run when executed.

2.Q: What do I need to do if Linux servers show under 'Non--Inventoried systems' even after I performed inventory on the discovered Linux servers 'N' number of times?

A: For RHEL 5.5, SLES10 and SLES11

1.Mount OMSA6.5 DVD in the Linux server.

2.Install 'srvadmin-cm' rpm.

3.Restart OMSA services.

4.Make sure OMSA inventory collector is working fine(Run ./invcol -outc=/home/inv.xml from /opt/dell/srvadmin/sbin/invcol location).

5.Re-inventory the Linux server in OME.

Now the Linux server will be either listed under 'Compliant systems' or 'Non-Compliant systems'.

3.Q: What order are packages installed on a system?
A: Packages are applied in the following order.-Driver-Firmware-Firmware ES-BIOS-Application

4.Q: What do I need to do when I see this error “Attempted to perform an unauthorized operation.” when performing a catalog import task?
A: The user needs to modify the permissions of the folder on the network share to allow the local user access.  When you are in a workgroup and not on a domain, access to a network share will be restricted so if you need to utilize a network share you will need to make sure OME is running on a machine on a domain.  

The OpenManage Essentials user has to be authenticated on the domain and the network share has to be authenticated on that domain as well.
When using Repository manager as you catalog source make sure that the packages associated with the RM generated catalog are present in the same folder as the catalog.
If the packages are not present in that folder you would see an invalid path result for the packages.

5.Q:  How do I configure Internet Explorer with Enhanced Security Configuration to ensure OpenManage Essentials can utilize all features that use resources from Dell Online?
A: To insure that these features work in the Dell Open Manage Essentials console on an environment with Internet Explorer Enhanced Security Configuration enabled.

The user needs to add *.dell.com to the Trusted sites zone.Import Catalog and System Update require internet access when the user selects Dell Online as the source.

The warranty report also uses Dell Online resources to retrieve information and also will not return data without it.

6.Q: When I try to run system updates in OME I get the following error- “Access to path ‘C:\Program Files (x86)\Dell\SysMgt\Essentials\SystemUpdate is denied”.
A: This is due to Windows 2008 R2 folder restrictions in the program files directory.  

Open folder – C:\Program Files (x86)\Dell\SysMgt\Essentials\In the Essentials folder make a new folder named: SystemUpdate

-Right Click

– SystemUpdate folder

-Select Properties

-Select Security tab

-Click Edit

-Select Users

-Select Full control

-Click OK

-Click OK

Then recreate the update task.

7.Q: Why does System update task show as failed in spite of successfully updating the server?
A: After executing the software update task which requires target server to be restarted, if target server does not come up within 30 minutes the task will show as failed in spite of successfully updating the server.  In that case you will have to run the inventory for the server separately to see the updated version on inventory page and compliance report.

8.Q: Why am I not seeing software inventory for a server or why does the server show up in the non-inventory state even though I executed an inventory task against it?
A: Do the following:Make sure OMSA is installed the server.

Check: C:\Program Files\Dell\SysMgt\oma\log

Delete all of the files except for the cachecfg.txt. Once the files are removed you will need to restart the DSM SA Shared Services within Services.msc. Once the DSM SA Shared Services has successfully restarted it may take up to 90 secs to repopulate the updated inventory files (Note: The new files will consist of the cachecfg.txt, Inventory.xml.1 and InvLog.xml)

9.Q: I have OpenManage Essentials installed and successfully discovered and inventoried my 11G servers. I downloaded the update catalog and have identified some servers that our non-compliant. When I run the update task it goes to 100% complete in less than 2 seconds and no update occurs.....any ideas?
A: Providing full control NTFS permissions to the C:\Program Files (x86)\Dell\SysMgt\Essentials\SystemUpdate folder has corrected the problem. The job runs successfully now.

10.Q: Can you re-run system update tasks on the same target that have not completed?
A: Previously Executed System update tasks can be re-run. It is not recommended to re-run the system update task for the same target while the first one is not complete as it will result in OME resending the same updates again.

11.Q: What do I do if SUU Import Catalog for System Update failed with this error “Exception message: Error: 1205, Procedure: usp_Catalog_Insert, Message: Transaction (Process ID 69) was deadlocked"?
A: Daemon Lite is not supported for mounting the ISO. If you are using Daemon Lite to mount the ISO, use MagicDisk or Virtual Clone Drive.

12.Q: I am unable to push updates to VRTX Chassis, why?
A: The VRTX chassis must be discovered and inventoried using WS-Man protocol for OpenManage Essentials to push updates. OpenManage Essentials does not support the update feature for the VRTX chassis using SNMP discovery and inventory.

13.Q: My compliance report pie chart disappeared or is not showing. How do I make it visible again?
A:  

-Refresh your browser.Or

-Click the ‘Filtered by: All Update Devices’ link next to the ‘System Update’ portal title.

-Check ‘All Update Devices’ in the device selection tree.

-Click ‘Apply’.

Within 30 seconds the pie chart will reappear.Note: If the chart still does not appear, make sure all devices are discovered and inventoried, and verify your catalog.

14. Q: When Plasma HA has 2 PERC controllers with different versions, the one with the lower version is shown in the software inventory information table. Why?
A: OME shows a single PERC because the two PERCs cannot be differentiated in the OME inventory. If the Plasma HA PERC versions are different then the user needs to update the PERC manually from the CMC console.

15. Q: Why does my update sent via iDrac fail even though I have provided the right credentials and there is no connection problem?
A: It is possible that the iDRAC SSL configuration need to be reset to correctly authenticate the connection, in order to successfully update any system components via WSMAN. Execute the below command for every iDRAC that fails updates and then rerun the update task.

racadm sslresetcfg

16. Q: The iDRAC is not able to download the packages and update tasks using WSMAN fail. The IP address of the OME server in the URI is blank.
A: OME uses DNS to create the URI to download the DUPs to iDRAC. Ensure your DNS is configured correctly and hostname resolves to IP Address. Also ensure that the DNS does not accidentally have a loopback address alone.

17. Q: When the server (MN) inventory is within 5mins after the reboot, older version of the firmware is displayed in OME UI.
A: You can manually run the inventory again or wait for the scheduled inventory cycle in OME to see the updated versions in OME.

18. Q: System with iDRAC firmware version 1.30.30 is not showing up as compliant. Why?
A: System iDRAC version 1.30.30 will never show up as complaint because the systemID return by the OME inventory is invalid.
The iDRAC need to be upgraded to version 1.40.40 or above to see valid systemID.

19. Q: I don't see upgrades for 9G and 10G servers when the catalog source is SUU.Why?
A: There are separate catalogs. 9G and 10G server updates are present in one SUU whereas 11G and 12G are present in another SUU.

20. Q: What do I need to do if an out-of-band system update task fails and the task description displays a message stating that "The specified URI is invalid."?
A: To resolve the issue, do one of the following:
     Ensure that the following ports are open on the firewall:
         - Port 442 (for WS-Man)
         - Port 80 (for HTTP)
         - Port 1279 (for task manager)
     Disable the firewall

7.Reports

1.Q:  Why is Virtual Machine Information and Virtual Machine Host Product information Tables missing in ESX Sever Device Details? 
A: The SNMP agent for this system may not be properly configured and is not returning any data for the VMWARE OID.

2.Q: On the Reports page, why does Device name shows as IP Address instead of the actual Device Name?
A: The IP address will be displayed instead of device names only when devices from which the alerts received is not discovered in OME.

3.Q: What do I need to do if the warranty report is not getting populated after running inventory?
A:  This can happen if OME cannot communicate with Dell Warranty websites if you have enhanced security configuration enabled for Internet Explorer. You can add api.dell.com and lt.dell.com websites to the trusted list for warranty report to work. Alternatively you can disable the enhanced security configuration.

4. Q: Why are the reports on home portal missing after upgrade from 1.2 to 1.3?
The custom portal layout saved in the database in OME 1.2 is not compatible with the custom portal layout in OME 1.3.
On upgrade from OME 1.2 to OME 1.3 if a user had a custom portal layout saved, this layout will be discarded and the default portal layout will be presented to the user.

8.Preferences

1.Q: Can I increase the console maximum timeout setting from 6 hours.
A: No, 6 hours is the maximum timeout setting.  The session timeout gives the application the ability to clean up the database.



9.Troubleshooting

1.Q: Where can I find the logs to help troubleshoot install issues? 
A: Check the ‘InstallUtil.log’ file for any install issues. This file is located in your windows temp directory.

2.Q: What do I need to do if I see this message "You do not have permissions to alter these settings.  Please contact your system administrator. "?
A: If you used a domain account to install OpenManage Essentials you will need to add that account to the local administrators group and run iisreset from the command line.

3.Q: When I try to run system updates in OME I get the following error- “Access to path ‘C:\Program Files (x86)\Dell\SysMgt\Essentials\SystemUpdate is denied”?

A: This is due to Windows 2008 R2 folder restrictions in the program files directory.  

-Open folder

– C:\Program Files (x86)\Dell\SysMgt\Essentials\-

In the Essentials folder make a new folder named: SystemUpdate
1.Right Click – SystemUpdate folder

2.Select – Properties

3.Select – Security tab

4.Click – Edit

5.Select – Users

6.Select – Full control

7.Click – OK

8.Click – OK
-Then recreate the update task.

4.Q: What do I do if I can’t find the right click option for OMSA launch although OMSA is installed on the target server?
A: You can delete and rediscover the same device which will show the right click option for launching OMSA.

5.Q: What do I need to do if all SNMP traps from an ESXi 5 host show up in OME as unknown?
A:  You have to change the hardware event source in the SNMP config on the ESXi 5 host from CIM to IPMI.

Run the following commands:

vicfg-snmp.pl --username root --password <yourpassword> --server <yourserver> --hwsrc sensors

The output of the --show command then should be:

Current SNMP agent settings:

Enabled  : 1

UDP port : 161

Communities : public

Notification targets : <myOMEservername>@162/public

Options : EnvEventSource=sensors

6.Q: What do I need to do if the warranty report is not getting populated after running inventory?
A:  This can happen if OME cannot communicate with Dell Warranty websites if you have enhanced security configuration enabled for Internet Explorer.

You can add api.dell.com and lt.dell.com websites to the trusted list for warranty report to work. Alternatively you can disable the enhanced security configuration.

7.Q: Why is OME unable to create a connection to SQL Server?
A: This is only 1 of many possible solutions:

Make sure TCP/IP is enabled using SQL Server Configuration Manager-Start Menu \ All Programs \ Microsoft SQL Server 2008 R2 \ Configuration Tools \ SQL Server Configuration Manager-Under SQL Server Network Configuration select ‘Protocols’ for each instance, Set the TCP/IP to Enabled.

8.Q: What can I do if my health status shows as unknown for my VM ESXi 5.x hosts?
A: For 12G servers, discover the iDRAC7 using WSMAN protocol to retrieve hardware inventory and health status. For older generation of servers, follow these steps:
Run this command from OS command prompt in OME server:

winrm i SendCmd cimv2/DCIM_OEM_DataAccessModule?__cimnamespace=root/dcim/sysman+InstanceID=DCIM_OEM_DataAccessModule1 @{CommandAndArguments="omacmd=getchildlist showbody=true showobjhead=true recurse=true computeobjstatus=true byobjtype=17 poid=2 comp=MainChassis daname=dceda"} -r:https://ESXiIPAddress:443/wsman -u:Username -p:Password -skipCNcheck -skipCAcheck -skipRevocationcheck -a:Basic -encoding:utf-8

Make sure to provide actual values for these three fields in the above syntax:

ESXiIPAddress

Username

Password

The command should return this info:

SendCmd_OUTPUTResultCode = 0ReturnValue = <MainSystemChassis ons="Root/MainSystemChassis" instance="0" creatoralias="dsm_sa_datamgr32" creatordisplay="Systems Management Data Manager"><oid>2</oid><objtype>17</objtype><objstatus>4</objstatus></MainSystemChassis><ObjCount>1</ObjCount><computedobjstatus strval="CRITICAL">4</computedobjstatus><SMStatus s32val="0" strval="SUCCESS">0</SMStatus>

If the command fails or does not return the above data, you may need to troubleshoot further:Reboot the ESXi server host once and run the command again. Make sure OMSA VIB is installed on the ESXi host.

9.Q: After installing OME 1.2 on Windows 2012, the UI goes blank automatically when the system is idle and is only refreshed on mouse over or browser refresh.
A: Try Installing latest MS-

Updates from Microsoft using “Control panel > Windows Updates” and verify IE10 version has to be greater than >16384.

10.Q: Why is my EqualLogic blade device not classified under the Modular group?
A: Make sure the chassis service tag in EqualLogic is populated for that to be classified under Modular group.


10.Misc.

1.Q: What ports and protocols are needed to be opened for proper access to the Essentials server?
A: Many ports and protocols...snmp, http, https, omremote, rpc, smb, 2607… and also add exe file copy over http.  

2.Q: What are SNMP “authentication traps”?
A: An authentication trap is sent when the SNMP agent is hit with an inquiry with a community name it does not recognize. These are case-sensitive also.The traps are useful to know if someone is probing your system, although its better nowadays to just sniff packets and find out the community name that way.If you use multiple community names on the network, and some management might overlap, people may want to turn these off as they become false positives (annoyances).

From MS (http://technet.microsoft.com/en-us/library/cc959663.aspx):Send Authentication Traps. When an SNMP agent receives a request that does not contain a valid community name or the host that is sending the message is not on the list of acceptable hosts, the agent can send an authentication trap message to one or more trap destinations (management systems). The trap message indicates that the SNMP request failed authentication. This is a default setting. 

3.Q:  Why is OME CLI functionality not working?
A: OME CLI functionality will not work when non default port is used for installing OME. If you want to use the CLI functionality, make sure that the default port 2607 is used during installation.

4.Q: Unable to delete nested custom groups from OME CLI, Why?
A: OME CLI functionality will not work when non default port is used for installing OME. If you want to use the CLI functionality, make sure that the default port 2607 is used during installation.

5.Q: Where can I get the files used to install OMSA?
A: See below links:

Microsoft Windows

Install and upgrades

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-WIN-6.5.0-2247_A01.10.exe

Major Upgrades

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-DUP-WIN-6.5.0-2247_A01.8.exe

Minor Upgrades

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-SP-WIN-6.5.0-2247_A01.12.msp

Citrix XenServer

Version 5.6

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.XenServer56_A01.11.iso

VMware ESXi Version 4.1

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-6.5.0-2247.VIB-ESX41i_A01.zip

Linux Distribution Bundle containing the below listed packages (they can also be downloaded individually)

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247_A01.15.tar.gz

VMware ESX Version 4.1

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.ESX41.i386_A01.tar.gz

Red Hat Enterprise Linux 

Version 5 i386

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.RHEL5.i386_A01.3.tar.gz

Version 5 x86 and x64

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.RHEL5.x86_64_A01.4.tar.gz

Version 6 x86 and x64

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.RHEL6.x86_64_A01.5.tar.gz

SUSE Linux Enterprise

Version 10 i386

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.SLES10.i386_A01.13.tar.gz

Version 10 x86 and x64

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.SLES10.x86_64_A01.6.tar.gz

Version 11 i386

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.SLES11.i386_A01.14.tar.gz

Version 11 x86 and x64

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.SLES11.x86_64_A01.7.tar.gz

6.Q. Why are the alerts and task schedules in OME display a timestamp which is off by 1 hour?
A: Check the location settings for the server in “Regional and language settings” under control panel to make sure the location for the server and date/time formats are set appropriately for the region where the server is located.

7. Q: Why is OME taking a long time to launch or traverse through various pages?
A: Please check if the windows update is running in the background. Windows update impacts the SQL performance if the update is related to SQL which in turn affects OME’s performance. Once the update is complete, Reboot your machine and launch OME again.

8.Q:  OME does not launch and throws an error message stating “An add-on for this website failed to run”
A: Add the OME URL to the exceptions list in the Internet Explorer options -> Security -> Local Intranet -> Sites -> Advanced ->

9. Q:  OME memory consumption shoots up when I have logged in as a domain user. What do I do to fix this issue?
A: Disable/Uncheck the following settings in the IE browser

• Check for Publisher’s certificate revocation

• Check for server certificate revocation

10. Q:  After running Discovery /Inventory on a system running Linux, command line task is failing with error message "unable to generate a Trusted Key for Linux"
A: Run an OMSA Deployment Task  which will successfully generate the Trusted Key. Once the OMSA deployment task complete you can run the Command Line Task on the target  because the new SSH Key would have been generated 

11. Q: I am using IE 11 and have enabled ActiveX, but I cannot launch the Troubleshooting Tool. Why?
A: Make sure you have the latest updates from Microsoft installed on the system. Older versions of IE 11 may have compatibility issues.

11.Compellent Known Issues

1.Q: The health status is not returned correctly by the Dell-Compellent device and OME shows the health state as unknown.
A: The fix is part of the Dell-Compellent firmware version 6.3.10 or above. Please make sure your Dell-Compellent device has the latest firmware installed.

2.Q: OME shows the Dell-Compellent Agent Version as 'M'.
A: The fix is part of the Dell-Compellent firmware version 6.3.10 or above. Please make sure your Dell-Compellent device has the latest firmware installed.

3.Q: Inventory details are not shown for most of the tables and it is shown as N/A in OME for Dell-Compellent viz Controller Information table, Enclosure Information table, Physical Disk Information table OR Most of the details in the reports for Dell Compellent are empty.
A: The fix is part of the Dell-Compellent firmware version 6.3.10 or above. Please make sure your Dell-Compellent device has the latest firmware installed.

4.Q: Service tag is not shown for Dell-Compellent device by OME.
A: The fix is part of future Dell-Compellent firmware. Please make sure your Dell-Compellent device has the latest firmware installed.

5.Q: OME does not show the model information for Dell-Compellent.
A: The fix is part of future Dell-Compellent firmware. Please make sure your Dell-Compellent device has the latest firmware installed

6. Q: When I discover a RAC device for my Compellent storage, I don’t see an entry for it in the OME device tree under the RAC device group.
A: When both the Compellent storage device and the RAC device are discovered in OME, OME 1.3 correlates the RAC device for Compellent. The information for the RAC device can be seen under Dell Compellent Arrays group by looking at the inventory information of the Compellent Storage device.

12. Configuration

1. Q: Are there restrictions on attributes like device name when using the Create Template feature to get a Chassis configuration?
A: For attributes that a user can create, we require that they do not contain brackets (‘[‘ or ‘]’).

2. Q: I set new minimum bandwidths for my partitioned NIC and deployment fails.The total minimum bandwidth I set adds up to 100 per partition.Why would I get an error on “MinBandwidth”?
A: When you deploy new bandwidths they are processed one at a time in order.If the new value increases the total “MinBandwidth” over 100 it will fail to deploy.Set the new values to zero as an intermediate step before applying the desired values if you get this error.

Example

MinBandwidth
OLD     20, 20, 30, 30
NEW     70, 10, 10, 10 – This will FAIL with old value 20 and new value will be blank

OpenManage Connections enable IT Administrators to:

• Improve operational efficiency and flexibility in managing large heterogeneous data center environments
• Extract richer information about the health and behavior of Dell PowerEdge servers, Dell PowerVault servers and storage and EqualLogic PS-Series Storage Arrays
• Make informed and rapid decisions impacting  the availability of data center resources  
• Utilize an existing systems management investment to easily integrate and manage Dell hardware within their infrastructure
• Complete Logical view helps administrators to better manage their Dell environments (Dell Blades/Chassis, EqualLogic Storage Pools)
• Support for operator controlled trap resolution through detailed knowledge articles (resolution instructions).
• Automatic alert correlation for quicker fault detection and resolution

Products in Dell OpenManage Connections

CA Network and Systems Management

• Dell OpenManage Connection for CA Network and Systems Management (NSM)

HP Operations Manager

• Dell OpenManage Connection for HP Operations Manager

IBM Tivoli Netcool/OMNIbus

• Dell OpenManage Connection for IBM Tivoli Netcool/OMNIbus

IBM Tivoli Enterprise Console

• Dell OpenManage Connection for IBM Tivoli Enterprise Console

IBM Tivoli Network Manager (ITNM)

• Dell OpenManage Connection for IBM Tivoli Network Manager IP Edition

Nagios

Welcome to Dell Repository Manager

Dell Repository Manager (DRM) is an application that allows IT Administrators to easily manage system updates. Dell Repository Manager provides a searchable interface used to create custom software collections known as bundles and repositories of Dell Update Packages (DUPs).

These bundles and repositories allow for the deployment of multiple firmware updates at once. 

A Dell Update Package (DUP) is a self-contained executable in a standard package format that updates a software element on a Dell server such as the BIOS, a device driver, firmware, and other similar software updates.

Additionally, Dell Repository Manager makes it easier to locate specific updates for a particular platform, which saves time.

See a screenshot of the Data Center Version GUI

 How does Dell Repository Manager Work?

DRM connects to Dell's online catalog of updates that contains information on the available Dell Update Packages (DUPs). Once you have selected your updates, Dell Repository Manager downloads the specific file(s) you have requested.

Repository Manager can also compare differences between two repositories at both the bundle and component level. It allows you to create deployment tools using your custom repository. Repository Manager is available for Dell Data Center (Server, Storage, Networking) and Dell Enterprise client products. The Data Center version can create and manage repositories for Dell PowerEdge servers, select EquaLogic, PowerVault & Compellent storage as well as select PowerConnect and Force10 networking switches.  The Dell Client version manages updates for Dell Latitude, Precision Workstation and OptiPlex client systems.

Dell Repository Manager integrates with Dell systems management products such as Dell OpenManage Essentials console and the Dell Management Plug-in for VMware vCenter. Dell Repository Manager automates creation of custom repositories by reading inventory information from these consoles and creating of a set of updates that is newer than what is currently installed.  

What's New + Downloads

  ( top )

( top )

  ( top )

Dell OpenManage Plug-in for Nagios Core provides a proactive approach to data center management that delivers features for monitoring 12th and later generation of Dell PowerEdge servers in environments managed by Nagios Core console. With this plug-in, customers have comprehensive hardware-level visibility of Dell PowerEdge servers including overall and component-level health monitoring for quicker fault detection and resolution. The plug-in protects an IT organization’s existing investment in Nagios Core console and helps ease the integration and monitoring of Dell servers.

Product features

• Discover and monitor Dell’s 12th and later generation of PowerEdge servers through an agent-free, out-of-band method using Integrated Dell Remote Access Controller (iDRAC) with Lifecycle Controller
• Monitor overall and component-level (such as Fan, Battery, Physical disk, Virtual disk, Fan, Battery, NIC, Intrusion, and so on) health status of Dell servers using SNMP or WS-MAN protocol
• Monitor SNMP alerts from supported devices
• Provide basic system information including component-level details about Dell servers
• Launch iDRAC web console from Nagios Core to perform further troubleshooting, configuration, or management activities

Business Benefits

• Protect existing investment in Nagios Core product to easily integrate and monitor Dell servers within customer’s infrastructure
• Improve operational efficiency and flexibility in managing large heterogeneous data center environment
• Increase productivity by reducing time to maintain, monitor and troubleshoot any issue in server infrastructure
• Make informed and rapid decisions impacting the availability of data center resources

Customers can choose to monitor Dell servers without software agents by leveraging agent-free, out-of-band technology using iDRAC with Lifecycle Controller. By using out-of-band management, IT administrators no longer need to install or periodically certify/validate the traditional in-band OpenManage Server Administrator (OMSA) agent installed in the server Operating System (OS). This out-of-band management technology allows IT administrators to effectively monitor Dell systems with increased availability from any location, and without the use of agents. It accomplishes this regardless of operating system or hypervisor presence or state.

Dell OpenManage Plug-in version 1.0 for Nagios Core is available as a software download offered at no charge for customers.

Product Download 

• Dell OpenManage Plug-in version 1.0 for Nagios Core

Technical Article & Wikis

• Agent-free Monitoring of Dell PowerEdge 12G Servers in Nagios Core and Nagios XI Whitepaper (BETA release)

Contents: -Fixes   Downloads

*Applicability: This field is applicable for the patch releases and provides details of the previous version of OMSA which should be installed before installing the patch.

*Fix/Enhancements:This field provides details on fixes included in the patch release. 

**Legacy PowerEdge Servers: 9th Generation, 10th Generation, 11th Generation and 12th Generation.

Examples:

9th Generation PowerEdge Servers: 1950, 2950, 6950 and so on

10th Generation PowerEdge Servers: M605, R300, R305, T105 and so on

11th Generation PowerEdge Servers: M610, M910, R415, T110 and so on

12th Generation PowerEdge Servers: M620, R720, R720XD, T420 and so on

For a complete list of Legacy servers refer the following link.

^*Selected Dell’s 11th generation PowerEdge Servers: R710, R610, R415, R515, R715, R815, M915, M910, T110 II and FM120

Fixes & Enhancement:

OMSA v7.4.0.2

•  

  Windows

• Windows2012 "No Instance(s) Available" is reported for Dell_CMApplication class data
• Wmiprvse.exe is crashing on Windows 2012 when accessing OMSAx64 7.x dccim64 CIM_DiscreteSensor
• OMSA 7.4 x86 MST.SYS service could not start with critical syslog error in Windows event log
• OMSA 7.4 dsm_sa_datamgr64 exception with 3rd party Sentinel HASP USB dongle/drivers

VMware

• • • OMSA7.4 not reflecting storage status change in ESXi 5.1 U2 – H200 controllers
    • Various SFCB-DCIM memory leaks

OS Independent

• • • R220_EST:Data Manager crashes while creating RAID 50 virtual disk via OMSA
    • Storage status changes (Ex: hard drive insertion/removal, virtual disk degradation, virtual disk rebuild progress) are not reflected in OMSA when SAS 6iR Integrated (Embedded) or PERC H200E (Embedded) are used.
    • OME 1.21 Broadcom firmware update reports failed in OM Essentials, but is actually successful
    • When a M820 system is migrated from M1000e to VRTX chassis, OMSA data manager crashes.

OMSA 8.0.1.1

• • • Tape Device is not getting reported in Windows  with OMSA  version 7.4.1. +
    • The PCIe devices are not seen in OMSA. (PCIe SSDs or controller )
    • VD, Fan, EMM, Battery, Power Supplies and Temperatures information are not showing on MIB
    • OMSA session logs out when trying to import secure VD by providing suggested passphrase

Downloads:

OpenManage™ Integration Suite for Microsoft® System Center  can help you proactively deploy, manage, monitor and optimize IT resources in both physical and virtual environments. System Center products capture and aggregate knowledge about your infrastructure, policies, processes and best practices, enabling you to automate IT operations and improve application availability and service delivery.

For more details visit - Dell OpenManage Integration Suite for Microsoft System Center

Dell OpenManage Connections are designed specifically for monitoring Dell hardware within infrastructures managed by HP Operations Manager, IBM Tivoli Netcool/OMNIbus, IBM Tivoli Network Manager (ITNM) IP Edition, Oracle Enterprise Manager, Nagios Core, Nagios XI, or CA Network and Systems Management (NSM) solutions.

For more details visit - Dell OpenManage Connections for Partner Consoles

Note: Dell_OpenManage_Plugin_v1.0_Nagios_Core_A00.tar.gz package is supported on RHEL and SLES operating systems as mentioned in the Systems Requirements section in product Installation Guide. The same package may work with other Linux variants but the offering is not covered by Dell support.

The Plug-in is community supported for CentOS and Ubuntu platforms. For CentOS and Ubuntu related queries, use: http://en.community.dell.com/techcenter/systems-management/f/4671/t/19470091

Contents: Download - Documentation - Whitepapers - Videos - Forum - Blogs - FAQ 

OpenManage Essentials (OME) is a systems management console that provides simple, basic Dell hardware management and is available as a free download.

The latest release is OME 2.0 and it launched on September 8, 2014.  It brings a lot of great new features to the product.

OpenManage Essentials is an easy to install, intuitive and simple to use, systems management console solution optimized for monitoring and managing Dell enterprise and remote office/business office-class hardware.  New features available with OpenManage Essentials v2.0 include 13th generation server support, enhancements in server discovery and agent-free update operations for legacy PowerEdge servers, and for 12G/13G servers, processes that enable automated bare-metal server and OS deployments and rapid detection of server configuration drift in production environments.     

Key benefits of Dell OpenManage Essentials v2.0: 

• Comprehensive monitoring and control of Dell servers, storage, networking, business client hardware, firewall appliances, and supported 3^rd party hardware, through a single systems management console 
• Automation of basic management tasks that deliver increased productivity, fewer errors, continuity in processes, consistency in configurations, and operational cost savings     
• Automated, agent-free implementations that enable uniform discovery, inventory, monitoring and update operations for Dell PowerEdge servers in physical  and virtual, multi-vendor operating system and hypervisor environments
• Faster time from inactivity to productivity and value with automated PowerEdge bare-metal server and OS deployments (more details at this link)
• Improved availability through rapid detection and resolution of issues related to server configuration drift from customer-defined baselines   

Key new features available with Dell OpenManage Essentials v2.0: 

• Support for the new 13^th generation PowerEdge servers
• Guided discovery wizard that simplifies and speeds server discovery and setup operations
• Deployment and update of iDRAC Service Modules (ISM)
• Removal of OpenManage Server Administrator (OMSA) dependencies when updating pre-11^th generation PowerEdge servers and windows drivers
• Enhanced scalability to support 4,000 devices and 40,000 alerts in the console
• Launch the virtual console of an IDRAC configured for Single Sign-On (SSO)
• Additional inventory and reporting data
• Displayof Warranty pop-up notification for devices
• Deploy 64-bit Dell Update Packages (DUPs)
• Server Configuration Management - available as a fee-based license for use with 12G/13G iDRAC Enterprise or iDRAC Express 
  

• Template-based server/chassis configuration and OS deployment for bare-metal 12G/13G PowerEdge servers
• Automated detection and notification of PowerEdge server(s)/chassis’ drift from a customer-defined  baseline configuration during server operation
• Boot a system from a network-mounted ISO using iDRAC
• Licenses are available at server point of sale (POS) as well as after point of sale (APOS)   
• Feature/functionality is activated by entering the Server Configuration Management license key on iDRAC Enterprise or iDRAC Express

Existing OpenManage Essentials features also available now in OME v2.0:

• Anytime, anywhere mobile access to data center health status information with OpenManage Mobile
• Integration with Dell ProSupport SupportAssistforproactive remote support, automated support case creation and hardware failure notification sent securely to Dell technical support for intelligent issue analysis, diagnosis, and part-replacements upon customer request
• Comprehensive, deep management visibility and control for Dell blades and Chassis Management Controller (CMC), Dell storage and networking devices, and Dell AppAssurethrough a context sensitive link and launch of the respective element management interface
• Geographic View at-a-glance visibility of VRTX systems’ physical locations geographically mapped
• Agent-free OOB inventory and update of Dell 11G and 12G PowerEdge servers
• Agent-free monitoring of Dell PowerEdge 12G servers
• Traditional agent-based systems management functionality in all supported 9-12G servers
• Management of Dell PowerEdge C platforms with IPMI
• Monitoring of non-Dell HW devices through import of 3^rd party HW SNMP MIBs
• Reporting of Warranty expiration and comprehensive inventory reports
• Hardware component-level monitoring and updates for Dell PowerEdge servers, blade systems and internal storage arrays
• Support and control of Dell hardware in Windows, Linux, VMware, Hyper-V and OpenSource  environments
• Enhanced management functionality through integration with the following Dell solutions :

• Dell KACE K1000 Appliance– comprehensive, economical and straightforward management of both clients and servers through a single interface
• Dell Repository Manager– version control and scheduling of PowerEdge server updates 
• Dell OpenManage Power Center– optimization of  PowerEdge power usage

Dell OpenManage Essentials Core Features:

OpenManage Essentials is available as a free download from the Dell Support Site. The OME console's inventory function integrates with the Dell Repository Manager to automatically facilitate the creation of custom repositories of new updates for your systems.  

If you are new to the product, Take the Quick Tour or watch the OME Overview Video below:

Download  

• Download OpenManage Essentials 2.0.1
• • previous versions available in the Archive section
• Dell Troubleshooting Tool for OME v2.0.1
• Dell MIB Import Tool for OME v2.0
• Download the Dell SNMP Configuration Tool

Discuss

• OpenManage Essentials Discussion Forum 

• OpenManage Essentials Blog Posts 

Learn

• OpenManage Essentials 2.0.1 Documentation - (Release Notes, Manuals, Support Matrix, User's Guide, Whitepapers)
• OpenManage Essentials 2.0 Documentation - (Release Notes, Manuals, Support Matrix, User's Guide, Whitepapers)

• OME Frequently Asked Questions (FAQ) 
• OME Tips and Tricks
• OME vs Dell IT Assistant
• OME Quick Tour
• Tutorial videos as the bottom of this page
• Service Offering: Remote Installation and Configuration of OME

Whitepapers and Best Practices

Video 1: Adding Devices to the Bare Metal and Re-purpose Device Group

 (Please visit the site to view this video)

Video 2: Configuring Credentials and Scheduling Inventory

 (Please visit the site to view this video)

Video 3: Configuring a Deployment Share

 (Please visit the site to view this video)

Video 4: Creating a Configuration Template

 (Please visit the site to view this video)

Video 5: Deploying a Bare Metal Device

 (Please visit the site to view this video)

Video 6: Detecting Configuration Drift

 (Please visit the site to view this video)

Video 7: Auto Deploying Bare Metal Devices

0:08 - Installing OpenManage Essentals 
0:56 - Discovery and Inventory 
2:03 - Monitoring Health of Devices 
2:43 - Using the Home Portal
5:58 - Deploying Updates
7:03 - KACE Integration + MonitoringOpenManage 

Client device support using SNMP/WMI

	OpenManage Essentials and Repository Manager Integration
	Enable SNMP on OpenManage Server Administrator for ESXi4
	Enable SNMP on OpenManage Server Administrator for Windows
	Enable SNMP on OpenManage Server Administrator for Linux (RHEL)
	Dell OpenManage Essentials with KACE Integration
	OpenManage Essentials Custom Alerts
	OpenManage Essentials Apply System Updates
	Installing Dell OpenManage Essentials
	OpenManage Essentials Discovery and Inventory
	Dell OpenManage Essentials Discovery

Summary

This page contains all white papers for both Lifecycle controller (LC) and iDRAC.

Introducing iDRAC8 with Lifecycle Controller for Dell 13th Generation PowerEdge Servers (new for 13G)

PowerEdge Software Licensing (new for 13G)

Deploy

Understanding PreBoot Networking on Dell PowerEdge Servers (new for 13G)

IPv6 Best Practices using iDRAC (new for 13G)

Dell Network Adapters with iDRAC (new for 13G)

Using Lifecycle Controller to Configure UEFI Secure Boot and OS Deployment (new for 13G)

Managing Backplane Split Mode (new for 13G)

Defining a Secure Boot Policy (new for 13G)

Optimizing I/O Identity and Applying Persistence Policy on Network and Fibre Channel Adapters (new for 13G)

BIOS Setup User Guide for 13th Generation PowerEdge Servers(new for 13G)

BIOS POST Troubleshooting Guide for 13th Generation PowerEdge Servers(new for 13G)

Unattended Installation of Red Hat Enterprise Linux 7 Operating System on Dell PowerEdge Servers Using iDRAC With Lifecycle Controller(new for 13G)

Unattended Installation of Windows 2012 (12G and 13G)

AutoConfig - Enabling rapid configuration of Dell servers using DHCP(12G and 13G)

Server Cloning with Server Configuration Profiles

Creating and Managing Server Configuration Profiles

Scripting WSMAN to Deploy OS Drivers

Scripting WSMAN to Deploy OS using Remote ISO Image to Stage and Boot

Scripting WSMAN to Deploy OS using vFlash to Stage and Boot to ISO

Operating System Deployment in PowerEdge Servers

Operating Systems Deployment using iSCSI or FCOE LUN

Auto Dedicated NIC Feature in iDRAC7

Auto-Discovery Network Setup Specification

Configuring BIOS and NIC Using RACADM through Dell iDRAC

FCoE Boot Configuration Setup on Intel Card

FCoE boot using Broadcom card

iDRAC Cloning

Reinitiate Auto-Discovery

Remote NIC Configuration Management 

Update

Updating BIOS on Dell 13G PowerEdge Servers (iDRAC8 - 13G only) (New for 13G)

Updating BIOS on Dell 12G PowerEdge Servers (iDRAC7 - 12G only) 

PowerEdge Updates with Repository Manager Best Practices Guide

Auto Backup and Auto Update using iDRAC

Lifecycle Controller Platform Update in Dell PowerEdge 12th Generation Servers

Remote Firmware Update

Recommended Workflow for Performing Firmware Updates on PowerEdge Servers

Monitor

Express Flash NVMe PCIe SSD Devie Monitoring, Inventory, and Configuration (New for 13G)

Using OpenManage Essentials to configure iDRAC7 Action Alerts

Agent-free Inventory and Monitoring for Storage and Network Devices

Updating Firmware on PowerEdge Servers Using the iDRAC7 Web Interface

Web Service Eventing for iDRAC7 1.30.30 or later versions

Converged Network Adapters with NIC, iSCSI, and FCoE Support

Gathering information from iDRAC7 using SNMPv3

iDRAC7 Network and Virtual Media Performance

iDRAC7 Networking and Improved Remote Access Performance

OMSA / OMSS to iDRAC7 SNMP-Gets Migration Guide

Maintain

Managing Web Server Certificates on iDRAC (New for 13G)

Integrate iDRAC8 with Active Directory (New for 13G)

System Erase in Dell 13th Generation PowerEdge Servers (New for 13G)

Methods to Save and Restore PowerEdge Server Configuration Settings and Firmware Images (New for 13G)

Generating Tech Support Report on 13th Generation Dell PowerEdge Servers (New for 13G)

Motherboard Replacement

Dell’s vFlash SD Flash Media Card – Better Endurance and Performance via Over-Provisioning

Configuring Low-Latency Environments in PowerEdge Servers

Dell iDRAC7 Licensing Whitepaper - Differences between iDRAC6 and iDRAC7

Discovering Features in the iDRAC Remote Services API

Hardware Inventory Viewing Script

How to Build Inventory Reports 

Import and Export Server Profiles

Lifecycle Controller Backup and Restore in Dell PowerEdge 12th Generation Servers

Automatic Backup Server Profile

Lifecycle Controller Part Replacement

Lifecycle Controller Workflow Optimization

Part Replacement

Network IO Identity

Restoring iDRAC7 License after System Board Replacement

General

iDRAC 7 & 8 Feature and Licensing Information Sheet (New for 13G)

FAQ: iDRAC Quick Sync & OpenManage Mobile - October 2014 (New for 13G)

iDRAC QuickSync Technical Guide- Nov. 2014

Principled Technologies' Review of 13G PowerEdge OpenManage(New for 13G)

Understanding Physical Computer System View Profile Implementation (New for 13G)

iDRAC7 with Lifecycle Controller - Feature Guide

New Feature Overview: December 2013 Releases of iDRAC7 and Lifecycle Controller 2

New Features and Usability Enhancements to RACADM Commands in iDRAC7

New Security Features in Integrated Dell Remote Access Controller 7

Active Directory using Lifecycle Controller 

Integrating iDRAC 7 with Microsoft Active Directory

Pre-failure alerts provided by Dell server systems management

Understanding the iDRAC Power State Management in Base Server Profile

Understanding the iDRAC Power State Management Profile

Using the iDRAC7 Video Capture Feature

vFlash Overview

vFlash Partition Management 

vFlash using the Lifecycle Controller GUI

Scripting - General

Using Filter Dialects with the WSMAN API (New for 13G)

Creating Applications using the WSMAN API (New for 13G)

Programmatic Scripting with WSMAN

Using Microsoft Windows PowerShell CIM Cmdlets with Dell iDRAC

Server Configuration Profile - XML File Structure (files )

What is the OpenManage Integration for VMware vCenter?

The OpenManage Integration for VMware vCenter (OMIVV) is designed to streamline the management processes in your data center environment by allowing you to use VMware vCenter to manage your entire server infrastructure - both physical and virtual. From monitoring system level information, bubbling up system alerts for action in vCenter, rolling out firmware updates to an ESXi cluster, to bare metal deployment, the OpenManage Integration will expand and enrich your data center management experience with Dell PowerEdge servers.

OpenManage Integration for VMware vCenter - Value proposition

 (Please visit the site to view this video)

Getting started

To download a free 5 host, 90 day evaluation appliance for version 2.3, please click here.  The following video steps through the installation process:

(Please visit the site to view this video)

What's new?

January 22, 2015 - v2.3 Release

• Support for the 13G server releases (R530, R430, FC630, M630, T430)
• Support for CMC monitoring and alerting with the new CMC firmware (M1000e = v5.0, VRTX = v2.0, FX2 = v1.1)

 

OMIVV Features

OMIVV Manuals

1.0.1
1.5
1.5.1
1.6
1.7
2.0
2.1
2.2
New! 2.3

Additional Videos

Features Overview

Chassis integration setup

Chassis information deep dive

Whitepapers

Other Resources

OpenManage Integration for VMware vCenter on Dell.com

Dell KACE™ Systems Management Appliances

Systems Management - Wiki

The Dell KACE Family of Systems Management Appliances

Dell KACE provides a comprehensive approach to systems management that allows Systems Administrators to save time while saving money for their companies. The Dell KACE Family of Systems Management Appliances are easy-to-use, comprehensive and affordable and they fulfill the systems management needs of organizations of all sizes, from initial computer deployment to ongoing management and retirement.



The KACE Advantage

Available in three different deployment options from on premise physical or virtual solutions or as a hosted, cloud service via K1000 as a Service*, the Dell KACE appliances make efficient computer, device and server management a reality. They provide a low cost alternative to computer management software by using a pre-integrated and pre-configured appliance-based architecture. Simply connect the appliance to the network, give it an IP address and you are ready to begin managing all your desktops, laptops, network connected devices and servers. Unlike traditional computer management software, Dell KACE appliances typically deploy in only one day. And because Dell KACE appliances are fully integrated and pre-configured, there are no hardware or software pre-requisites, no incremental professional service fees and no hidden costs. It's all in the appliance.

For complete product information, go to http://www.kace.com/products/overview/  

* K1000 as a Service may not be available in all regions, please check with your local sales representative for availability.

Dell KACE Links

White Papers

Dell KACE K1000 Series Management Appliance ArchitectureInternal design and network configuration specifics of the K1000 Management Appliance

Dell KACE K2000 Series Deployment Appliances ArchitectureInternal design and network configuration specifics of the K2000 Deployment Appliance

Five Steps for Easier- and More Effective- IT InventoryingUnderstand how to improve the process and the results of effective IT inventory  

Nine Simple (but Critical) Tips for Effective Patch ManagementPatching has never been more important, so understand how to make it manageable and effective 

Solving systems management challenges for K-12Discover why KACE appliances are so well suited to challenges faced in elementary education 

Six Ways to Extend and Expand Your Systems Management Capabilities to Your User EnvironmentLearn how to better secure and control user environments while maintaining worker productivity 

Five Easy Steps to Smarter Systems ImagingCreating and maintaining system images can be a daunting task; learn how to work smarter to get the job done 

Dell KACE K1000 Management Appliance: Best Practices for a Secure DeploymentUnderstand best practices for deploying the K1000 in a secure environment   

Migrating from Windows XPLearn tips and tricks for getting to a new OS environment quickly and painlessly  

By the Numbers: Lowering Energy Costs at the DesktopUnderstand how power management can save real dollars for organizations of all sizes

Recent Dell KACE Content on Dell TechCenter

Dell KACE Chats:
01-25-11: Dell Client and Systems Management Futures
02-22-11: KACE Chat

Blog Posts:
01-25-11: Dell KACE K1000 Announcement and the Dell TechCenter Dell KACE page

Suggested Dell KACE Webinars

Software License Audit: Beat it and Breeze it!

6/26/2014  

Overcome Inefficient IT Asset Management

5/29/2014

Solving Systems Management Challenges for Educational Institutions

5/23/2014

 RIP Windows XP Support

4/17/2014  

IT Security Risks from Inefficient IT Asset Management (ITAM)

3/27/2014  

Enterprise Mobility Management from Dell: Secure, Sane and Simple Mobile Device Management

2/27/2014  

Smarter and Faster Large-scale Systems Imaging

1/23/2014  

Simple, Effective Patch Management: From Dilemma to Done Deed

11/13/2013

Analyst Reports and Surveys

Rethinking IT Asset Management in the Age of the "Internet of Things"

5/13/2014 

Securing the Internet of Things: A Survey of IT Professionals

5/13/2014     

Dell KACE K2000 Systems Deployment Appliance vs. Symantec Ghost - Choosing an Enterprise Deployment Solution

4/14/2014  

Vendor Landscape: IT Asset Management Mid-Market

11/22/2013  

Best Practices in Lifecycle Management: Comparing Suites from Dell, LANDesk, Microsoft, and Symantec

9/20/2013

IT environments are becoming increasingly more diverse and complex, and consequently harder to manage. Mobility, along with more and more “smart” devices (i.e. the Internet of Things) has led to a significant increase in the number and types of devices that are connected to corporate networks, devices that you must now track, manage and secure. The scope of the problem becomes even larger when you also consider the number of different platforms that need to be managed – these include Windows, Windows Server, Mac OS X, Linux, UNIX, Chromebook, iOS and Android. Issues and concerns may include: 

• Lack of visibility over all of the devices accessing the corporate network, which results in security and compliance concerns, and can lead to increased downtime for key systems, devices and applications. This can reduce productivity and result in frustrated end users.
• Having to use multiple tools to manage a heterogeneous environment consumes budget and human resources, introduces complexity in managing the business, and can lead to console fatigue.
• Adoption of non-Windows-systems – such as Chromebooks or Linux devices – becomes an entirely new challenge, especially due to the lack of integration of these platforms with a primary systems management solution for such key functions as asset lifecycle management and service desk.

All of these factors are driving the imperative for you to make anypoint systems management a higher priority. If your organization previously felt that it could ‘get along’ without a comprehensive systems management strategy, you are likely now feeling the pressure to find a comprehensive “anypoint” systems management solution, one that is both easy to use and addresses all of your concerns.

The Dell KACE K1000 Systems Management Appliance (K1000) provides you with that solution. The K1000 provides comprehensive systems management for computers and servers, including discovery, inventory and asset management, software distribution, patch management, policy enforcement and service desk. And the latest release of the K1000 (available in March 2015) strengthens the focus on anypoint systems management and delivers greater visibility across your entire IT environment. New and enhanced functionality expands the types of devices managed by the K1000 to Chromebooks, Windows servers and network connected non-computer devices. We have also made improvements to the usability of a number of K1000 components. With this release, the K1000:

• Becomes the first systems management solution to inventory Chromebooks– the information is integrated into K1000’s asset management, reporting, alerting and service desk workflows to provide comprehensive asset lifecycle management for Chromebooks
• Expands its server management capabilities by introducing log, threshold and application monitoring for servers
• Extends its agentless inventory capabilities to Windows servers and PCs to allay any concerns over agent-related performance issues on mission critical servers
• Enables you to gather actionable data from connected non-computer devices – printers, projectors, power back-up devices – and integrates that data with K1000’s reporting, alert and service desk workflows to enable pro-active device maintenance
• Delivers simplified deployment and ease of use through a redesigned interface and enhanced functionality for patch management, service desk agent deployment and software asset management

You can find out more about the latest enhancements to the K1000 by attending a live demo or by visiting www.kace.com or http://software.dell.com/products/kace-k1000-systems-management-appliance/.

Contents: Download - Documentation - Whitepapers - Videos - Resources

Dell OpenManage Server Administrator (OMSA) is a software agent that provides a comprehensive, one-to-one systems management solution in two ways: from an integrated, Web browser-based graphical user interface (GUI) and from a command line interface (CLI) through the operating system. 

OMSA is designed so that system administrators can manage server systems both locally and remotely on a network. It also interfaces with OpenManage Essentials (OME) console, which allows for monitoring of the systems in your data center from a single interface.

Currently the OMSA agent can be installed on 32 and 64 bit versions of Windows Server and Red Hat Linux as well as Novell SUSE Linux.

[New] For a quick tour of OpenManage Server Administrator's releases during 2014.Please click here.

[2 December 2014] Latest release v8.0.2 is available now. To download them,refer Download OM 8.0.2:

NOTE: Server Administrator version 8.0.2 is supported only on the following systems:

•  PowerEdge R430
•  PowerEdge R530
•  PowerEdge T430
•  PowerEdge M630
•  PowerEdge FC630
•  PowerEdge C4130

• Installation: Added support for the following operating systems

• Red Hat Enterprise Linux 7
• VMware ESXi 5.5 U2 and 5.1 U2
• Citrix XenServer 6.2 SP1

• Added support for the following cards
  • Paradise Key Intel bNDC (4x1Gb)
  • Broadcom Gamma bNDC (4x1Gb)

   

• Added support for the following other hardware

• Intel 16/18 core CPU
• High Capacity DIMM 32 MB and 64 MB

• Added support for PowerEdge RAID Controller (PERC) H730P Slim.

• This release provides fix for SSLv3 Poodle vulnerability. As part of this fix, OMSA will not allow SSLv3 connections.

[17 September 2014] Latest release v8.0.1 is available now and it brings lots of new enhancements:

NOTE: Server Administrator version 8.0.1 is supported only on the following systems:

•  PowerEdge R730
•  PowerEdge R730 XD
•  PowerEdge R630
•  PowerEdge T630

• Installation: Added support for the following operating systems.
  • Red Hat Enterprise Linux 7.0
  • VMware ESXi 5.5 U2 and 5.1 U2
  • Citrix XenServer 6.2 SP1

• Web/UI Enhancements:

  • Added support for additional attributes and values in BIOS setup groups.

• Browser Support:

  • Google Chrome 27,28 and 30.
  • Safari 6.0

• Network Interface Cards (NICs) Supports:

  • Broadcom 5720 1Gb  bNDC
  • Intel 1350 1Gb bNDC
  • Intel X710 10 Gb rNDC
  • Emulex OCm14104-UX-D 10Gb rNDC
  • Emulex OCm14102-U2-D 10Gb bNDC
  • Emulex OCm14102-U3-D 10Gb Mezz
  • Emulex OCe14102-UX-D 10Gb PCIe

• Storage Management:

• • Support enabled for MD1400 and MD1420 enclosures.
  • Support for S130 SWRAID
  • Support for  PERC 9 cards:
    • H730
    • H730P
    • H830
    • H330
  • Support for 12gbps SAS HBA
  • Support for controller mode enumeration (RAID and HBA)

• Deprecated support for SNMP set feature.

Dell OpenManage

Dell OpenManage is a set of systems management applications built using industry standard protocols and specifications. Dell OpenManage is not a product within itself, but rather a brand name for the suite of products in the portfolio. Server Administrator (OMSA) is part of OpenManage family.

You can refer various system management manuals to learn more about the Dell products.

Manuals:

• Various OpenManage
• Various Server Administrator

Dell OpenManage v8.0.1 Documentation

• Documentation (Events,  Management Tools, Release Notes etc.)

 Dell OpenManage v8.0.2 Documentation

• Documentation (Events,  Management Tools, Release Notes etc.)

For more details on previously released Server Administrator and other OpenManage products, refer the OpenManage manuals.

• Download OpenManage MIBs for Management Consoles

Server Administrator v8.0.1 Documentation

Refer all the below documents from the Server Administrator Manuals page.

• Server Administrator Storage Management Guide
• Server Administrator CIM Reference Guide.
• Server Administrator SNMP Reference Guide.
• Server Administrator CLI (Command Line Interface) Guide.
• Server Administrator User's Guide
• Server Administrator Readme
• Server Administrator Release Notes
• Server Administrator Installation Guide
• Storage Management User's Guide

Server Administrator v8.0.2 Documentation

Refer all the below documents from the Server Administrator Manuals page.

• Server Administrator Storage Management Guide
• Server Administrator CIM Reference Guide.
• Server Administrator SNMP Reference Guide.
• Server Administrator CLI (Command Line Interface) Guide.
• Server Administrator User's Guide
• Server Administrator Readme
• Server Administrator Release Notes
• Server Administrator Installation Guide
• Storage Management User's Guide

Download

OMSA v8.0.1 Download

OMSA v8.0.1 can be downloaded from the following links. Please refer Server Administrator Installation Guide and Support Matrix to install these packages on the supported operating system.

Resources

Dell Repository Manager Overview
(Please visit the site to view this video)

DRM Terms and Concepts

 (Please visit the site to view this video)

Configuring Advanced Settings

(Please visit the site to view this video) 

Configuring Email Settings

(Please visit the site to view this video)

Manual Repository Creation

 (Please visit the site to view this video)

Automate Repository Creation with iDRAC

(Please visit the site to view this video)

Configuring New Catalog Notification Settings 

(Please visit the site to view this video)

Automate Repository Creation with M1000e

(Please visit the site to view this video)

Automate Repository Creation with VRTX

(Please visit the site to view this video)

Schedule Repository Search for new Updates

(Please visit the site to view this video)

New Catalog Notification

(Please visit the site to view this video)

Create a Deployment Tool Overview

(Please visit the site to view this video)

Create a Server Update Utility

(Please visit the site to view this video)

Create a Bootable ISO

(Please visit the site to view this video)

Create a Lightweight Deployment Script

(Please visit the site to view this video)

Save a Repository Catalog and Files to a location

(Please visit the site to view this video)

Search Dell Support Site

(Please visit the site to view this video)

Configuring FileStore Settings
(Please visit the site to view this video)

Creating Bootable ISO - step by step guide to create a Bootable ISO using Dell Repository Manager
(Please visit the site to view this video)

Adding a DUP - Step by step process of adding a DUP from support.dell.com into a repository that has been created using Dell Repository Manager.
(Please visit the site to view this video)

Comparing Repositories for Updates -Step by step demonstration of comparing an existing repository with what is currently available from Dell.
(Please visit the site to view this video)

Using Dell Repository Manager to create a customized Server Update Utility that has just the systems and updates you want to deploy.
(Please visit the site to view this video)

Using the Search Dell Support Site feature to find updates for Dell EqualLogic devices.
(Please visit the site to view this video)

Using the Search Dell Support Site Feature to find updates for older Dell PowerEdge Servers.
(Please visit the site to view this video)

Finding Dell PowerEdge update that are newer then what is in the catalog
(Please visit the site to view this video)

Finding PowerEdge C Updates - Using the Search Dell Support Site feature to find updates for Dell PowerEdge C Servers.
(Please visit the site to view this video)

Using the Search Dell Support Site feature to find updates for Dell PowerConnect devices.
(Please visit the site to view this video)

Using the Search Dell Support Site feature to find update for Dell PowerVault devices.
(Please visit the site to view this video)

Using the Schedule Automatic Search feature to automate finding new updates.
(Please visit the site to view this video)

Creating a Scripted Deployment Pack - Using Dell Repository Manager to create a tool to push updates using scripts.
(Please visit the site to view this video)

Overview of using Repository Manager’s Search Dell Support Site feature.
(Please visit the site to view this video)

Setting up Dell Repository Manager to run behind a Proxy Server
(Please visit the site to view this video)

Using Dell Repository Manager with Dell Management Plug in for VMware vCenter
(Please visit the site to view this video)

Using Dell Repository Manager with Dell OpenManage Essentials
(Please visit the site to view this video)

Dell Repository Manager Overview Demonstration ( full transcript )

(Please visit the site to view this video)

USB Updates Using Dell Repository Manager with Lifecycle Controller

(Please visit the site to view this video)

To learn more about USB updates using Repository Manager and LifeCycle Controller, please visit:
http://www.delltechcenter.com/page/Updates+using+USB+with+Lifecycle+Controller

Dell Repository Manager Integration with OpenManage Essentials

(Please visit the site to view this video)

Updating the Repository in Dell Repository Manager

(Please visit the site to view this video)

Adding a DUP to Repository Manager v2

(Please visit the site to view this video)

Creating a Bootable ISO

(Please visit the site to view this video)

Setting the Proxy Server

(Please visit the site to view this video)

Dell Repository Manager - Build Custom SUU (Server Update Utility)

(Please visit the site to view this video)

Dell Repository Manager - Deploy Scripted Updates

(Please visit the site to view this video)

Using Dell Repository Manager to Apply Updates on VMware ESX 4

(Please visit the site to view this video)

Automated Hardware Updates using Dell Repository Manager and the Remote File Share Feature of the M1000e Blade Chassis
- Details on the customization used in this demo.

(Please visit the site to view this video)

Quick Links:

(Please visit the site to view this video)

CMC 4.4 (released June 2013) Overview

What is the M1000e?

The M1000e is Dell’s foundation for a blade server solution. It provides the infrastructure (industry-leading power & cooling, networking and blade manageability) for companies who choose to deploy blade-based server solutions. Its components include:

• The Dell Chassis Management Controller (CMC) is a systems management hardware and software solution for managing multiple Dell blade chassis.
• PowerEdge servers- M420, M520, M620, M820, M610, M610X, M710, M710HD, M905 and M910 Blade Servers.
• Blades Manageability Options- CMC, iDRAC, Dell AIM, Dell OpenManage Integration Suite for Microsoft System Center, and Dell OpenManage Integration for VMware vCenter.
• Integrated Networking

What's New

( top )

( top )

  ( top )

OpenManage Mobile Overview

Dell OpenManage Mobile is a software application that enables one to securely perform a subset of datacenter monitoring and server remediation tasks from a mobile device.

OMM is supported for Android and iOS mobile devices.

OpenManage Mobile can connect to your datacenter through the Dell OpenManage Essentials management console. This allows a user to monitor all systems managed by OpenManage Essentials such as Dell Servers, Storage, Networking, and Firewall appliances and any other supported third party appliance from your android mobile device.

OpenManage Mobile can also connect to a Dell PowerEdge server directly through the iDRAC interface. Once connected, a user can perform several basic management functions on the server. OpenManage Mobile can connect to a server in two possible ways:
1) Remotely using Wi-Fi or broadband network from anywhere.
2) Physically at the data center using Near Field Communications (NFC) technology. This requires a Dell 13G PowerEdge server equipped with an iDRAC Quick Sync Bezel. This connectivity is supported only on Android Mobile devices. iOS platform does not support NFC capabilities yet.

Key benefits:

• Flexible schedule for system administrators: Monitor your data center systems from anywhere at anytime
• Increase business productivity: Reduce response time on critical alerts by taking server remediation actions from your phone

Key Features

• Connect to multiple OME servers from a single mobile device. Supports OpenManage Essentials 1.3 and 2.0.
• Connect to multiple 12G and 13G servers individually through the iDRAC web interface.
• Connect to multiple 13G servers through the iDRAC Quick Sync interface (Android only).
• Forward server details, health status, network info, firmware info, and log entries from iDRAC via email using compatible email clients.
• Establish connection with individual 12G & 13G server OS desktops remotely using Virtual Network Computing (VNC). 
• Receive critical alert notification on your mobile device as they arrive into your OpenManage Essentials management console.
• Acknowledge, forward and delete alerts from your mobile device.
• Browse device details, health status, firmware inventory, and event logs of individual systems.
• Perform server management functions such as Power On, Power cycle, Reboot, or Shutdown from the mobile application.
• Email Reporting - Forward server details, health status, network info, firmware info, and log entries from iDRAC via email using compatible email clients.

FAQ: iDRAC Quick Sync & OpenManage Mobile - October 2014

Minimum Requirements 

• Mobile device running: 1)Android OS v 4.0.3 or higher 2) iOS mobile devices running 7.0 or higher
• OME v1.3 or OME v2.0 management console (for data center monitoring features)
• 12G & 13G servers (for 1:1 connection through IDRAC)
• 13G servers (R630, R730, R730 XD) and the iDRAC Quick Sync Bezel (for at-the-box features)

Videos

Value proposition video for iDRAC with Quick Sync enabled by OMM v 1.1

(Please visit the site to view this video)

Video showing iDRAC Quick Sync features with OMM 

(Please visit the site to view this video)

Video explaining the value proposition of the application –

(Please visit the site to view this video)

A video explaining the 4 key steps involved in using the application -

(Please visit the site to view this video)

Download -

https://play.google.com/store/apps/details?id=com.dell.omm

Documents -   

OpenManage Mobile v1.2 User Guide (for Android) 

OpenManage Mobile v1.0 User Guide (for iOS)

OpenManage Mobile Best Practices White Paper

iDRAC QuickSync Technical Guide - Nov. 2014

OpenManage Mobile TIP of the day

12/02/2014 - iDRAC Quick Sync

Certain Android handsets do not autonegotiate well at all NFC speeds. This might be an Android OS bug or a bug in the chipset silicon of the handset. So far we have not managed to isolate any vendor or Android OS version that  has this problem. It happens to be random across manufacturers, but consistent to a handset model.

Of the supported 106, 212, and 424 kbps for Quick Sync, only 106 kbps works effectively.

If you have a a device that has the above-mentioned problem during Quick Sync, then you are advised to launch the “Add via Quick Sync” animation within the OMM app before you perform an Quick Sync Scan, in order to have a successful scan.

For the devices that  do not have this problem, you can be in any state of using the app (even minimized) and the app is launched when you attempt to do a Quick Sync read.

03/18/2014 - Push Notifications

Question – I am able to connect to my OME through 3G/4G connections and get notifications. When I am not connected to my OME server I still keep receiving notifications from the devices I am monitoring. Why is this happening? How can I stop this?

Answer – When a user adds an OME to the OMM app on the phone, he/she chooses a filter for “push notifications”. This is the second screen of the “Add OME” wizard. Whenever OME receives an alert that matches the filter chosen by the user it sends an alert update via the end users phone network to the mobile device. If “All Alerts” was chosen, the user will receive all alerts that are received by OME. Ideally an administrator should set the filter to only those alerts that are critical and are of interest to avoid alert overload.

The alerts will get pushed to your mobile phone even when you are no longer connected to the OME, and away from your company network. These messages are not warnings about lack of connection to OME. As an OME administrator, you would want to receive these alerts even when not connected to the OME (for example when you are offsite or it is after work hours), since they usually indicate problems in your data center. After receiving one or more alerts log onto OMM, connect to the OME, and then view more details on the alerts. After browsing through the alert details take action on the alert, without having to physically access the OME or the targets managed by OME. If you don’t log onto OMM, the alerts will accumulate as they are still marked “unread.”

If you don’t want to receive alerts when not connected to the OME this feature can be turned off. There are several ways to do this.

1)      Log onto OMM, edit the OME’s connection and change your filter settings to “None” or to the filter you are most interested in. You have to be connected to the OME to make this change. A user can always re-subscribe to the right filter as his roles and responsibilities changes over time.

2)      Log onto OME via a web browser, and in the “Preference” section you will see your phone listed in the “Mobile Settings” page. You can choose to delete or disable your device from that list. 

OpenManage Mobile Forum -

Have a question or feedback on OMM. Start a discussion here.

Others –

OpenManage open source license document

Why do I want to use this tool?

OpenManage Essentials provides support for formatting hardware alerts (i.e., SNMP traps) for most Dell enterprise hardware. If you want to monitor non-Dell devices, you can use the OpenManage Essentials MIB Import Utility to define new alerts for OpenManage Essentials. Defining alerts enables OpenManage Essentials to monitor a wider range of hardware and to set up email and forwarding rules for these devices.  The MIB Import Utility is an optional tool that is only required if you want to add support for formatting alerts received from third-party devices.

The details:

Dell OpenManage Essentials MIB Import Utility enables you to extract trap definitions from SMIv1 or SMIv2 management information base (MIB) files. The extracted traps can be viewed and edited before importing them to OpenManage Essentials. This tool also enables you to manually define and manage traps. Using the imported and manually-managed trap definitions, OpenManage Essentials classifies the incoming trap from a specific device as expected.

If you want to monitor (classify incoming SNMP traps) a SNMP supported device that is not currently supported by OpenManage Essentials, use MIB Import Utility to import or manually define that device’s SNMP trap definitions for OpenManage Essentials.

Please review the readme file after you install this tool.  The readme also provides a list of some of
the MIBs that have been tested using this tool. Feel free to post updates on the DTC/OME forum including MIBs that you have imported using this tool.  Your posts would be of help to the community. 

Understandably, all MIBs are different and not all MIBs adhere to the specifications. This tool tries to accommodate these differences, but if you notice any issues with a MIB you are trying to import, post a question on the OpenManage Essentials forum.

Ensure the following before using this utility:

• The remote device supports SNMP (v1/v2) protocol.
• SNMP services on the remote device are working fine and trap destination point to
  the OME system.
• You have the device specific SNMP MIB files (main MIB and its reference MIBs).
• Validate these specific MIB(s) using a standard MIB compiler tool.

Download: OpenManage Essentials MIB Import Utility v1.4 (for OME v2.0)

Download: OpenManage Essentials MIB Import Utility v1.3 (for OME v1.3)

Download: OpenManage Essentials MIB Import Utility v1.2 (for OME v1.2)

Download: OpenManage Essentials MIB Import Utility v1.1 (for OME v1.1)

Download: OpenManage Essentials MIB Import Utility v1.0 (for OME v1.0.1)

Whitepaper: Monitoring Force 10 Switches in OpenManage Essentials   (Deprecated)

Whitepaper: Monitoring HP Servers and Third Party Hardware in OpenManage Essentials  

Videos:

MIBImport Utility Overview:

(Please visit the site to view this video)

Adding a trap definition:

(Please visit the site to view this video)

Deleting a trap definition:

(Please visit the site to view this video)

Editing a trap definition:

(Please visit the site to view this video)

Reverting a trap definition:

(Please visit the site to view this video)

For more information about OpenManage Essentials, go to www.DellTechCenter.com/OME

Quick Links:

What is CMC for VRTX?

The newly announced Dell PowerEdge VRTX is a revolutionary, easy-to-manage, remote and office-optimized platform that converges servers, storage and networking into a compact package. It can hold up to 4 server nodes, up to 48TB of integrated, shared storage, and network switching.

Unique VRTX Features

More than simply a small blade server, the Dell PowerEdge VRTX offers something that no other blade server solution has: the ability to use PCIe slots. By combining the density of blade servers with the flexibility of rack server I/O options with PowerEdge VRTX, Dell gives you the flexibility to use less expensive PCIe cards while still being managed through shared chassis management. Another exciting new feature is VRTX's shared storage and on-board RAID controller. Pulling this all together into one, easy-to-manage platform is where VRTX shines.

CMC's role

Part of each VRTX platform, CMC is a dedicated, hot-pluggable module (a second, redundant unit is optional) within the platform that provides a secure web/browser-based interface that is used to take inventory, perform configuration and monitoring tasks, remotely power on/off blades and enable alerts for events on servers and components in the blade chassis. CMC integrates with each of the VRTX server nodes’ embedded iDRAC module, so users can perform iDRAC functions such as opening a remote console session from the CMC interface. Chief among those configuration tasks is setting up shared storage, creating virtual disks and managing PCI slot assignments. Like iDRAC7, CMC for VRTX is licensed in two different varieties: Express and Enterprise. More details on the difference between what comes with each license for both CMC and iDRAC7 for VRTX is available here.

What's New

( top )

( top )

( top )

( top )

Hardware

( top )

  ( top )

Under Construction

What is Catalog?

Biz Client Catalog

Biz Client Catalog is an aggregation of all Dell Update Packages’ (DUP) metadata carried for Dell Optiplex, Dell Latitude, Dell Precision and Dell Tablet brands of systems. These are utilized through end-user products like Dell Command Update/ Dell Client System Update, Dell Repository Manager and Software Centre Configuration Manager / Software Center Update Publisher

Biz Client Catalogs are released every fortnight on the 2nd and 4th Tuesday of every month

Enterprise Catalog

Enterprise Catalog is an aggregation of all Bundles and Dell Update Packages’ metadata carried for Dell PowerEdge, Dell PowerVault and Dell EqualLogic Servers

Enterprise Catalogs are released every month 2nd Friday

What's New + Downloads

 LC Catalog