Jump to content


drewz99

SCCM 2012 OS Deployment Hangs

Recommended Posts

Just started having an issue when attempting to PXE into configmgr console for OSD. My machines will pxe to server, load boot image, load WinPE, prepare windows, load nic adapter, hang at 2012 SCCM splash scrren for about 20 seconds, then reboot.

Would anybody happen to have a resolution to this issues we are seeing?

 

I have redistibuted/updated distribution points in terms of content including boot images. This just started since i've moved and isolated this pxe service point to a new vlan.

Thanks

Share this post


Link to post
Share on other sites


pressing F8 is doing nothing for me? I'm not too sure what is going on? I have the vmware nic driver in the boot image and this has worked for months prior switching vlans. Do you think WMI would have anything to do with this?

Share this post


Link to post
Share on other sites

I don;t see any link with WMI, I would assume that the VLAN switch is the problem. Do you have IP Helpers pointing to the PXE server in the new VLAN? Is there a firewall between the VLANs?

 

You should be able to press F8 before the rebooting starts... You sure you enabled it in the boot image and distributed it?

Share this post


Link to post
Share on other sites

Recreated the boot images, removed/reinstalled the PXE roll/WDS from box.

Now, once all that was done, I am unable to to PXE at all. Getting a Started using DHCP Referral error/Config manager is looking for poilcy, It says it downloaded the wdsnbp.com file, then bombs out? Any ideas Peter?

Share this post


Link to post
Share on other sites

I have been able to get past the dhcp referral issue only to have it:

pxe, start win PE, prepare network connection, then hang for 20 seconds or so. Back to where i started.

Share this post


Link to post
Share on other sites

In our environment this happens for (so far) three reasons.

 

1. The client is not getting an IP address from DHCP (does not apply to you). Solution: make sure the correct NIC drivers are added to the boot image.

2. The date/time is incorrect in BIOS on the client. Solution: set the correct date/time.

3. There are no task sequences deployed to the client. This one is rare but has happened a few times for us. It seems like the client is in some sort of limbo where it's not unknown but it still isn't a part of a collection to which an OSD TS is deployed. And this all depends on how you deploy your TS, do you deploy to "All Unknown Computers" etc. Solution: find out the MAC address of the client and search for it in the SCCM console (create a query from where you can get the MAC address) --> delete the device from the SCCM console. If your OSD TS is deployed to "All Unknown Computers" this is all you have to do. If you deploy to another collection you need to import the device again and add to the correct collection (watch out for limiting collections etc).

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...