This is not a problem.  This is by design.  OpsMgr agent extracts ALL runtime scripts from loaded workflows, on to the disk.  Then – it will call these scripts using cscript.exe and passing specific parameters to them.  This is not a “problem” on DC’s.

DC’s might run a large number of cscript.exe processes at the same time, especially right after healthservice restart.  During this time – you will see high processor utilization, which is also normal, however unwanted.  This should not last for very long.

It has the highest impact on machines that are on VERY old hardware, not enough memory, or virtualized on an over-committed host.

What you can do to mitigate this in general:

1.       Apply cscript 5.7 update.  This has been reported to use less CPU per script.

2.       Ensure your healthservice is not restarting constantly.

3.       Disabled script based workflows for older machines and live without the monitoring they provide.

4.       Ensure you don’t do ANY custom authoring, using scripts, that run on multiple instances per agent, and don’t allow for cookdown of the script datasource.

Can anybody having the idea on this…please guide me…

Many Thanks,

Narendra.

So many VB scripts are running in the  \Health Service State\Monitoring Host Temporary Files 61and 62 folders on the agent server.

I am running with SCOMsp1 with latest Management packs.

While running the scripts which service or .exe will it use….how to know which script is running for what purpose..

Especially I having the problem with DC’s .  I want to know what are the SCOM Scripts running from the DC servers and what is the result.

Is all the scripts running by the agent  are stored at the time of Agent installation .

Can anybody faced this issue…please suggest me ….

Many Thanks,

Narendra.

DISCLAIMER:
This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated.

==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/momlist/

DISCLAIMER:
This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated.

==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/momlist/

==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/momlist/