If the PC that is failing PXE is indeed in a collection to which the task sequence is deployed, you might want to double check to make sure there are not duplicate records for that machine in ConfigMgr. I've been in environments where a duplicate record is created and the machine I think is in the correct collection isn't actually the machine I am working to PXE boot.
Jeff On Thu, Jun 19, 2014 at 3:12 PM, Brian McDonald <[email protected]> wrote: > Yes, the deployment is setup to target media and PXE. > > ------------------------------ > Date: Thu, 19 Jun 2014 14:58:58 -0500 > Subject: Re: [mssms] PXE and known computers > From: [email protected] > To: [email protected] > > > Is the task sequence deployed to a collection of which the known computer > is a member? Is the deployment available to media and PXE? > > Jeff > > > On Thu, Jun 19, 2014 at 2:51 PM, Trevor Sullivan <[email protected]> > wrote: > > Have you looked at the smspxe.log, to see why they’re getting rejected? I > am assuming that you have a OSD task sequence advertised to the known > computers (hopefully not “required,” but still valid)? > > > > Cheers, > > Trevor Sullivan > > Microsoft PowerShell MVP > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Brian McDonald > *Sent:* Thursday, June 19, 2014 2:49 PM > *To:* [email protected] > *Subject:* [mssms] PXE and known computers > > > > Is there a trick to getting PXE working with known computers in SCCM 2012 > R2? > > I can PXE bare metal machines (unknown to SCCM) with no problems. However, > if they are cliented PXE doesn't seem to work on these machines. > > I get the following: PXE Boot aborted. Booting to next device... > PXE-MOF: Exiting PXE ROM. > > What am I missing here? > > Thanks, > > Brian > > > > > > >
