You are browsing the archive for AdminUi.

SCCM 2007 : Best Practice importing drivers (Part 3) , Creating your search folders in SCCM.

7:54 am in AdminUi, ConfigMgr, ConfigMgr 2007, 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 . This section is Part 3 : Creating your search folders in SCCM.

clip_image004 In this example we are creating a search folder for reporting drivers of the “Lenovo R61”

First of all, Driver search folders are used combined with categories attached to your drivers. It is very important that you execute the task described in my previous post “Best Practice importing drivers Part 2″ correctly. If you assign these categories incorrectly , your driver search folder will display incorrect results.

The driver search folder is being used to easily fill up the driver package with the correct drivers for the correct hardware model.

I. In the ConfigMgr console, expand ”Site Database

II. Expand Computer Management in the left pane.

III. Expand the “Operating system deployment” à Click “Drivers

IV. Navigate to the Folder “[PC]”

V. Go to the folder “[Search Folders]” , right click on the folder and select “New search folder

clip_image006

VI. The following window appears and you must select in step 1 the field “Categories”

clip_image008

VII. In step 2 you click on the field “Categories” and select your value that suits your hardware model !

clip_image010

clip_image004[1] In this example we are creating a search folder for reporting drivers of the “Lenovo R61”

clip_image012

VIII. In step 3 you must select the checkbox “Search all folders under this feature”.

clip_image014

IX. In step 4 you must fill in your name that represents the correct hardware model. In this case it is “R61-8935CTO Drivers”. Click “OK” to close the window.

clip_image014[1]

X. When you go back to the search folder you just created , you will see that the drivers that have the R61-8935 category assigned are all there.

image

 

For the Part 4 , I will show you on how to import drivers from your search folder into your earlier created driver package !

 

Hope it helps,

 

Kenny Buntinx

SCCM 2007 : Best Practice importing drivers (Part 2) , importing a driver into the SCCM Database.

4:28 pm in AdminUi, ConfigMgr, ConfigMgr 2007, 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 . This section is Part 2 : Importing a driver into the SCCM Database.

Import a single Driver in the SCCM database

clip_image004 In this example we are importing drivers into the driver package for the “Lenovo R61”

 

First of all, download the latest drivers from the manufacturer’s website if new PC models are introduced.

It could be possible that some drivers are already present in the SCCM Database , so they will be denied to be imported again.

As this is no exact science and very difficult to predict when it happens, I will give you some guidelines in the next section.

We will now focus on drivers that weren’t known by the database before.

 

I. Extract the drivers and copy them into the “\\<Your Server>\Drivers\PC\_OriginalSources_\XP\<PC Model>” folder

II. Following procedure to import the drivers:

clip_image006

– Open your ConfigMgr Console

– Expand “Computer Management”

– Expand “Operating System Deployment”

– Expand “Drivers” in the left pane

– Expand “[PC]” in the left pane

– Right click on “Drivers” and Click on Import.

III. In the “Source Folder” , type in the UNC path to the folder where you have extracted your drivers for a specific type of hardware (e.a video, audio ,etc ).

clip_image008

IV. Click next when source folder is specified.

V. The Wizard will propose one or more drivers, select those you need and click “Categories

clip_image010

VI. Add a new Category if it didn’t yet existed, add the driver to the category. Specify the category name for drivers, when finished click ok.

clip_image002[1]you MUST add the hardware type and the driver category if they do not exist already ! We will use this later for the ease of finding the drivers back thru search folders.

clip_image012

VII. Press “OK” and the following screen will appear

clip_image014

VIII. Click Next and theAdd driver to driver package” will appear. All the drivers will be imported later into the specific created driver package for the specified hardware model.

clip_image016

IX. Click Next and the “Add driver to boot images” will appear.

clip_image018

X. Click Next.

clip_image020

XI. Click “Next” and “Close” the wizard if the import was successfully ended .

clip_image022

This process will be needed for every driver that needs to be integrated in the OS deployment for a specific hardware model. This can be a time consuming task at the beginning of the deployment configuration. If an update on a driver is needed, it is the specific driver that can be easily located and updated on a central place in SCCM .

Be careful when uploading drivers , because Multiple Driver Delete  does NOT work .I think they forget to add this in the initial release ! However there is a script on MyITForum to multi delete drivers.

 

How to handle or import a duplicate or existing driver in the SCCM Database ?

clip_image004[1] In this example we try to import a duplicate(existing) driver into the SCCM driver database for the “Lenovo R61”

First of all, when importing the latest drivers from the manufacturer’s website when new PC models are introduced, it could happen that the driver is already in the SCCM driver database because of other hardware models using the same driver. When this is the case, they will be denied to be imported again.

As this is no exact science and very difficult to predict when it happens, I will give you some guidelines in this section.

I. When it happens, it shows you the following window below.

clip_image024

II. If you look closely ,it will tell you “The selected driver has already been imported at this site.”.This means we will have to look now in the database where it is.

III. By default you will not see the inf files in the view at the SCCM console. To perform this action , follow the steps below.

IV. Expand “Operating System Deployment”

V. Expand “Drivers” in the left pane

VI. Expand “[PC]” in the left pane

VII. Right click on “[PC]” and Click on “View” -> “Add/Remove columns..”.

clip_image026

VIII. In the next pane , remove the existing “Displayed columns” and add the new ones as shown below.

clip_image028

IX. Click “OK” to continue. You will now have the following view :

clip_image030

X. Now you could use the “Look For” field to allocate your driver in the database. If we look closer into the error that we earlier had , we could look for the inf file , in this example ( rimsptsk.inf )

