Agent and Health Service Discovery Scripts *.js --- script issues (what do they do?)
Mainly ‘DiscoverAgentRelationshipSettings.js’ and ‘DiscoverHealthServiceCommunication.js’, I’ve looked these up.
‘DiscoverAgentRelationshipSettings.js’ is a discovery script that appears to be required for my AD intergration to run? I’m assuming it get’s
configuration information from SCP in AD I’ve set up. Do I have to run this script for AD integration to work properly? If so, can I change the interval seconds and the time seconds in an override of somekind to resolve or at least slow down the
script errors I get for this? They usually are not high repeaters but on a some machines they do happen quite a bit more often.
‘DiscoverHealthServiceCommunication.js’ I’m just not sure about at all. Where is it, I couldn’t find anything on it? Does it need to run?
Can I override any of the settings to resolve the script issues I have, again most not high repeaters but some machines do happen quite a bit more often.
I’ve applied the latest WSH patch and WMI fixes suggest for script issues to all the affected machines. It did seem to slow down some from that but it’s
still my main script error on agent machines.
April 21st, 2010 10:21pm
see this post:
http://blogs.technet.com/stefan_stranger/archive/2010/03/10/basic-troubleshooting-discovery-script-follow-up-on-kevin-s-post.aspx and the post of kevin holman as well.Rob Korving
http://jama00.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
April 22nd, 2010 2:00pm
debugging each server with multiple discovery script errors isn't really an option here. it's just to many. i'm not even sure if the debugging process is the same with the js script files. The other problem is they don't happen all the
time and the times they do happen do not coincide with heavy load times like backups, etc.
Can anyone just tell me what these scripts do????????
April 22nd, 2010 10:09pm
i think not many people will know unless they had similar issues and looked at the script itself. so i guess you have to look yourself if you want to know exactly what they do.
You probably don't have to debug each server and js script will work too.Rob Korving
http://jama00.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
April 22nd, 2010 11:02pm
If you know what managment pack they are hosted in, then you can export the sealed MP via powershell. That should dump the sealed MP to XML. Now you can scrape through the XML to find the actual script. There maybe params associated
with the script, if so, you can go to one of your agents that has this script, search for the folder it is in, then use cscript to manually execute it on the box and see what occurs.Regards, Blake Email: mengottohotmail.com Blog: http//discussitnow.spaces.live.com
April 22nd, 2010 11:20pm
I will debug a script tomorrow and post back the findings here. My concern is when I go to run the script, it will run normally so I won't have anything to show me what's wrong because these scripts run most of the time.
Free Windows Admin Tool Kit Click here and download it now
April 23rd, 2010 12:52am
As I expected, no failure when it ran. The scripts are both related to AD integration but this bring me back to square one, what can I do to resolve these script error? Would it be alright to change the intervals for these scripts?
Below is a snippet from the debug:
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation. All rights reserved.
SourceType: 0
SourceId {00000000-0000-0000-0000-000000000000}
ManagedEntityId: {00000000-0000-0000-0000-000000000000}
ComputerIdentity: mycomputer.domain.forest.com
ManagementGroupName: dev
EnableADIntegration value: true
UseActiveDirectory value: true
Primary SCP Info value: myMGServer.domain.forest.com
Registry Path: HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Agent Management Groups\dev\AD Cache\Secondary SCP Info Root\Secondary SCP Info 2\Service DNS Name
Registry Criteria: /(Primary|Secondary) SCP Info\s{0,1}\d*/ig
RegEx Results: Secondary SCP Info ,Secondary SCP Info 2
Could not find "Secondary SCP Info 2\Service DNS Name" under "HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Agent Management Groups\dev\AD Cache\Secondary SCP Info Root\"
This is not a fatal error as the HealthService may not have any failovers.
Match results: Secondary SCP Info 2
Registry Path: HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Agent Management Groups\dev\AD Cache\Secondary SCP Info Root\Secondary SCP Info 3\Service DNS Name
Registry Criteria: /(Primary|Secondary) SCP Info\s{0,1}\d*/ig
RegEx Results: Secondary SCP Info ,Secondary SCP Info 3
Could not find "Secondary SCP Info 3\Service DNS Name" under "HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Agent Management Groups\dev\AD Cache\Secondary SCP Info Root\"
This is not a fatal error as the HealthService may not have any failovers.
Match results: Secondary SCP Info 10
<DataItem type="System.DiscoveryData" time="2010-04-23T16:58:23.2724531-04:00" sourceHealthServiceId="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"><DiscoveryType>0</DiscoveryType><DiscoverySourceType>0</DiscoverySourceType><DiscoverySourceObjectId>{00000000-0000-0000-0000-000000000000}</DiscoverySourceObjectId><DiscoverySourceManagedEntity>{00000000-0000-0000-0000-000000000000}</DiscoverySourceManagedEntity><RelationshipInstances><RelationshipInstance
TypeId="{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}" SourceTypeId="{xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}" TargetTypeId="{xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}"><SourceRole><Settings><Setting><Name>{xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}</Name><Value>agentserver</Value></Setting></Settings></SourceRole><TargetRole><Settings><Setting><Name>{xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}</Name><Value>myMGServer</Value></Setting></Settings></TargetRole></RelationshipInstance><RelationshipInstance
TypeId="{xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}" SourceTypeId="{xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}" TargetTypeId="{xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}"><SourceRole><Settings><Setting><Name>{xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}</Name><Value>agentServer</Value></Setting></Settings></SourceRole><TargetRole><Settings><Setting><Name>{xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}</Name><Value>myMGServer</Value></Setting></Settings></TargetRole></RelationshipInstance></RelationshipInstances></DataItem>
April 24th, 2010 12:15am
Anyone got any other ideas about how to approach this issue?
Free Windows Admin Tool Kit Click here and download it now
April 28th, 2010 7:23pm
Hi,
I will mark this thread as answered due to no activity for a long time. Feel free to re-open it if needed. ThanksAnders Bengtsson | Microsoft PFE | blog at http://www.contoso.se
December 22nd, 2010 6:50am