How to verify if a Dell custom ESXi image was installed

I'm 99% sure I used a custom Dell ESXi image when installing v4.1 on my 2950, however, I want to verify for I'm about to update to v5.5 via a Dell custom image .ISO.  How can I verify a Dell custom image is currently installed?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Joseph DalyCommented:
You should be able to do this through vcenter. Click on the host that you are looking to upgrade and on the summary tab of the host check the location for Image Profile. This should show the image being used.

For example we are an HP shop so ours shows. (Updated) HP-ESXi-5.5.0-U3
gopher_49Author Commented:
I see a host profile field but it's empty...  At the top of the screen I have VMWare ESXi, 4.1.0, 348841... But..  The only mention of a profile is the host profile and it's blank.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Is 348841 your build ?

If you go to Hardware Status, does it show the hardware ?
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

gopher_49Author Commented:

Yes.  348841 is my build.  On the hardware status I see all hardware sensors and they are accurate.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Looks like a Dell OEM version, to be honest, I would recommend, a full installation rather than an upgrade.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
gopher_49Author Commented:

So..  Would I just install get a new USB memory stick..  Load a clean install to it and build my network settings?   That's really the only real config I have...  And of course import the LUNs
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Correct, as quick as that!
gopher_49Author Commented:
Sounds drama free for I've read botched upgrades can be troublesome.  I verified on Dell's website that my 2950 hardware is supported on the 5.5 image.  I'll schedule downtime this weekend and perform the clean install.

I'll close this ticket / question for any other issues that might occur would be a different topic.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, we do not do upgrades!
gopher_49Author Commented:
I trust your opinion..  :)  Thanks for the help!
Show what image you installed:
Log in via SSH and:
> software profile get
gopher_49Author Commented:
I get a not found error when running that command.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
missing a command, which should be >-

esxcli software profile get

which will return...

(Updated) Dell ESXi-5.5-1331820(A01)
   Name: (Updated) Dell ESXi-5.5-1331820(A01)
   Vendor: esxi006
   Creation Time: 2015-05-26T14:08:29
   Modification Time: 2015-05-26T14:10:58
   Stateless Ready: False

also if you look at your vibs (drivers), if you have any which state OEM, then you know you have an OEM version!

