locked
Skype for Business 2015 Management pack not able to discover instance installed on WIndows 2012 R2 with Powershell5 RRS feed

  • Question

  • Management pack has successfully discovered the Instance which are installed on with Winnows 2008 with power shell 3.0 but it s not able to discover  Skype for Business  2015 installed on  Windows 2012 R2 with Powershell5. We are currently running  on SCOM 2012 R2 with UR11 Patch. So there are no issue with patch level. Let me know if there is any workaround. There are no issues with Service account. As it has successfully discovered 42 instances and monitoring all roles on that machine.

    Omkar umarani SCOM STUDENT

    Sunday, October 30, 2016 12:16 PM

Answers

  • After removing patch KB3134759. Everything back to normal. Case solved.

    thanks and regards

    Onkar umarani


    Omkar umarani SCOM STUDENT

    • Marked as answer by Onkar Umarani Monday, November 14, 2016 11:42 PM
    Monday, November 14, 2016 11:42 PM

All replies

  • Hi Sir,

    Is there any clue under "Operations Manager" in event viewer ?

    Best Regards,

    Elton


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, October 31, 2016 5:26 AM
  • Hello Onkar,

    If the instances are showing healthy under Agent Managed, and not getting discovered by SFB2015 MP you can follow below steps:

    1: Check if "Network Service" is added under below groups on those servers.

    • RTC Component Local Group
    • RTC Local Administrators

    2: Clear agent cache and restart Microsoft Monitoring Agent service on the server.

    3: Putting those servers under Maintenance Mode for 30 Minutes.

    4: Last, Rebooting the servers.

    http://chrishayward.co.uk/2015/12/10/skype-for-business-2015-edge-servers-not-discovered-by-scom-sfb-management-pack/

    Regards,

    Shashi

    Monday, October 31, 2016 10:22 AM
  • No Clue under Event Viewer and already tried clear agent/reboot/maintenance mode. Already check service account.

    Any comments about Powershell5 Version and SCOM agent relation.


    Omkar umarani SCOM STUDENT

    Monday, October 31, 2016 10:26 AM
  • Hello Onkar,

    If the agent is showing healthy under Agent Managed, it should not be an issue with PowerShell5. Please confirm if other Management Packs are able to discover those instances, like Windows Server 2012 MP.

    Regards,

    Shashi

    Monday, October 31, 2016 10:49 AM
  • Yes it's able to discover. I will update tracelog tomorrow.

    Omkar umarani SCOM STUDENT

    Monday, October 31, 2016 11:46 AM
  • After Generating Trace i found this .

    [3]15704.16488::11/02/2016-08:01:52.247 [ModulesBatchResponse] [] [Warning] :TraceStdErr{batchresponse_cpp1150}The process '"C:\Windows\system32\windowspowershell\v1.0\powershell.exe" -Command ".\DiscoverMachine.ps1"' returned with error:
    new-object : The term 'new-object' is not recognized as the name of a cmdlet,
    function, script file, or operable program. Check the spelling of the name, or
    if a path was included, verify that the path is correct and try again.
    At C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service
    State\Monitoring Host Temporary Files 11\1302\DiscoverMachine.ps1:32 char:22
    + $Script:logMessage = new-object System.Text.StringBuilder
    +                      ~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (new-object:String) [], CommandN
       otFoundException
        + FullyQualifiedErrorId : CommandNotFoundException
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service
    State\Monitoring Host Temporary Files 11\1302\DiscoverMachine.ps1:35 char:3
    +   $Script:logMessage.Append($message) | out-null
    +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service
    State\Monitoring Host Temporary Files 11\1302\DiscoverMachine.ps1:36 char:3
    +   $Script:logMessage.Append("`n") | out-null
    +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service
    State\Monitoring Host Temporary Files 11\1302\DiscoverMachine.ps1:35 char:3
    +   $Script:logMessage.Append($message) | out-null
    +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service
    State\Monitoring Host Temporary Files 11\1302\DiscoverMachine.ps1:36 char:3
    +   $Script:logMessage.Append("`n") | out-null
    +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service
    State\Monitoring Host Temporary Files 11\1302\DiscoverMachine.ps1:35 char:3
    +   $Script:logMessage.Append($message) | out-null
    +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service
    State\Monitoring Host Temporary Files 11\1302\DiscoverMachine.ps1:36 char:3
    +   $Script:logMessage.Append("`n") | out-null
    +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service
    State\Monitoring Host Temporary Files 11\1302\DiscoverMachine.ps1:35 char:3
    +   $Script:logMessage.Append($message) | out-null
    +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service
    State\Monitoring Host Temporary Files 11\1302\DiscoverMachine.ps1:36 char:3
    +   $Script:logMessage.Append("`n") | out-null
    +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service
    State\Monitoring Host Temporary Files 11\1302\DiscoverMachine.ps1:35 char:3
    +   $Script:logMessage.Append($message) | out-null
    +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service
    State\Monitoring Host Temporary Files 11\1302\DiscoverMachine.ps1:36 char:3
    +   $Script:logMessage.Append("`n") | out-null
    +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service
    State\Monitoring Host Temporary Files 11\1302\DiscoverMachine.ps1:35 char:3
    +   $Script:logMessage.Append($message) | out-null
    +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service
    State\Monitoring Host Temporary Files 11\1302\DiscoverMachine.ps1:36 char:3
    +   $Script:logMessage.Append("`n") | out-null
    +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service
    State\Monitoring Host Temporary Files 11\1302\DiscoverMachine.ps1:35 char:3
    +   $Script:logMessage.Append($message) | out-null
    +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], ParentContainsErrorRec
       ordException
        + FullyQualifiedErrorId : InvokeMethodOnNull


    Omkar umarani SCOM STUDENT

    Wednesday, November 2, 2016 3:36 PM
  • After removing patch KB3134759. Everything back to normal. Case solved.

    thanks and regards

    Onkar umarani


    Omkar umarani SCOM STUDENT

    • Marked as answer by Onkar Umarani Monday, November 14, 2016 11:42 PM
    Monday, November 14, 2016 11:42 PM