Make changes to WDS/SCCM boot file to run script before Task Sequence:

  I recently had a customer who couldn't re image machines because of some hidden partition stuff on manufacture preloaded machines. It actually turned out that a couple of files needed to be removed prior to running the TS. So we added a  script to be run prior to the launch of the TS, to get rid of these files. Its not like its a big secret, how you do this, as it is in the WinPE.chm but I thought just make small description of the steps anyhow. 1. MountRW SCCM boot.wim with ImageX - ImageX /MountRW C:\boot.wim 1 C:\mount [...]

By | 2008-07-14T15:44:32+00:00 July 14th, 2008|OS Deployment|1 Comment

Using BDD/MDT DriverPaths1 in SCCM

  I have always loved the DriverPaths1=\\server\path\%model% part of BDD\MDT because it enabled you to have all your model specific drivers in a corresponding folder rather than a repository. SCCM pretty much forces you to use repositories.... I know that you can create different driver packages and categorize your drivers, thereby  enabling you to only use specific drivers. However, you then have to create a bunch of IF statements, to make this a reality.   The BDD/MDT way is to add the "DriverPaths1=\server\path\%model%"  to your CustomSettings.ini, and then create a folder structure looking something like this: Each folder would then [...]

By | 2008-07-12T15:41:43+00:00 July 12th, 2008|Hardware & Drivers|5 Comments

Keep Test Computers in Test collection.

  When testing your different deployment scenarios eg. Task Sequences, you normally create a Test collection, and associate a test PC to that collection. Now ones the PC has successfully carried out the steps in the TS, you might want to change some thing, and then run the TS again. You now find that the test PC does not work any more, and you have to associate the PC all over again. Why does this happen! The PC receives a new GUID during deployment, and therefore, the original associated PC will become obsolete. The PC (obviously still with the same [...]

Storage drivers in XP image

When capturing an image, it's always a good idea to add needed storage drivers to the [SysprepMassStorage] section of your Sysprep.inf before capturing. The two most common Mass Storage Drivers are the : Intel Matrix Storage Manager Driver (IaStore.sys) and Dell SAS 5x and SAS 6x Controller Driver (symmpi.sys)   In Sysprep.inf add the following lines... ================insert into sysprep.inf======================== [Sysprep] BuildMassStorageSection = No [SysprepMassStorage] ;Dell SAS 5x and SAS 6x Controller Driver PCI\VEN_1000&DEV_0054&SUBSYS_1F041028=C:\drivers\SAS\symmpi.INF PCI\VEN_1000&DEV_0054&SUBSYS_1F061028=C:\drivers\SAS\symmpi.INF PCI\VEN_1000&DEV_0054&SUBSYS_1F071028=C:\drivers\SAS\symmpi.INF PCI\VEN_1000&DEV_0054&SUBSYS_1F081028=C:\drivers\SAS\symmpi.INF PCI\VEN_1000&DEV_0054&SUBSYS_1F091028=C:\drivers\SAS\symmpi.INF PCI\VEN_1000&DEV_0058&SUBSYS_1F0E1028=C:\drivers\SAS\symmpi.INF PCI\VEN_1000&DEV_0058&SUBSYS_1F0F1028=C:\drivers\SAS\symmpi.INF PCI\VEN_1000&DEV_0058&SUBSYS_1F101028=C:\drivers\SAS\symmpi.INF PCI\VEN_1000&DEV_0058&SUBSYS_021D1028=C:\drivers\SAS\symmpi.INF ;Intel Matrix Storage Manager driver PCI\VEN_8086&DEV_2681&CC_0106=C:\drivers\sata\IAAHCI.INF PCI\VEN_8086&DEV_27C1&CC_0106=C:\drivers\sata\IAAHCI.INF PCI\VEN_8086&DEV_27C5&CC_0106=C:\drivers\sata\IAAHCI.INF PCI\VEN_8086&DEV_2821&CC_0106=C:\drivers\sata\IAAHCI.INF PCI\VEN_8086&DEV_2829&CC_0106=C:\drivers\sata\IAAHCI.INF PCI\VEN_8086&DEV_2922&CC_0106=C:\drivers\sata\IAAHCI.INF PCI\VEN_8086&DEV_2929&CC_0106=C:\drivers\sata\IAAHCI.INF PCI\VEN_8086&DEV_3A22&CC_0106=C:\drivers\sata\IAAHCI.INF PCI\VEN_8086&DEV_2682&CC_0104=C:\drivers\sata\iaStor.INF PCI\VEN_8086&DEV_27C3&CC_0104=C:\drivers\sata\iaStor.INF PCI\VEN_8086&DEV_27C6&CC_0104=C:\drivers\sata\iaStor.INF PCI\VEN_8086&DEV_2822&CC_0104=C:\drivers\sata\iaStor.INF PCI\VEN_8086&DEV_282A&CC_0104=C:\drivers\sata\iaStor.INF ======================================================= [...]

By | 2008-07-08T15:08:28+00:00 July 8th, 2008|Hardware & Drivers|1 Comment

Unpack Intel drivers

  I recently spent more time that I should have, trying to unpack both the Intel NIC drivers executable and the Mass Storage driver executable. For some reason it is not easy to find the correct switches to use for this action, and when you find them it can be somewhat difficult to figure out exactly how they work. INTEL Network drivers: Download the newest NIC drivers from HERE You now find yourself with and pro2kxp_xxxx.exe file who wants to install something on you pc (which you properly do not want). So in order to only extract the files you [...]

By | 2008-07-01T14:31:51+00:00 July 1st, 2008|Hardware & Drivers|2 Comments