clip_image031

XI. Now you fill in the “Look For” field the “rimsptsk.inf” and click “search”. The following results will show.

clip_image033

XII. Select the results and right click “Categories”

clip_image035

XIII. Add the “Categories” that refers to your hardware model and you are done.

 

For the Part 3 , I will show you on how to create a search folder to find your drivers back into the SCCM database !

 

Hope it Helps ,

 

Kenny Buntinx

Keyboard Layout values for use in Task Sequences & Collection Variables

9:13 am in AdminUi, ConfigMgr, ConfigMgr 2007, OSD, sccm, SCCM 2007, SMS, Sms 2003 by Kenny Buntinx [MVP]

I just needed to find a list with Keyboard variables to customize my Windows XP Build in SCCM. It could become handy for people needing them when building international images.
[“Keyboard Layout”]
0000041C = “Albanian”
00000423 = “Belarusian”
00000813 = “Belgian Dutch”
0000080C = “Belgian French”
00000416 = “Brazilian (ABNT)”
00000402 = “Bulgarian”
00010402 = “Bulgarian Latin”
00001009 = “Canadian English (Multilingual)”
00000C0C = “Canadian French”
00010C0C = “Canadian French (Multilingual)”
0000041a = “Croatian”
00000405 = “Czech”
00010405 = “Czech (QWERTY)”
00000406 = “Danish”
00000413 = “Dutch”
00000425 = “Estonian”
0000040B = “Finnish”
0000040C = “French”
00000407 = “German”
00010407 = “German (IBM)”
00000408 = “Greek”
00050408 = “Greek Latin”
00010408 = “Greek (220)”
00030408 = “Greek (220) Latin”
00020408 = “Greek (319)”
00040408 = “Greek (319) Latin”
0000040E = “Hungarian”
0001040E = “Hungarian 101-key”
0000040F = “Icelandic”
00001809 = “Irish”
00000410 = “Italian”
00010410 = “Italian (142)”
0000080A = “Latin American”
00000426 = “Latvian”
00010426 = “Latvian (QWERTY)”
00000427 = “Lithuanian”
00000414 = “Norwegian”
00000415 = “Polish (Programmers)”
00010415 = “Polish (214)”
00000816 = “Portuguese”
00000418 = “Romanian”
00000419 = “Russian”
00010419 = “Russian (Typewriter)”
00000C1A = “Serbian Cyrillic”
00010C1A = “Serbian Latin”
0000041B = “Slovak”
0001041B = “Slovak (QWERTY)”
00000424 = “Slovenian”
0000040A = “Spanish”
0001040A = “Spanish variation”
0000041D = “Swedish”
0000100C = “Swiss French”
00000807 = “Swiss German”
0001041F = “Turkish F”
0000041F = “Turkish Q”
00000422 = “Ukrainian”
00000809 = “United Kingdom”
00000409 = “US”
00010409 = “US-Dvorak”
00030409 = “US-Dvorak for left hand”
00040409 = “US-Dvorak for right hand”
00020409 = “US-International”

Hope it helps ,

 

Kenny Buntinx

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”.

clip_image006.

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

clip_image008

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” !

clip_image010

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”.

clip_image012

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.

clip_image014

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 !

clip_image016

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

clip_image018

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

OUR SYMPTONS:

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
point.

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 !

 

**************************smpmgr.log***************************************

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  

**************************smpmgr.log***************************************

 

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

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. http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3001200&SiteID=17 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

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:

http://support.microsoft.com/default.aspx/kb/940848

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.

mmcupdatewarning01

 

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:

mmcupdatewarning01.5

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.

mmcupdatewarning02

 

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:

mmcupdatewarning05

 

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

SCCM 2007 : Branch Distribution Point option is "grayed" out on the New Site Roles Wizard

1:02 pm in AdminUi, ConfigMgr, ConfigMgr 2007, sccm, SCCM 2007 by Kenny Buntinx [MVP]

When adding a new Distribution Point using the “New Site Roles” wizard; sometimes the “Branch Distribution Point” option is not available (grayed out) and the only option you have is to create a standard Distribution Point. Well, there can several reasons to this. Most times because the computer on which you are trying to install the Branch Distribution on, has no ConfigMgr Agent Host installed which is a requirement for BDP’s.

However, if your ConfigMgr site is configured in native mode, and the computer on which you are trying to install the BDP is configured for Internet Based Client Management (IBCM); the wizard will prevent you from installing a BDP on the computer, and as a result; the “Branch Distribution Point” option will not be available (grayed out).

The ConfigMgr documentation states that BDP’s are not supported on the internet, but also currently states that ConfigMgr will not prevent us from installation a BDP on a IBCM-enabled client…. But that is not the case; the wizard will actually prevent us from doing so :-)

You can read more about this issue and how to workaround it on Carol Bailey’s blog post: http://blogs.technet.com/wemd_ua_-_sms_writing_team/archive/2008/07/23/cannot-select-option-for-branch-distribution-point-in-a-native-mode-site.aspx

Hope it helps ,

Kenny Buntinx

Infrastructure Planning and Design Guides for App-V & SCCM

5:02 pm in AdminUi, AppV, ConfigMgr, ConfigMgr 2007, sccm, SCCM 2007 by Kenny Buntinx [MVP]

Two new IPD guides has been published:

  1. Microsoft System Center Configuration Manager 2007 SP1 with R2
  2. Microsoft Application Virtualization 4.5

Download them from the following link.

Hope it helps

Kenny Buntinx