You are browsing the archive for 2009 February.

SCCM 2007 : Best Practice importing drivers (Part 1) , creating a driver Package.

4:26 pm in AdminUi, ConfigMgr, ConfigMgr 2007, Drivers, OSD, sccm, SCCM 2007 by Kenny Buntinx [MVP]

Did you ever wonder what would be the required best practice steps on how to import new drivers in System Center Configuration Manager (SCCM), when building a new hardware model. Well I try to explain the steps to accomplish this in a few sections .

First a word about integrating drivers in SCCM


These instructions describes the process of integrating the drivers in to the OS deployment functionality. The approach for driver integration into OS deployment functionality:

– All drivers are integrated into driver packages per hardware model.

– Drivers Packages are created in the corresponding folder for each hardware model on the SCCM box.For example : “\\<Your Server>\Drivers\PC\SCCM_Driver_Packages\XP\<PC Model>”

– Drive source are created in the corresponding folder for each hardware model on the SCCM box.For example : “\\<Your Server>\Drivers\PC\_OriginalSources_\XP\<PC Model>”

Categorize the drivers needed for deployment

“Nice” drivers

Drivers that can be installed/imported using an INF file.

“Nice” drivers list for deployment:

These drivers are needed for OS deployment and are imported into one driver package per hardware type in SCCM for further use in the OS deployment task sequencer.

“Bad” drivers

Drivers that must be “installed” (setup.exe). This could be a Bluetooth driver, finger print reader software or even DVD software that is specific to a particular model type. Generally, this type of drivers are also called “Hardware based applications”.

A small example is the 4 in 1 Card reader drivers for Lenovo laptop R61.A software package will be created for deployment and used for further use in the OS deployment task sequencer.


Create a Driver Package for your specific hardware model (for nice drivers)

clip_image004 In this example we are creating a driver package for a “Lenovo R61”

I. Open your “Windows Explorer”

II. Go to “\\<Your server>\Drivers\PC\SCCM_Driver_Packages\XP\”

III. Create a sub-folder that is representing your hardware model , in this case “R61–8935CTO”.


IV. In the ConfigMgr console, expand ”Site Database

V. Expand Computer Management in the left pane.

VI. expand the “Operating system deployment” and Click “Driver Packages

VII. Navigate to the sub-folder [PC]

VIII. Right click on the “[PC]” folder and select “New” -> “Driver Package


IX. New Driver Package wizard starts:

· Give your new driver package a unique name that represents your hardware model & version.

· Fill out the commenting window as shown below , but adapt to your HW model.

· In the Driver Package Source , you must fill in the UNC path to your earlier created folder on the SCCM primary server. The UNC path in this case will be “\\<your Server>\Drivers\PC\SCCM Driver_Packages\XP\R61-8935CTO”.

· Note that this is not the drivers source but the working directory for Configuration Manager when to add drivers to the “Driver Package” !


X. Click Ok

XI. Expand the “Operating system deployment” and expand “Driver Packages” .Expand the driver package you just created for OS deployment and select “Distribution Points”.


XII. Right click the “Distribution Points” folder. In the right click context menu you will see “New Distribution Point”. The following screen will appear and select “Next” on the Welcome screen.


XIII. Select the appropriate Distribution Point(s) where you want your package to be copied and click “Next” , but NEVER select the SMSPXEIMAGE$ distribution point !


XIV. Click “Close” on “completion” page.


XV. Your SCCM driver package is now ready to be integrated with imported drivers from the database.


For the Part 2 , I will show you on how Import a Single driver into the SCCM database !


Hope it helps ,


Kenny Buntinx.

SCCM 2007 : Changing your name/description of your secondary sites

10:27 am in AdminUi, ConfigMgr, ConfigMgr 2007, sccm, SCCM 2007 by Kenny Buntinx [MVP]

Today I ran into a weird customer question.They wanted to change the description on their secondary sites.

After some investigation I found a way of doing this without having to reinstall the entire secondary sites.

To do this , you must : 

  1. Stop the SMS executive service.
  2. Open the C:\Program Files\SCCM\Inboxes\SiteCtrl.Box\sitectrl.cto file.
  3. At the top of the file , you find your sitecode and below that you’ll find the site desciption.
  4. Change the name and save the file.
  5. Restart the SMS Exec service.
  6. The site name/Description has changed.

However , this method is NOT supported by Microsoft !

This posting is provided AS IS with no warranties ! Test it first into a TEST environment !

Hope it Helps ,

Kenny Buntinx

SCCM 2007 : State Migration Point Bug , Does not clean up the old SMP- USMT Records in "Computer Association".

