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(256, 87%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
SCOM agent managed version,doamin,version are showing unknow checked all other tasks MP and connectivity are working fine
Hi @Lloyd33-9166,
Were these agents recently discovered? If this is the case, give it some time for the correct information to populate.
If the agents have already been added/discovered some time ago, start by checking the Operations Manager event log for any errors.
Also try checking with PowerShell if you gey any agent information:
Import-Module OperationsManager
Get-SCOMAgent | Select Name, Version
If PowerShell returns the correct information, try clearing the cache of your Operations Console and your SCOM management servers.
How and When to Clear the Cache
----------
(If the reply was helpful please don't forget to upvote or accept as answer, thank you)
Best regards,
Leon
Run the powershell it shows blank information in agent version agent is already been monitoring for a long time not seeing any errors in event viewer all MP looks good and imported I manually cleared cache and removed from agent and re-added still the details are unknown.
Hey @Lloyd33-9166,
Are all agents affected?
If not, the best thing to do is to check the events on one of the affected agents after restart of the agent. Look for errors or warnings.
If all agents are affected I would do the same, but on the management servers.
I would also ccheck the overall SCOM management group health in the console.
Regards,
Stoyan
These are only happening for few agents I restarted the services in affected agent seeing below errors is this might be the issue
Health Service Script : 1010
Server_Discovery.vbs : Insuficient number of parameters. Script was aborted.
Health Service Script : 1010
RemoteAgent_Discovery.vbs : Insuficient number of parameters. Script was aborted.
It appears that these two errors are discovery scripts for the BackupExec management pack if I'm not mistaken.
I suggest you start troubleshooting by following Kevin's guide over here:
https://kevinholman.com/2009/10/01/fixing-troubled-scom-agents/
Hi,
I doubt that those two scripts can be the cause for the agent details not being discovered.
I would follow the article Leon posted on one of the affected agents and see what comes up.
I would also encourage you to uninstall the AV software from one of those agents, reboot and test. Deactivating the services is unfortunately not sufficient because of the so called filter drivers, which remain active. Please test this and get back to us.
Regards,
Stoyan
I checked further on this looks like server objects are not discovered for these servers triggering on demand discovery is failing
Initialization of a module of type "Microsoft.SystemCenter.OnDemandDiscoveryTriggerAction" (CLSID "{31742191-31A5-4C93-9D9B-92E6CD2FA665}") failed with error code The parameter is incorrect. causing the rule "Microsoft.SystemCenter.TriggerOnDemandDiscovery" running for instance "" with id:"{ED01FCC8-5F20-7146-B00A-020B22479B46}" in management group "". Error Code: -2130771961 (Unknown error (0x80ff0007)).
Could you provide some more information below: