The management pack for Endpoint protection 2012 for Linux version 4.5.10.1 fails to discover scep on servers with 1.5.1-150 aka the omi agent. I haven't found a newer version of the MP. 

I am curious if anyone else is having this issue and if so, were they able to overcome it.

I ran winrm invoke with the command and it does return an output but its slightly different. The discovery script in the sealed management pack (Microsoft.SCEP.Linux.Library.xml) is looking for ExecuteShellCommand_OUTPUT
($StdOut = $xml.DataItem.WsManData.ExecuteShellCommand_OUTPUT.StdOut) and based on my outputs below the new agent is returning SCX_OperatingSystem_OUTPUT. I  am assuming this is the problem but don't know how to fix it.

 



Host that works with 1.4.1-308

ExecuteShellCommand_OUTPUT
    ReturnCode = 0
    StdOut = scep_daemon installed
scep_daemon stop
 11:46:26 up 56 days,  2:33,  0 users,  load average: 0.00, 0.00, 0.00

    StdErr = error[66a40000]: Agent not authorized

    ReturnValue = true



Host with 1.5.1

SCX_OperatingSystem_OUTPUT
    ReturnValue = TRUE
    ReturnCode = 0
    StdOut = scep_daemon installed
scep_daemon stop
 11:46:57 up 40 days,  1:24,  1 user,  load average: 0.00, 0.00, 0.00

    StdErr = error[607e0000]: Agent not authorized





part of discovery script
<ScriptName>ServiceDiscoveryMapper.ps1</ScriptName>
                <ScriptBody>
                  param($SourceId, $ManagedEntityId, $ComputerName, [string]$CmdOutput)                
                                    
                  function GetDayDiff
                  {
                 param ($nNow, $nDate)
                 
                 if (($nNow) -and ($nDate))
                 {
                 [datetime]$nNow  = $nNow
                 [datetime]$nDate = $nDate
                 $nDiff = $nNow.ToFileTime() - $nDate.ToFileTime()
                 $nDiff = [Math]::Truncate($nDiff / (10000000 * 60 * 60 * 24))
                 }
                 
                 return $nDiff
                  }
 
                  $api = new-object -comObject 'MOM.ScriptAPI'
                  $discoveryData = $api.CreateDiscoveryData(0, $SourceId, $ManagedEntityId)
                  $xml = [xml]$CmdOutput
                  $StdOut = $xml.DataItem.WsManData.ExecuteShellCommand_OUTPUT.StdOut
                  $IsDiscoveryError = 1
                  $DiscoveryErrorText = "error: SCEP not found" + $CmdOutput

Hi Hugage,

Thanks for the info - you are correct the changes from System Center 2012 OpsMgr Sp1 to System Center 2012 R2 OpsMgr involved changes to the CIMOM Server (Open Pegasus to Open management infrastructure).

The xml that the ESET management pack is looking for no longer exists with OMI and needs to be changed to accommodate the new return structure. Lets get a case opened up and see if we can get a suitable solution

Hi,

Was wondering if you got anywhere with this? I am experiencing the same issue. SCOM is happily monitoring my CentOS servers at the OS level. We have installed SEP and the associated management packs but SCOM is not detecting that SCEP is installed.

Cheers

Dave