This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 1%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETK%3C/text%3E%3C/svg%3E)
Dear all,
I have encountered the difficulties of SCOM monitoring Storage Spaces direct.
Created Custer cl1 with 2 nodes cl1n1 and cl1n2. Installed the SCOM agents on both nodes and activated the agent proxy on these nodes.
Used a domain account as Agent Action Account that is a member of the local administrator's group on both Cluster nodes.
MP I imported:
I left these profiles empty.
As result S2S seed is not discovered in SCOM. All other S2D components are not discovered too.
Please tell me what I'm doing wrong? How to set up S2D monitoring in SCOM
The problem has been solved. On cluster in hclm\cluster "OSVersion" was set to "10 (17763)". S2Dseeddiscovery.ps1 script expects 10.0* value at "OSVersion". S2D discovery script start working after changing the OSVersion to the "correct" value.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 92%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXM%3C/text%3E%3C/svg%3E)
Hi,
It sounds like you're having a tough time getting Storage Spaces Direct (S2D) to be properly discovered in SCOM.
Here are a few steps and checks that might help resolve the issue:
I hope these steps help you get S2D monitoring up and running in SCOM. Let me know if you need further assistance or if there's anything else I can help with!
Hi,
Thank you for your reply. I used the correct MP ver 1.0.47.4.
Unfortunately, I do not find anything in the "operation manager" log on either the proxy agent or the SCOM management server at all regarding the S2D discovery. Even attempts to do this....
Please anyone help me solve the problem. There is no information about this problem on the internet
delete
Could you please go through the step-by-step guide and check if there are any actions that might have been missed?
The problem has been solved. On cluster in hclm\cluster "OSVersion" was set to "10 (17763)". S2Dseeddiscovery.ps1 script expects 10.0* value at "OSVersion". S2D discovery script start working after changing the OSVersion to the "correct" value.
That's fantastic news! Thanks for your feedback. Please click 'Accept Answer' to close this thread.