You are browsing the archive for 2009 March.

SCCM 2007 : Finding the right mass storage drivers for IBM Blade HS20 (8843) & HS21 (8853)

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

I have spend a few days an building a Windows 2003 R2 SP2 rig for deployment thru SCCM on IBM Blade center HS20 (8843) & HS21 (8853).

The HS21 blade went very smooth , but it was a fight to get the HS20 going.Even after downloading the mass storage drivers from the IBM Website it would not work !

Then I have used drivermax.exe ( Freeware tool) to list and export the current driver . And guess what ? Yes , it was not the same driver , nor version .

Below you will find some screenshots on witch driver to use and wath to select into your task sequence .

HS21 :

SNAG-0186  SNAG-0187

 

HS20 :

SNAG-0188 SNAG-0189

Hope it Helps ,

 

Kenny Buntinx

by

SCUG Session Getting started with Out of band service management

12:22 am in ConfigMgr, ConfigMgr 2007, events, SCCM 2007 by

SCUG Session Getting started with Out of band service management

 

Date: 02/04/09

Time: 18u30

Place: Microsoft Belgium

Speaker: Kim Oppalfens

 
 
Abstract: Configuration Manager 2007 SP1 added this brand new feature called
out of band service management. In my opinion a worth-while addition, yet it
competes with the NAP feature for the position of least used SCCM 2007 feature,
whereas it deserves a place up there with the feature hotshots like software
distribution and os deployment. The main reason it isn’t up there in the
popular feature list is most likely because the provisioning of systems to
support out of band service management can be a little bit tricky. During this
session we’ll show you how to get provisioning going. We’ll talk about the 3
different ways of provisioning, and show you the easiest way to get going. If
you have ConfigMgr 2007 SP1 running and have machines with Intel Vpro
capabilities then you can’t miss this session. Unless the following features
are not apealing to you at all:
 

  • Powering on/off one or many
    computers.
  • Restarting a nonfunctioning
    computer or booting from a locally connected device or known good boot
    image file.
  • Re-imaging a computer by
    booting from a boot image file that is located on the network or by using
    a PXE server.
  • Reconfiguring the BIOS settings
    on a selected computer.
  • Booting to a command-based
    operating system to run commands, repair utilities, or diagnostic
    applications.
  • Configuring scheduled software
    update deployments and advertisements to wake up computers prior to
    running.

 

Registration

SCCM 2007 : Best Practice importing drivers (Part 4) , adding drivers to your SCCM Driver Package.

7:49 am in 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 4 : adding drivers to your SCCM Driver Package.

clip_image002 In this example we will add the drivers of the “Lenovo R61”model into a driver package

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 “[PC]” folder

V. Expand the “[Search Folders]” and select your hardware model search folder .

VI. Select all drivers , right click and select “Add or Remove Drivers to Packages”

clip_image004

 

For the Part 5 , I will show you on how to integrate your drivers from your earlier created driver package into task -sequences based on WMI queries !

 

Hope it helps,

 

Kenny Buntinx

SCCM OSD : Windows XP SP3 and Blue screen during installation of the Setup Windows & ConfigMgr Client step !

5:54 pm in ConfigMgr, ConfigMgr 2007, OSD, sccm, SCCM 2007 by Kenny Buntinx [MVP]

I had some issues today after installing Windows XP SP3 via the SCCM Tasksequence .The task sequence aborts just after the step “Setup Windows & ConfigMgr Client” with :

Faulting application winlogon.exe, version 0.0.0.0, faulting module OSDGINA.DLL, version 0.0.0.0, fault address 0x0001a30a.

After investigation , it seems that the Windows XP SP3 is working well but the SCCM Client is not installed correctly as the icons are not showing in the control panel.

I resolved the issue by :.

In the Client install folder there were numerous files not digital assigned or  with no bytes in size.

1.) windowsupdateagent30-x86.exe = No digital signature
2.) WindowsXP-KB923845-x86-ENU.exe = No digital signature
3.) MSRDCOOB_X86.EXE = No digital signature
4.) wmirdist.msi = 0 bytes in size

It seemed that my install source became corrupted for some reason . I replaced the above mentioned files and now it works !

Hope it helps ,

Kenny Buntinx

TechDays 2009 : Come out and speak to us !

7:32 pm in Uncategorized by Kenny Buntinx [MVP]

Join us on March 10-12, 09 for the most important ITPro & Developer event organized by Microsoft in Belux.

The Belgian System center User Group will be there the entire time.

We will be wearing shirts with our logo printed on , so feel free to pull us over and ask us any questions you may have !

So see you there !

Kenny Buntinx

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