this is ouput from ESXi 5.5 (DELL OEM!)

 2015-05-26T14:08:29.468956+00:00: The following VIBs are
        esx-base      5.5.0-2.62.2718055
        misc-drivers  5.5.0-2.62.2718055
        mtip32xx-native       3.3.4-1vmw.550.1.15.1623387
        sata-ata-piix 2.12-10vmw.550.2.33.2068190
        net-e1000e    1.1.2-4vmw.550.1.15.1623387
        sata-ahci     3.0-21vmw.550.2.54.2403361
        scsi-megaraid-sas     5.34-9vmw.550.2.33.2068190
        esx-tboot     5.5.0-2.33.2068190
        xhci-xhci     1.0-2vmw.550.2.39.2143827
        tools-light   5.5.0-2.62.2718055
      2015-05-26T10:01:38.728819+00:00: The following VIBs are
        vmware-fdm    5.5.0-2646482
      2015-05-26T10:00:12.523958+00:00: The following VIBs have been
        vmware-fdm    5.5.0-1750787
      2014-11-25T15:14:31.810671+00:00: The following VIBs are
        vmware-fdm    5.5.0-1750787
      2014-10-20T15:49:02.678696+00:00: The following VIBs are
        esx-base      5.5.0-0.15.1746974
        misc-drivers  5.5.0-0.7.1474526
        tools-light   5.5.0-0.14.1598313
      The general availability release of VMware ESXi Server 5.5.0
      brings whole new levels of virtualization performance to
      datacenters and enterprises.

   VIBs: ata-pata-amd 0.3.10-3vmw.550.0.0.1331820, ata-pata-atiixp 0.4.6-4vmw.550.0.0.1331820, ata-pata-cmd64x 0.2.5-3vmw.550.0.0.1331820, ata-pata-hpt3x2n 0.3.4-3vmw.550.0.0.1331820, ata-pata-pdc2027x 1.0-3vmw.550.0.0.1331820, ata-pata-serverworks 0.4.3-3vmw.550.0.0.1331820, ata-pata-sil680 0.4.8-3vmw.550.0.0.1331820, ata-pata-via 0.3.3-2vmw.550.0.0.1331820, block-cciss 3.6.14-10vmw.550.0.0.1331820, dell-configuration-vib 5.5-0A01, ehci-ehci-hcd 1.0-3vmw.550.0.0.1331820, elxnet 10.0.575.7-1OEM.550.0.0.1198611, esx-base 5.5.0-2.62.2718055, esx-dvfilter-generic-fastpath 5.5.0-0.0.1331820, esx-tboot 5.5.0-2.33.2068190, esx-xlibs 5.5.0-0.0.1331820, esx-xserver 5.5.0-0.0.1331820, ima-be2iscsi, ima-qla4xxx 500.2.01.31-1vmw.0.3.040121, ipmi-ipmi-devintf 39.1-4vmw.550.0.0.1331820, ipmi-ipmi-msghandler 39.1-4vmw.550.0.0.1331820, ipmi-ipmi-si-drv 39.1-4vmw.550.0.0.1331820, lpfc 10.0.575.8-1OEM.550.0.0.1198611, lsi-mr3, lsi-msgpt3, misc-cnic-register 1.78.1.v55.7-1OEM.550.0.0.1198611, misc-drivers 5.5.0-2.62.2718055, mtip32xx-native 3.3.4-1vmw.550.1.15.1623387, net-bnx2 2.2.3t.v55.7-1OEM.550.0.0.1198611, net-bnx2x 1.78.28.v55.2-1OEM.550.0.0.1198611, net-cnic 1.78.12.v55.6-1OEM.550.0.0.1198611, net-e1000, net-e1000e 1.1.2-4vmw.550.1.15.1623387, net-enic, net-forcedeth 0.61-2vmw.550.0.0.1331820, net-igb, net-ixgbe 3.18.7-1OEM.550.0.0.1198611, net-mlx4-core, net-mlx4-en, net-nx-nic 5.0.621-1vmw.550.0.0.1331820, net-qlcnic 5.5.164-1OEM.550.0.0.1198611, net-qlge, net-tg3 3.133d.v55.1-1OEM.550.0.0.1198611, net-vmxnet3, ohci-usb-ohci 1.0-3vmw.550.0.0.1331820, qlnativefc, rste, sata-ahci 3.0-21vmw.550.2.54.2403361, sata-ata-piix 2.12-10vmw.550.2.33.2068190, sata-sata-nv 3.5-4vmw.550.0.0.1331820, sata-sata-promise 2.12-3vmw.550.0.0.1331820, sata-sata-sil 2.3-4vmw.550.0.0.1331820, sata-sata-sil24 1.1-1vmw.550.0.0.1331820, sata-sata-svw 2.3-3vmw.550.0.0.1331820, scsi-aacraid, scsi-adp94xx, scsi-aic79xx 3.1-5vmw.550.0.0.1331820, scsi-be2iscsi, scsi-bnx2fc 1.78.16.v55.4-1OEM.550.0.0.1198611, scsi-bnx2i 2.78.11.v55.4-1OEM.550.0.0.1198611, scsi-fnic, scsi-hpsa 5.5.0-44vmw.550.0.0.1331820, scsi-ips 7.12.05-4vmw.550.0.0.1331820, scsi-megaraid-mbox, scsi-megaraid-sas 5.34-9vmw.550.2.33.2068190, scsi-megaraid2 2.00.4-9vmw.550.0.0.1331820, scsi-mpt2sas, scsi-mptsas, scsi-mptspi, scsi-qla2xxx 902.k1.1-9vmw.550.0.0.1331820, scsi-qla4xxx 634.55.20.0-1OEM.550.0.0.1198610, tools-light 5.5.0-2.62.2718055, uhci-usb-uhci 1.0-3vmw.550.0.0.1331820, vmware-fdm 5.5.0-2646482, xhci-xhci 1.0-2vmw.550.2.39.2143827
~ #
gopher_49Author Commented:
On my new Dell ESXi v5.5 custom image it returns the Dell custom image version, however, on one of my other environments running Dell custom image for v4.1 it returns 'Unknown namespace software'.  This gets back to why a clean install makes sense.  Especially on environments where the networking and storage is easy to add back.   I ended up performing a clean install for upgrade from v4.1 to v5.5 and it went really smooth.  But..  The esxcli software profile get is a great command to know.  This would of made me go the clean install route for sure..  And it seems the clean install route is the way to go in general.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
v4.1 does not support esxcli, this was introduced in 5.x.

in 4.1 you use - esxupdate
South ModModeratorCommented:

I've removed the Assisted Solution (Comment #40863040) since you indicated it produced an error. In the future, please only accept those comments which actually provide you with a solution, or with assistance towards a solution.

Community Support Moderator
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.