You are browsing the archive for 2009 January.

New Configuration Manager Knowledge Base articles

8:25 pm in ConfigMgr, ConfigMgr 2007, sccm, SCCM 2007, SQL by Kenny Buntinx [MVP]

KB960065 – Updates are not deployed to some clients when you use WSUS or SUM to deploy updates in System Center Configuration Manager 2007 Service Pack 1
Sys Center Config Mnger 2007 AL EN-US

KB957255 – The wake-on-LAN (WOL) feature in System Center Configuration Manager 2007 Service Pack 1 wakes clients one hour earlier than expected
Sys Center Config Mnger 2007 AL  EN-US

KB960741 – The SMS_Executive service process crashes on a Configuration Manager 2007 Service Pack 1 site server when you use Intel WS-MAN Translator to provision computers that are equipped with AMT 3.2.1 chipsets
Sys Center Config Mnger 2007 AL EN-US

KB961105 – Error message when you try to import OSD drivers in System Center Configuration Manager 2007 Service Pack 1 systems: “The selected driver is not applicable to any supported platforms”
Sys Center Config Mnger 2007 AL EN-US


Hope it helps ,

Kenny Buntinx

App-V 4.5 Hotfix (KB959834) Package is released!

10:34 am in AppV, ConfigMgr, ConfigMgr 2007 by Kenny Buntinx [MVP]

The following issues are fixed in the Hotfix package:

  • Empty virtual directories may become inaccessible.
  • When you try to run ArcGIS as a virtual application, ArcGIS may stop responding on some systems.
  • When you use Symantec Endpoint Protection, and the Application and Device Control feature is enabled, virtual applications may not start and may generate the following error message: The application failed to initialize properly (0xc000007b)
  • When you try to run SmarTerm Essentials as a virtual application, SmarTerm Essentials may not start because it cannot validate its license.


get the new Hotfix  here:


Hope it helps ,

Kenny Buntinx

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

Error message when you install SQL Server 2005: “There was an unexpected failure during the setup wizard” – Error 1603.

1:17 pm in SQL by Kenny Buntinx [MVP]

Today I ran into some serious trouble at a customer . I had to install SQL server 2005 for a System Center Essentials installation.Every time I installed the SQL server it just would quit with a funny error : “There was an unexpected failure during the setup wizard”. What the hell ?

Doing some investigation , it seems to be a know bug when your sources aren’t coming from the original CD’s.If you are downloading them from the MVLS site , you will run into this issue one day .

This problem occurs because the folders that contain the files that are required during the installation of SQL Server 2005 do not have a correct layout.
This problem is most likely to occur if you start the SQL Server 2005 installation from a folder on a network share or on a hard disk when the folder was copied from the SQL Server 2005 installation CDs.

Solution:To work around this problem, set the folders in the correct layout for the SQL Server 2005 installation. The SQL Server 2005 installation uses the following two folders:

  • Servers
  • Tools

These two folders must be under the same level of a folder or the root folder of a drive. The names of these folders must be exactly Servers and Tools. The Servers folder contains all the files that are required to install major SQL Server 2005 components, such as database engine. The Tools folder contains tools components and Books Online for SQL Server 2005.Then try installing sql from the path\servers\setup.exe

Hope it helps ,

Kenny Buntinx

MMC updates for configuration manager (Software updates) Warning

10:13 am in AdminUi, ConfigMgr, ConfigMgr 2007, kb940848, MMC updates, prerequisite checker, sccm, SCCM 2007 by Kenny Buntinx [MVP]

Hi all,

Would you like to install Configmgr 2007 for once with a complete clean Pre-requisite checker? Do you want to eliminate all warnings?

Has this dreaded MMC updates for configuration manager warning been there for every sccm installation you do? Read on to learn, what is going on, and how to fix it.

The message is reportedly fixed by installing software update KB940848, which you can find here:

Issue 1: There are 2 server 2003 hotfixes with this kb article per processor architecture, the SP2 version is part of SP2 and hence applies to Windows Server 2003 SP1 machine. The SP3 version will be part of SP3 when it gets released, and hence applies to Windows Server 2003 SP2 machines.

Now even after you run this update and re-run the check, you still see this line in the prerequisite checker.



Additionally you’ll have the following line in your configmgrprereq.log:

Failed to connect to registry for KB940848 with 203.

What is going on here? Do I need to reboot? Nope, the reboot isn’t needed and doesn’t fix the issue. Let’s re-run the check and use process monitor to investigate what is going on.

If you re-run the check this is what process monitor shows you:


NAME NOT FOUND on HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB940848.

Odd, I installed the update just fine, and it does appear in add/remove programs, although it shows with a -V3 attached.

Let’s search the registry ourselves, and lo and behold the key indeed does not exist, yet a very similar key with -V3 attached does exist.



Turns out that the pre-requisite checker is looking in the wrong spot. Ok, now let’s fix this, I exported the registry to a .reg file, which you can find attached to this post. Modified it to write to KB940848 instead of KB940848-V3. I subsequently re-imported that reg file. and if we re-run the check after that we get this:



Notice the the MMC updates line is gone, problem fixed.