<

How to deploy PCs with SCCM

Published on
11,979 Points
5,679 Views
3 Endorsements
Last Modified:
Approved
Adrian McGarry
Information is at the heart of my experience in IT, with over 20 years as a Data Protection Officer.

1. Boot PC and press F10, select storage options and change the compatibility from “AHCI” to “IDE”, save and exit
2. Boot PC and press F12
3. Upon PXE display of searching for DHCP server, press Pause break to obtain MAC address
3. Open Configuration Manager, expand Operating System Deployment and select Computer association,
4. Select from the actions pane "Import computer information" which launches wizard,
5.a. Select "import single computer", click NEXT and enter PC name and MAC address, clicking NEXT, (Proceed to step 6)
5.b. Select "import multiple computers", click next and a select the CSV file with settings of PCs to import (must at least contain PC Name, MAC address)
6. Choose your "Collection", then click NEXT, CLOSE to complete the import.
7. Back on the PC, unpause the screen by pressing RETURN and wait for the PXE to find the boot image and Press F12 when prompted. NOTE: If it does not find the PXE boot images the first time reboot press F12 and wait for PXE to find boot image and press F12 again.
8. PXE boot process starts running through it's tasks NOTE: A screen will appear asking for the PC name, enter the name and click “Finish”
9. The GUI screen will continue and stop at a brief wizard asking you to choose a task sequence, choose the appropriate task sequence,click next and wait until completed (or do something more prodcutive instead).

Troubleshooting guide: Error “PXE boot aborted”
1. Refer to note on point 7;
2. Check you have input the MAC address correctly, as this is one of the security methods for accessing SCCM deployment
3. If you have just imported the computer into a collection and the PC is not booting into the PXE boot sequence, wait 10-15 mins. and try again.
4. Check the “site status” within SCCM, ensuring that the PXE service point is OK NOTE: If not OK, then restart the “Windows Deployment Services”. If any changes are made to the boot image, then you must update the distribution point by selecting the specific boot image and choose “update distribution point” from the task pane. Errors relating to PackageID; look up what the package is by looking in one of three places;
Usually boot image related issues so select the “boot images” node under OS deployment, if this is failing then it usually pertains to changes in the boot image, again select the specific boot image and choose “update distribution point” from the task pane.
It could be an issue with a Driver package; select the “Driver Packages” node and check the Package ID, to determine which driver is causing the problem; right click to problematic pack-age and select “properties”, select the “data Source” tab and check the driver is present in the source directory; Update the distribution point of the driver.
Check the O.S. install Package; select the “O.S. install Package” node and check the Package ID, to determine which O.S. is causing the problem; right click to problematic package and se-lect “properties”, select the “data Source” tab and check the source files are present in the source directory; Update the distribution point
3
Comment
0 Comments

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Join & Write a Comment

In response to a need for security and privacy, and to continue fostering an environment members can turn to for support, solutions, and education, Experts Exchange has created anonymous question capabilities. This new feature is available to our Pr…
Basic Overview of office 365 user portal

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month