11:37 am in AdminUi, ConfigMgr, ConfigMgr 2007, migration, sccm, SCCM 2007, SMP by Kenny Buntinx [MVP]

A few weeks ago I ran into some serious trouble at a customer.The state migration point at a secondary site ran full. At first site this wasn’t really an issue , as we expected to go over the default values that where configured in the state migration point properties as the site contained 800 users . The pic below confirmed the settings , so we altered it to the new settings .

SNAG-0182 SNAG-0183

Problem solved we thought , nothing was thru …

As soon as we did one extra , the same problem reoccurred. Strange ?! What the Hell ?!

After doing some futher investigation , it seemed that our older records that should have been purged after 14 days , where still into the console as shown below , with also the content still available on disk .

ComputerAssociation - not deleted


Consider our scenario:
* On a site server that is running Microsoft System Center Configuration
Manager 2007 Service Pack 1, you configure a state migration point role.
* On the state migration point, you capture several user states and then
restore them.
* You wait for state store deletion to occur on the state migration

In this scenario, you notice that only two expired user state stores are
deleted. Additionally, the Smpmgr.log file indicates that the first user
state store deletion was successful but that the second deletion failed,
and you receive the following error message:

CheckAndDeleteSMPStores failed with error code (80004005)


Looking in the smpisapi.log , everything looked ok :

========== BEGIN: smpisapi.log ========== 

Query string to parse: ‘op=healthcheck’.       

Creating state store – E:\SOURCES\USMT\SMPSTOREE_B2DE4AB0$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473.    Statestore – E:\SOURCES\USMT\SMPSTOREE_B2DE4AB0$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473 exists.

Returning status “200 OK”

========== END: smpisapi.log ==========


After some further investigation in the smpmgr.log .It is really the message that he is not able to delete the stale records!

It does not perform the cleanup as scheduled into the SMP settings. We have specified 31 Days for the cleanup to happen and the folders with the content are still there !



Checking store for cleanup of failed or stale state stores…  

Cleanup of store “E:\SOURCES\USMT\SMPSTOREE_B2DE4AB0$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473″ failed with errorcode (80004005)

CheckAndDeleteSMPStores failed with error code (80004005)

Failed to cleanup stores. (0x00000000) 

Secondly we get the Http error 500 back into the log file , so it seems that both are related;

Completed availability check on local machine  



What is causing this :

When the state migration point module deletes the first in a series of expired user state stores in a loop, the module does not correctly
initialize the computer-name length for the next iteration of the loop. Therefore, after the second expired user state store is deleted, you
receive the error message, and additonal user state store deletions are aborted.

What is the solution :

After having a long session with Microsoft Premier Support we came to a non public hotfix solution , but that has been publicly made available from the 26th of Januari !

To apply this hotfix, you must have System Center Configuration Manager 2007 Service Pack 1 installed.

This hotfix KB961269 does not replace any other hotfixes!

The hotfix wil replace the  Smpmgr.dll  with file version 4.0.6221.1147  and will do a site reset after .


Hope it helps ,

Kenny Buntinx

Sccm presentation at Microsoft Techdays

1:32 pm in ConfigMgr, ConfigMgr 2007, events, personal, sccm, SCCM 2007, techdays, Training by Kenny Buntinx [MVP]

Hi All,

For the third year in a row I will be delivering a presentation at the Microsoft Techdays in Belgium. This years presentation will resolve about ConfigMgr aka SCCM 2007 R2 tasksequences, and what you can do with them. I will cover as much of the in’s and out’s of Tasksequences as possible, explain what has changed since R2, and point out any pitfalls whenever appropriate.

The techdays promises to be another top-conference, with confirmed speakers like Steve Riley (Security Expert), Scott Schnoll (Exchange Expert), Ronald Beekeleaar (Virtualisation & isa expert), and Jeff Wettlaufer from the ConfigMgr product team. If you are interested in this blog, then the presence of Jeff should be a neat surprise. Afaik, this is the first time that the event will have someone from the SCCM product team to present.

In an economic climate where travel & expenses are tough to get, the Microsoft Techdays team did an astonishing job in getting a great line-up. I am definitely looking forward to it.

So why should you attend?

  • Top speaker line-up of knowledgeable people in the subject area
  • 6-month free technet plus subscription if you register as one of the first 250 participants as of today.
  • I will be there the entire time, feel free to pull me over and ask me any questions you may have (This is the cheapest consultancy you’ll ever get out of me :-)
  • In days where training budgets are tight, going to the larger conferences like Teched and MMS might be tough, the Techdays can provide for a cost-effective alternative that provides great value for money.