Here’s a new Knowledge Base article we published. This one talks about an issue where an Operations Manager AD Replication Monitor generates an "Invalid Script Parameter Configuration" error message.
System Center Operations Manager 2007 generates alerts on Domain Controllers regarding incorrect script parameters with an alert context similar to the following: Script Parameters are configured incorrectly And Invalid Script Parameter Configuration AD Replication Monitoring : detected an error with one or more parameters. The error is: InterSiteExpectedMaxLatency must be greater than the IntrasiteExpectedMaxLatency parameter. IntersiteExpectedMaxLatency = 15 IntrasiteExpectedMaxLatency = 30 IntersiteExpectedMaxLatency will be set to the value 90 for this execution of this script. You also see an event with ID 66 in the Domain Controller's Operations Manager log: Log Name: Operations Manager Source: Health Service Script Date: Event ID: 66 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: DC1.contoso.com Description: AD Replication Monitoring : detected an error with one or more parameters. The error is: InterSiteExpectedMaxLatency must be greater than the IntrasiteExpectedMaxLatency parameter. IntersiteExpectedMaxLatency = 15 IntrasiteExpectedMaxLatency = 30 IntersiteExpectedMaxLatency will be set to the value 90 for this execution of this script. To correct the error, find the rule 'Script - AD Replication Monitoring' and from the response tab of its properties, edit the script and modify the parameter in question.
Though the alert context points us towards fixing the AD Replication Monitor and a script, the error occurs due to a rule that has incorrect values specified in the overrides.
To resolve this issue follow these steps:
For the most current version of this article please see the following:
2722619 - Operations Manager AD Replication Monitoring generates "Invalid Script Parameter Configuration" error
J.C. Hornbeck | System Center & Security Knowledge Engineer
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/ ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ Operations Manager Team blog: http://blogs.technet.com/momteam/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Aah, that doesn't seem to be worded right:
"If the overridden value for this parameter is lesser than the value of Intersite Expected Max Latency parameter, modify it to a lesser value."
Should that be 'greater' in there somewhere?