July 11 2012

Deploying printer drivers during SCCM task sequence

I recently had a requirement to pre-populate the Windows 7 Driver Store with some printer drivers so that non-admin users could add printers without the need to install drivers for this particular model. I utilized the PnPUtil command to do this during the SCCM Build and Capture Task Sequence which will copy and register the driver in the c:WindowsSystem32DriverStore directory on Windows 7.

Simply create a SCCM package that includes all of the driver files (.inf,.cat files etc) and then in your task sequence use a command line step to run “cmd.exe /c PnPutil.exe -i -a  C:_SMSTaskSequencePackagesxxxyyyyy*.inf” where xxxyyyyy is your SCCM package ID.  This will scan that whole folder and copy and inject all valid drivers into the OS.  I reference the C:_SMSTaskSequence directory because my task sequence is set to download first and then run.  Afterwards I found this article which does something similar but uses the %_SMSTS variable to provide the location – http://blog.coretech.dk/mip/personal-note-no-5-make-driver-available-for-none-admin-user/ – so if you run from the DP then this may be more useful.

 



----------------------------------------------------------------------------
I use a maximum of one Google Ad per post to help offset some of my blog hosting costs.

----------------------------------------------------------------------------

February 27 2012

Printer migration with SCCM and USMT 4 hardlinks

I recently had a situation where I needed to migrate network printers during Windows 7 refresh and Windows XP to Windows 7 upgrade scenarios when using USMT 4 hard link, also known as offline mode. According to the Microsoft Technet documentation (http://technet.microsoft.com/en-us/library/dd560792%28WS.10%29.aspx#BKMK_4) by design this is not possible. However I still needed to get it done.  I used a new XML file called Printers.xml (orginally from MyITForum but slightly modified by me – if you are using the link here then rename it to Printers.xml from Printers.xml.txt) and then added this to my task sequence capture and restore user data steps as shown in the screenshot below:

Once the computer is refreshed or upgraded, the network printers are now there! * Note that this will only migrate the printers, not the print drivers so you may see some printers are migrated and others are not… It’s still best to use logon scripts / GPO preferences to map printers in a consistant manner..