Sam's IT Knowledgebase

If you get the error code  87D00267 in a task sequence when deploying an Operating System it  basically means the machine is unable to talk to the DHCP server. From a bit of investigation it  seems that some machines with SSD's actually boot up into the task sequence quicker than it  gets an IP Address! The get around this problem you need to put some pauses in the task  sequence.  The best way is to put the pause in the task sequence just before the point where it  fails. There is  some further reading into this issue below, the sites credited with links.  Part 1 Source: http://ericsccm2012.blogspot.com.au/2013/04/applications-fail-to-install-on-ssd.html Applications Fail to Install on SSD Drives. We received several of the new Dell Latitude 6430U models with SSD drives.  Very nice laptops in a small case.  Easily found drivers for them and loaded into SCCM.  Started the task sequence on one and all look...

Ref:https://technet.microsoft.com/en-us/library/dd799289(v=WS.10).aspx Add Device Drivers on an Offline Windows PE Image 2 out of 2 rated this helpful  -  Rate this topic Published: October 22, 2009 Updated: October 22, 2009 Applies To: Windows 7, Windows Server 2008 R2 Note This content applies to Windows 7. For Windows 8 content, see  Windows Deployment with the Windows ADK . The following procedure demonstrates how to use the Deployment Image Servicing and Management (DISM) tool to add a device driver (.inf) to an offline Windows® PE image. Before you can run a DISM command, you must first mount the Windows PE image. To add a device driver to an offline Windows PE image Mount the base image by using the DISM tool to a local Windows PE directory. For example: Dism /Mount-WIM /WimFile:c:\winpe_x86\winpe.wim /index:1 /MountDir:c:\winpe_x86\mount Add the .inf file to the base image by using the  dism...