Network Adapters and Logical Disks discovery problem for windows server 2019

Alireza Zarif 16 Reputation points
2021-01-08T13:27:12.173+00:00

Hi,
I have a problem discovering logical disks and network adapters for a server with 2019 data-center operating system.
All the other logical disks and network adapters have discovered without any problem and the point is that, those are on windows server 2016 and 2012 operating system.
I see event 22402 in event viewer:
‌‌Forced to terminate the following PowerShell script because it ran past the configured timeout 360 seconds.
Script Name: Microsoft.Windows.Server.10.0.LogicalDiskDiscovery.ModuleType.ps1

I checked logical disk discovery Powershell and in the beginning it checks the sever clustering.
I execute below command and it freezes in Powershell with no answer.

$oInstances = Get-WmiObject -Namespace "root\cimv2" -Query "Select ID, Name from Win32_ServerFeature where Name = 'Failover Clustering'"

I am not sure if this is the problem but this command should have an answer.
So what's the problem here?
The agent is updated to last version 10.19.10153

Thanks,
Alireza

Operations Manager
Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,493 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. CyrAz 5,181 Reputation points
    2021-01-08T13:43:42.9+00:00

    The problem is more a WMI problem than a SCOM problem. SCOM relies heavily on WMI, and WMI can become corrupted pretty easily.
    You'll find various procedures on how to reset/restore WMI but be aware that this can cause more damage than good, so always do a backup or snapshot before trying these.

    0 comments No comments

  2. AlexZhu-MSFT 5,956 Reputation points Microsoft Vendor
    2021-01-11T01:52:09.67+00:00

    Hi,

    As CyrilAzoulay explained, operations manager did not get the return of the script within 6 minutes. At such situation, we may try to fix the WMI as suggested. Besides, can we execute the following cmdlet?

    Get-WmiObject -Namespace "root\cimv2" -Query "select * from Win32_LogicalDisk WHERE (DriveType=3 or DriveType=6) and FileSystem!=null"
    

    Hope the above information helps.

    Alex Zhu


    If the response is helpful, please click "Accept Answer" and upvote it.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.