Jump to content

SCCM 2012 OSD stuck on PXE boot

FN-GM

By FN-GM
in O/S Deployment

 Share

Recommended Posts

FN-GM

FN-GM

Posted
Posted

Hi,

 

I have setup a New SCCM setup.

 

I have my required WIM file and i have created a task sequence. I have configured my x86 boot image to "deploy this boot image from the PXE service point" I have uploaded all this to a distribution point. I have deployed the task sequence to a machine where my test machine already lives. It had a previous install of windows on and has been talking to SCCM for a couple of weeks.

 

When i PXE boot i get the attached.

 

Any thoughts

SCCM PXE.PNG

sparkeh

sparkeh

Posted
Posted
It does yes, so if its already in there i cant image out to the machine?

 

Thanks

Well, I would have thought that if you advertised the TS to the machine it would just pick it up and run it without the need to PXE boot it?

Unless I am mistaken, I use PXE to add new machines to SCCM but advertise TS to existing machines to reimage.

edie209

edie209

Posted
Posted

Is it just stopping at that screenshot? or does it move on to the next bootable device?

 

Do you have Active Directory System Discovery enabled? and has that found your pc or have you manually added it?

FN-GM

FN-GM

Posted
  • Author
Posted
Well, I would have thought that if you advertised the TS to the machine it would just pick it up and run it without the need to PXE boot it?

Unless I am mistaken, I use PXE to add new machines to SCCM but advertise TS to existing machines to reimage.

 

I would like to use PXE on all machines ideally. Have i missed something here

 

Is it just stopping at that screenshot? or does it move on to the next bootable device?

 

Do you have Active Directory System Discovery enabled? and has that found your pc or have you manually added it?

 

The machine reboots. I have system discovery working and it found the machine and installed the client ages ago.

 

Thanks

edie209

edie209

Posted
Posted
Just a thought have you had any machines PXE booting with SCCM? I had a similar problem early on and the DHCP was not configured correctly options 66 and 67. If that is ok have you tried restarting the wds service? failing that try clearing the required pxe deployments and restarting wds service/
  • Thanks 1
FN-GM

FN-GM

Posted
  • Author
Posted
Nope this is my first time at doing it. I havent configured DHCP that might be where i am going wrong. Do you have any good quides on how to do this please?
FN-GM

FN-GM

Posted
  • Author
Posted

I have been on an SCCM coruse but PXE was covered at all.

 

Do i use the x64 image even though i am using a mix of x86 and x64?

 

I have installed WDS.

 

Also am i required to deploy the task sequence to a collection. If any machines are turned on will they see this in the software center? My aim is to be able to PXE and reimage problem machines at any time.

 

Thanks

edie209

edie209

Posted
Posted

Both boot images need to be distributed (I use the x64 to boot though)

 

I am probably not much further along than you but lets see what we can sort out for you.

 

Deploy the TS (Task Sequence) to a test collection with a pc to try out first just so you know all is good without re-imaging an entire suite and getting it wrong. I have found (and this might be wrong) that I have had to visit each machine for the image to be deployed initially by SCCM ( I am playing around with Required TS as we speak) The TS can be hidden from the software center when you create it.

 

Hopefully that will get you on your way but any questions fire away.

FN-GM

FN-GM

Posted
  • Author
Posted
Deploy the TS (Task Sequence) to a test collection with a pc to try out first just so you know all is good without re-imaging an entire suite and getting it wrong

 

Yep got that covered :)

 

I cant seem to see where to hide the TS. am i being blind? Thanks

FN-GM

FN-GM

Posted
  • Author
Posted

Is there a 3rd option to configure in DHCP for some reason in my mind i am thinking option 60 is also needed.

 

Thanks

edie209

edie209

Posted
Posted

Just a thought when you installed WDS did you configure it? I have read somewhere this error is to do with a mis-configuration of wds, have a look here using SCCM 2012 RC in a LAB - Part 2. Add SUP and WDS - Configuration Manager 2012 - Release Candidate - www.windows-noob.com he explains how to install wds.

 

BTW if this is your problem you can remove the role reboot the server and re add the role (I know cos I have done it) It is really important that it is setup the way he describes.

edie209

edie209

Posted
Posted
Is there a 3rd option to configure in DHCP for some reason in my mind i am thinking option 60 is also needed.

 

Thanks

 

Mine is not but dhcp is on a different server

FN-GM

FN-GM

Posted
  • Author
Posted
Mine is not but dhcp is on a different server

 

We should be good then.

 

When i installed WDS i didnt touch it. Will look at the guide and get to you.

 

Thanks

FN-GM

FN-GM

Posted
  • Author
Posted

ah ha!!! i have changed option 67 in DHCP to this - SMSBoot\x64\pxeboot.com

 

and it now gives me the F12 boot option. But i can get the attached error.

 

Ergghhh!!

pxe3.PNG

edie209

edie209

Posted
Posted

I have have a similar issue when a TS in the early days failed and I right clicked both boot images, went into properties unticked "Enable Command Support" clicked apply, let it go through its process and then ticked it again, let it go through the process again and then deployed both images again

 

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing


×
×
  • Create New...