Might be the subnet which your are trying for image added /mapped to some other site server in boundaries. It tries to pick content from the defined server.
On Mon 6 Jul, 2015 10:24 pm Chris Carbone < [email protected]> wrote: > As far as those logs go, you might be looking in the wrong area because > I also receive all of those same entries and PXE works fine here. > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Kevin Kaminski > *Sent:* Monday, July 06, 2015 11:41 AM > *To:* [email protected] > *Subject:* [mssms] RE: [sccm 2012] PXE boot not working in native mode > > > > It doesn’t go that far and if I look for the task sequence status there > are no messages to be found. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Chris Carbone > *Sent:* July 6, 2015 10:34 AM > *To:* '[email protected]' > *Subject:* [mssms] RE: [sccm 2012] PXE boot not working in native mode > > > > When you say PXE is failing with a black screen, do you even see the > dialog appear within WinPE where it says, “Loading Windows Settings” > “Preparing Network Connections” etc etc. Do you get that far? And if you do > get that far, at which step does it attempt, and then bomb out? > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Kevin Kaminski > *Sent:* Monday, July 06, 2015 10:11 AM > *To:* [email protected] > *Subject:* [mssms] [sccm 2012] PXE boot not working in native mode > > > > Hi, I’m in a rather weird position that has me hung up. I did some work > cleaning up a customer’s PKI as they had some invalid CDPs being specified > in their certificates. In the end we opted to publish our CRLs to LDAP and > HTTP locations to fix this issue. I went about issuing the certificates for > the primary site server, the first one was used for the DP/MP/WSUS roles > and the second for PXE. I also issued client certificates as well. > > > > Everything is working from client communication to updates deployment but > PXE keeps failing with a black screen after booting. I’ve taken > certutil.exe and validated both the CRLs with –URL and the validity of the > certificates using –verify. If I look into the SMSPXE.log on the server I > see quite a few things going wrong but I haven’t been able to resolve > them. Here is a quick overview of what I see as potential problems, I can > post more of the log if it helps anyone. > > > > > > > > 1. I just rebuilt the image yet I am still being told to update it. > It is even more confusing because it was built from scratch when the new > certificate was configured and confirmed to be in the running configuration > through the SMSPXE.log. > > 2. I still can’t find much on this task sequence variable and I am > not sure if this is one of those SCCM errors you can ignore or is it linked > to our issue. > > 3. I still can’t find much on this task sequence variable and I am > not sure if this is one of those SCCM errors you can ignore or is it linked > to our issue. > > 4. I keep seeing this in the logs but it just does not make sense. > The best match I get suggests that the distribution point is using a > self-signed certificate which it is not from the checks I have done in the > SMSPXE.log. There is another that suggests you have the wrong root CA > certificate configured in SCCM which I did re-confirm the right one is in > place. > > > > I’ve tried chasing a number of forum posts but I can’t seem to get > anywhere. I am open to suggestions as to where to go next. Any takers? > > > > This electronic mail transmission may contain confidential information > intended only for the use of the individual(s) identified as addressee(s). > If you are not the intended recipient, you are hereby notified that any > disclosure, copying, distribution or the taking of any action in reliance > on the contents of this electronic mail transmission is strictly > prohibited. If you have received this transmission in error, please notify > me by telephone immediately. > > > > > This electronic mail transmission may contain confidential information > intended only for the use of the individual(s) identified as addressee(s). > If you are not the intended recipient, you are hereby notified that any > disclosure, copying, distribution or the taking of any action in reliance > on the contents of this electronic mail transmission is strictly > prohibited. If you have received this transmission in error, please notify > me by telephone immediately. > >
