This post will outline driver package creation, management, and best practices for System Center Configuration Manager (SCCM / ConfigMgr). The steps outlined in this post will ensure minimal driver management in SCCM, while ensuring the end device receives the proper drivers during imaging.
Staging and Imaging the New Device
The first step in the process is to get the new device able to image with the environment’s gold image. You will have to note that it may be necessary to inject the network drivers into your Windows Pre-Installation Environment (WinPE) boot image. If the device fails to load the WinPE environment it is either the network or storage drivers are not available.
Pick the below scenario that matches your environment:
- The Task Sequence deployed to unknown computers and the local administrator password is set
- Begin imaging the device
- The Task Sequence deployed to unknown computer but the local administrator password is not enabled
- Copy the task sequence to enable the local administrator account, deploy the task sequence and start imaging the device
- No task sequence is deployed to unknown computers but the local administrator password is set
- Import the device and add it to the proper collection and begin imaging
- No task sequence is deployed to unknown computers but the local administrator password is not enabled
- Copy the task sequence, enable the local administrator account, deploy the task sequence, import the device, and begin imaging the device
To import a device into SCCM follow the steps outlined in the below link:
If network drivers are in the Operating System media that task sequence will complete successfully. If the device does not receive a network driver it will fail, and you must logon as the local administrator.