OME 1.1 identifies "Windows 2008 std without Hyper-V" OS as "Unknown Windows OS Distribution" or "Invalid String"

Hi Alan thanks for the post.

I'm not sure I'm clear.  Generally, if a device gets classified under the Unknown group, there is very little inventory that is retrieved.  Usually just IP addr and maybe MAC address.  So I'm surprised you say you are seeing robust inventory data.

Let's try this, please run the Dell Troubleshooting tool (installed on the OME desktop) against the target server.  Let me know what version of "Server Administrator" is returned in the result set for the SNMP test.

Also, below are some standard troubleshooting steps for discovery, review those as well and we will go from there.

Thanks,

Rob

--

OME Discovery

Here are the important items to check when you are chasing down OME Discovery and Inventory issues.

1. Check FAQ 3.6 if inventory is not showing up.

2. Be sure OMSA is on the managed node (target)  if you are using SNMP/WMI (#3.3)

3. Be sure you have “accept packets” checked on your managed node (#3.4)

4. If discovering a 2008 server, see item #3.5

5. Be sure you check the community string, remember they are *case sensitive* (#3.4).  Did you type it in correctly in the discovery wizard?  Did you type it in correctly in the managed node SNMP properties?  Did you type it in correctly in the TS test screen?

6. Run the SNMP troubleshooting test for SNMP or WMI.  For SNMP the results *must* include the version of OMSA in the table.  For WMI the results *must* contain the words “Dell Server Agent” for the namespace returned.

Thanks Rob - will check out your suggestions tomorrow. Just to clarify, this is a screenshot of what I see for the "flavour" of OS which is not being identified.

 Note - I am on OMSA 6.1 on the server so I'll upgrade tomorrow to latest 7.2(?) and see if that makes any difference.

Thanks v much!

Alan.

 

 

Ok, let me know.  And post the results of the TS tool test for SNMP test...but mask your private data, etc.

thx

Rob

Hi Rob,

Just a quick update. This does not appear to be an issue with DELL ESSENTIALs. It appears that the version of Windows we are using is not recognised by the OMSA itself. This is being worked through a Pro Support case number with Dell Pro Support (I though this may be better than attempting to work on via the forum).

We upgraded to OMSA 7.2 on a number of machines and still had the issue.

I'll let you know how I get on so info can be shared...

Thanks

Alan.

Hi Rob,

We have been given a work around by DELL PROSUPPORT for all the “Windows Server 2008 std/ent without Hyper-V” installations popping up in DELL ESSENTIALS as “Unknown Windows OS Distribution”.

Issue:

Dell Open Manage Server Assistant does not recognise the OS install we have used on a lot of our Windows 2008 installs over the last few years. This is an official SKU from Microsoft however OMSA does not have it in its database.

Short Term Fix (hack):

(Make sure you are on the latest version of OMSA - as of today that is v7.2 for me).

Edit either of these files depending on whether OMSA 32 bit or 64 bit installed. This is done on the SERVER being monitored NOT the Dell ESSENTIALS server:

• C:\Program Files\dell\sysmgt\omsa\ini\dcsdst64.ini
• C:\Program Files (x86)\dell\sysmgt\omsa\ini\dcsdst32.ini

Search and Replace the following text:

•            Search:             Unknown Windows OS Distribution
•            Replace:           Windows Server 2008 Standard without Hyper-V  OR Windows Server 2008 Enterprise without Hyper-V

Then cycle the OMSA services on the server being monitored:

• DSM SA Data Manager
• DSM SA Event Manager
• DSM SA Connection Service
• DSM SA Shared Services

Dell say they have added this to the issues register for the product which "may" be fixed in a later release.

Just thought I would share results from our OMSA issue and to confirm - this issue is not with DELL ESSENTIALS. It's with DELL Open Manage Server Administrator (OMSA).

Alan.