SCCM: How to extract drivers from an existing machine for later OSD

Michael published a quick-cheat for that. You can extract drivers to a folder, import them to SCCM or MDT and deploy back to bare-metal machines.

 

powershell command is:

Export-WindowsDriver -Destination “C:\Drivers\$((Get-WmiObject -Class win32_computersystem).Model)” -Online

 

more details here: http://deploymentbunny.com/2016/02/26/powershell-is-king-export-drivers-from-windows/

SCCM: OSD on Lenovo M83

I downloaded a driver pack for M83 model from Lenovo website , imported it in SCCM and tried to deploy my Win 7 image.

After driver installation the process stopped on the first boot with error:

Driver ipf63x64.inf is missing or corrupted

It looks like a known issue for Lenovo community http://forums.lenovo.com/t5/Enterprise-Management-IT/Introducing-ThinkPad-Driver-Packs-for-SCCM/td-p/800691/page/9

 

Resolution:  I removed all FCoE-related components (net, SCSI and system classes) from my driver pack (for that you need to find all drivers under “Drivers” node, right-click Edit-Package and clear a checkbox corresponding to your package. Updated the package on DPs. I actually left just one network friver from multitude provided by Lenovo in the driver pack.

After that installation passed successfully.

 

As a side note – the pack from Lenovo did not impress me too much – it looks like manufacturer put all available drivers there and did not bother to test it.

Driver Grabber in its turn missed some drivers (for example Lenovo Application Integration driver – LBAI.sys).

SCCM 2012: Preparing XP gold image

1. Prepare VM (on VMWare Workstation 8.0)

– VM type: Windows XP

– HDD: SCSI (check .vmdk file to verify SCSI type is set to BusLogic)

– Network adapter E1000 ( enter ethernetN.virtualDev = "e1000"  in VM configuration (.vmx) file. N is the adapter index, if there is only one adapter it will be 0)

2. Prepare SCCM boot image.

– Extract SCSI drivers from wimndows.iso in VMWare Workstation installation folder

– Add the drivers to 32-bit image

3. Prepare Driver package

– Create n empty Driver Package

– Add SCSI drivers to the package

– Download drivers from Intel site (Prowin32.exe)  http://downloadcenter.intel.com/detail_desc.aspx?agr=Y&DwnldID=18717

– Extract drivers to a temp folder and import them to the prepared Driver Package. Note: (some drivers are for Windows 8 and will give you an error).

4. Prepare Deployment Tool Package

– Extract \Support\Tools\Deploy.cab  to a tem folder

-Create a package using the temp folder as a source (we do not need any Program)

5. Create a package containing Software Updates for XP and Deploy it to a collection containing the reference machine (otherwise “Install Updates” step won’t work

6. Prepare Task Sequence:

– Add a TS variable OSDDiskpartBiosCompatibilityMode=TRUE to workaround Uberbug issue

-Add Apply Driver Package Step to apply VMWare drivers for XP

Note: If you use a Hyper-V based machine you do not need any additional drivers (but still need Uberbug step and a package for Deployment tools)

Note. As soon as the image is captured remove the .wim file from the destination folder. SCCM cannot manage situation when the destination file is already exists and the TS will fail if you will decide to recapture the image.

Driver Packs for SCCM OSD

Placeholder for Driver Pack collections for SCCM OSD

Lenovo: Lenovo forum

Dell: Dell Enterprise Client Wiki

HP: Deploymentresearch Blog

Speed up graphics in Windows Servers running on VMWare platform

Found an article explaining procedure of speeding up graphics on VMWare-based VMs (in addition to VMWare Tools installation). The matter in face even with installed VMWare tools the machines are mot using WDDM driver. Bust they can be installed manually from C:\Program Files\Common Files\VMware\Drivers\wddm_video. The drivers can also be injected in WinPE images.

Windows 7: How to allow users to install printers if they are not Administrators

Problem: If users are not Local Administrators they cannot install Printer (and other) drivers to their machines.

Resolution:

There are two main approaches:

1. Pre-stage drivers for users using ConfigMgr or PNPUTIL as described here: http://blog.coretech.dk/mip/personal-note-no-5-make-driver-available-for-none-admin-user/ and here: http://technet.microsoft.com/en-us/library/cc772036.aspx

2. Or allow installation of a specific hardware class for limited users as described here: http://technet.microsoft.com/en-us/library/cc725772(v=ws.10).aspx

3. Use GPO as described here: http://techibee.com/group-policies/allow-normaldomain-users-to-add-network-printers-in-windows-7/457 . Just in case the link will be dead – it is under Computer Configuration – Administrative Templates – Printers – Point and Print Restriction