You are browsing the archive for SCE.

SCE 2007 SP1 : Client performance issues and pure frustration !

9:24 pm in AdminUi, essentials, SCE, script by Kenny Buntinx [MVP]

I did a clean install SCE 2007 with SP1 and deployed the agent to all our clients @ our customer.After a while 90% of our  client infrastructure were reporting very slow performance (read icons disappearing from the desktop and no change to hit task manager). People getting mad all over the place ( 150 clients) . After doing some searching I removed all the Information Worker management packs.

No change at all after doing this!

I investigated even more and was thinking that it could be the Mcafee virus scan 8.0/8.5 that had scriptscan enabled.

No change at all after doing this!

I put in an exclusion for the path “C:\Program Files\System Center Operations Manager 2007″ in McAfee VirusScan 8.0/8.5.

No change at all after doing this!

There were a lot of client errors “Performance Monitor Could not find a performance counter” . So I followed the instructions in the thread below to disable the rule as a work around. until they have a long term fix

No change at all after doing this expect for no alerts of that kind in the console.

I tried to investigate some more on the client side now and I discovered this :

SCE 2007 uses ‘cscripts.exe’ to collect data and send back to SCE Management server. For each rule defined in ‘Authoring’ we have a cscript running on the clients to collect that data. Each rule has its own collection interval, but if we use the defaults most of these collection intervals would be the same.Since these collection intervals are same, it means that around 10-12 cscripts for the OS without considering any other custom rules

Each cscript would take a few milliseconds to collect data, and even if you were watching the process console, you wouldnt be able to see them all together but the truth is different . They all fire simultaneously, inadvertently they get ‘stuck’. This is because not enough CPU resource is not available for their execution to complete.Lets say an average of 75 MB of memory for 10 cscripts, that becomes 75 x 10 = 750 MB of RAM just for a Monitoring collection agent that you need for inventory purposes !

Why are each of these cscripts consuming around 50 -140 MB each ! A common XP client has 1 gig of ram and that should be enough !

And why could they not write a mechanism that controls the CSCRIPT launch , instead of launching them all at once !

When is Microsoft likely to sort these bugs out? I thought SP1 was supposed to solve all the issues but it seems they have introduced many new ones.

Why isn’t Microsoft being able to write an agent that does the monitoring for servers ( witch they already have and is ok for a server ) , and write a small agent based on the SCCM client for the PC client management ( e.a software inventory / dustribution/ patching ) .That would make life much easier , for both of us ( product team & consultants )

At the end , we ended up to uninstalling the agent on all the clients ! The funny part is , that when we did the proof of concept , these problems did not arise !

I am pretty frustrated with this product right now , because my ass is on the line at the customer to defend his choice .

Thanks for reading this because it had to come of my chest ….

Hope it helps ,

Kenny Buntinx

SCE 2007 SP1 Network Discovery Process Never Finishes – SQL Broker must be enabled

12:28 pm in SCE by Kenny Buntinx [MVP]

Today we ran into a hair-tearing problem while implementing SCE SP1 at a client…


After successfully installing and configuring SCE 2007 SP1, we ran the Discovery process (Computer and Device Management Wizard) but it seemed to want to run forever and ever. Event viewer showed numerous ‘RPC server unavailable’ errors for the Health Service Modules.

After some investigation, we found the issue may be due to SQL Service Broker being disabled.

To solve this, please check the following steps:

1. Open SQL Server Management Studio.
2. Click New Query.
3. In the query window, enter the following query:

SELECT is_broker_enabled FROM sys.databases WHERE name=’OperationsManager’

4. Click Execute.

If the result returns 0, doing the following steps to enable SQL broker:

5. Run the query:


6. Click Execute.
7. Enter the following query:


8. Click Execute.
9. Close SQL Server Management Studio.

Note: Closing SQL Server Management Studio closes the connection to the database in single user mode.

10. Disable OpsMgr SDK Service and OpsMgr Config Service.
11. Open SQL Server Management Studio.
12.  Click New Query.
13.  In the query window, enter the following query:


14. Click Execute.

You can verify the setting for ENABLE_BROKER is set to 1 by using this SQL query:

SELECT is_broker_enabled FROM sys.databases WHERE name=’OperationsManager’.


Before you can use discovery, you may have to restart the following services: OpsMgr SDK Service, SQL Server, and SQL Server Agent.


Hope it stops you from pulling your hair out as well 😉

Kenny Buntinx

Merlijn Van Waeyenberghe