Hi,

I have setup a virtual SCCM 2007 SP2 lab to test OSD and PXE booting but when i boot a bare metal client it loads the respective boot image, gets to the Config Manager splash screen (WinPE 3), a message says "Windows is starting" followed by "Preparing Network Connections" then the client reboots.

I initially thought this to be a network driver missing in the boot image so i injected the correct driver but i still have the same problem.

I enabled command support on the boot image and ran an ipconfig/all to ensure the NIC was obtaining an IP address which it was and it lists the NIC as the correct model.

Can anyone offer any advice as to what the issue may be?

Been pulling my hair out for a couple days now :(

Thanks

well after it gets the ip can you ping the FQDN of the configmgr server ?

and keeping the command prompt open what does the smsts.log file reveal about the problem ?

Troubleshooting PXE and OSD Deployment problems
Troubleshooting with the help of SMSTS.LOG and F8

I can ping the SCCM server fine.

JUst had a look at the smsts log file and i think it may be a problem with the SCCM client package not being present in the SMSPKGE$ share. 

Am i correct in thinking that the only package that should be on the PXE service point is the boot images and the other packages should only be on the DP?

yes the boot image is the only image that needs to be on your standard dp's as well as the PXE service point dp.-

I thought the boot images didnt need to be copied to the DPs, it was only required on the PXE SPs?

Anyways, in addition to the missing SCCM client package i didnt have my advertisement configured for remote DPs.  I have corrected both these issues and now trying again.

Still failing!

Heres an extract of the smsts.log

Adding \\sccm.domain.local\SMSPKGEIMAGES$\SMSPKG\DER00010 to remote DP list

Shuffling Remote DP list

Attempting to connect to \\sccm.domain.local\SMSPKGEIMAGES$\SMSPKG\DER00010

CCM::Utility::Filesystem::Directory::Exists

Failed to verify existence of \\sccm.domain.local\SMSPKGEIMAGES$\SMSPKG\DER00010

Content location request for DER00010:2 failed

Any ideas?

• Edited by aaronmcl Tuesday, April 10, 2012 11:00 AM

Still failing!

Heres an extract of the smsts.log

Adding \\sccm.domain.local\SMSPKGEIMAGES$\SMSPKG\DER00010 to remote DP list

Shuffling Remote DP list

Attempting to connect to \\sccm.domain.local\SMSPKGEIMAGES$\SMSPKG\DER00010

CCM::Utility::Filesystem::Directory::Exists

Failed to verify existence of \\sccm.domain.local\SMSPKGEIMAGES$\SMSPKG\DER00010

Content location request for DER00010:2 failed

Any ideas?

• Edited by aaronmcl Tuesday, April 10, 2012 11:00 AM

I took your advice and added the boot images to the DPs and wouldnt you know it - its working!

Thanks for your help!

• Edited by aaronmcl Tuesday, April 10, 2012 11:17 AM

I took your advice and added the boot images to the DPs and wouldnt you know it - its working!

Thanks for your help!

• Edited by aaronmcl Tuesday, April 10, 2012 11:17 AM

Hi,

Solved for me:

I get the folowing error message in the smsts.log:

[LOG[Failed to get information for MP:

This is a dhcp Server options issue. Option 006 was configured as 127.0.0.1. It must be changed by the dns server ip address.

Try it. even if pinging the sccm server works... 

On sccm 2012 (labs with windows server 2008 r2 sp1 & hyper-v)

• Proposed as answer by Tech-Os Thursday, April 25, 2013 9:31 AM

Hi,

Solved for me:

I get the folowing error message in the smsts.log:

[LOG[Failed to get information for MP:

This is a dhcp Server options issue. Option 006 was configured as 127.0.0.1. It must be changed by the dns server ip address.

Try it. even if pinging the sccm server works... 

On sccm 2012 (labs with windows server 2008 r2 sp1 & hyper-v)

• Proposed as answer by Tech-Os Thursday, April 25, 2013 9:31 AM

If connecting with VMs and using the vmnet3 adapter, inject the drivers for vmware  located in Program Files\Common Files\VMware\Drivers\ to the boot x64 and x86 boot images and then it will work.

• Proposed as answer by brandon.brouwer Tuesday, January 27, 2015 3:04 AM

If connecting with VMs and using the vmnet3 adapter, inject the drivers for vmware  located in Program Files\Common Files\VMware\Drivers\ to the boot x64 and x86 boot images and then it will work.

• Proposed as answer by brandon.brouwer Tuesday, January 27, 2015 3:04 AM