I finally figured it out, of course it's a bone-headed error. I installed OMCI across the domain, and the only four computers that didn't respond were Precision T1500.  A brief search shows they don't seem to support OMCI. [URL]  So, that's that.  All is working as designed. Thanks for the help, Steve Kamego
We have a single DC which is running OME 1.3, PowerEdge T710 Server 2008 R1. I'm attempting to get OMCI communicating on a test PC, Precision T1500 Win 7.  I've successfully installed OMCI ver 8.2.1.70 on the PC.  OME doesn't pick up on OMCI as a Data Source, only WMI is shown in Data Sources, so the PC has unknown health status & no hardware logs. On the PC, I've attempted to install OMCI with SNMP enabled and disabled.  I've also attempted to disable and enable SNMP in services. On OME, I've set up discovery  with WMI enabled and SNMP enabled, and WMI enabled and SNMP disabled, same result. Using the troubleshooting tool on the DC, for WMI, both Windows NameSpace and Dell Client Agent (OMCI) NameSpace show they are present. We have a SonicWall NSA router/firewall with McAfee/SonicWall Enforced Client AV/firewall.  I've disabled the software firewall, and for the hardware firewall, there is an existing rule for LAN to LAN to pass all.  I've also set a rule for port 1311 for LAN to LAN to allow all. On the PC, using NMAP, port 1311/tcp shows open.  On the DC, using the troubleshooting tool, port 1311 shows "Could not connect to 1311 port". I should state, OME does successfully pick up on OMSA on the Servers.  It also picks up successfully on our PowerConnect 2824 and network printer. I'm not sure I'm convinced this is a firewall issue, I don't show any logs of blocking traffic and it does successfully communicate with OMSA, just not OMCI.  Why would the troubleshooting tool show OMCI is present, but OME not pick up on it? What am I missing?  I'll give any more details if required. Thanks, Steve
OMCI communication troubles