PXE Boot - Contacting Server....

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

PXE Boot - Contacting Server....

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> PXE Boot - Contacting Server....

Page: [1]

Message

<< Older Topic Newer Topic >>

PXE Boot - Contacting Server.... - 3/11/2008 2:31:12 PM

rjarrett

Posts: 571
Score: 17
Joined: 5/26/2004
Status: offline

Roger Truss posted the output of what a successful PXE boot looks like. Thanks, it triggered an understanding of what is going on with my PXE clients. Specifically, it states "...Please provide these details to your Windows Deployment Services Administrator so that this request can be approved."

Duh! The install is pending approval. So, it sits there waiting, waiting, waiting... Somehow, I have to approve it. Either real-time or by some form of preset configuration.

Q1. How do I "approve" a PXE client request without configuring WDS?

Q2. How can I make SCCM "automatically approved" requests without configuring WDS?

Roger Truss' Post

quote:

Contacting Server (xxx.xxx.xxx.xxx)
Architecture: x64

TFTP download SMSBoot\x64\pxeboot.com

Then the WDS server gives me 5 options when I boot an x64 system (The first 4 I created using the WDS console):
Image Deploy (x86)
Image Capture (x86)
Image Deploy (x64)
Image Capture (x64)
Remote Installation Services

http://www.myitforum.com/forums/m_173000/mpage_1/key_/tm.htm#173000

Thumbnail Image

Attachment (1)

< Message edited by rjarrett -- 3/12/2008 9:07:44 AM >

_____________________________

Let me know if this helped...

Rob Jarrett
SMS\VB Development

Post #: 1

PXE Boot - Contacting Server.... - 3/12/2008 8:50:08 AM

rjarrett

Posts: 571
Score: 17
Joined: 5/26/2004
Status: offline

PXEGuy, from TechNet, suggests that I don't have an approval problem.
http://forums.microsoft.com/technet/showpost.aspx?postid=2991626&siteid=17&sb=0&d=1&at=7&ft=11&tf=0&pageid=1

Despite this, my PXE clients still don't proceed past the "Contacting Server" message. In the SMSPXE.log, there are new "Device has been accepted" every time a new "." shows up on the client screen. So, it appears to be waiting. Here are a couple of things to know about my questions:

Q1. How do I "approve" a PXE client request without configuring WDS?
I install WDS, assign the PXE role, and deploy the boot images without configuring WDS.

Q2. How can I make SCCM "automatically approved" requests without configuring WDS?
I have configured a "Lifecycle" collection and added my new PXE client, by MAC address, to it.
The Task Sequence that uses my x86 boot image and installs my reference image is advertised to Lifecycle.
The advertisement is set to "Run ASAP"

_____________________________

Let me know if this helped...

Rob Jarrett
SMS\VB Development

(in reply to rjarrett)

Post #: 2

RE: PXE Boot - Contacting Server.... - 3/12/2008 10:28:40 AM

wbracken

Posts: 951
Score: 21
Joined: 4/12/2002
From: St. Louis
Status: offline

A good place to start troubleshooting is looking at the status messages on the server for the PXE service point as well as the PXE logs on the server. I had this problem before and it turned out for me that I didn't have both x86 and x64 boot images assigned to both the standard DP and the PXE DP.

_____________________________

William Bracken

My new Blogsite:
http://www.clientarchitect.com

(in reply to rjarrett)

Post #: 3

Boot Images - 3/12/2008 11:04:48 AM

rjarrett

Posts: 571
Score: 17
Joined: 5/26/2004
Status: offline

I am 100% confident that both the x64 and x86 images were deployed to both the normal share and the SMSPXEIMAGES$ share. The status messages showed it, the files are physically there, and the network imaging using bootable media verifies that the normal share works at a minimum.

As you may have seen from the other threads, I have even tried some WDS only testing. So far, I can get the PXE boot to pull down and launch the WinPE boot image using WDS-only. It never launches the O/S imaging file, but at least I have been able to verify that the boot image works through a PXE system.

The WDS-only deployment behaves similarly, and it behaves more as expected. I get the same boot messages up to the "Contacting Server..." point as I would with an SCCM\PXE\WDS deployment. The difference is, if the computer account exists in AD or if I "approve" it using the WDS Pending queue, it proceeds to run the boot WinPE.

That seems to be the distinction. The "approval" process works in a WDS-only mode, but not in an SCCM\PXE\WDS mode. I have added the computer to a collection called Lifecycle using the Computer Association | Import Single Computer wizard. So, it should be "approved" by the SCCM. The Task Sequence for the O/S reference image is advertised as "mandatory" to the Lifecycle collection, so it should be "pre-approved" and not require any interaction.

_____________________________

Let me know if this helped...

Rob Jarrett
SMS\VB Development

(in reply to wbracken)

Post #: 4

PXE Boot - Contacting Server....Timeout - 3/12/2008 1:07:37 PM

rjarrett

Posts: 571
Score: 17
Joined: 5/26/2004
Status: offline

The attached shows two screen shots in one. The top half is what it looks like while the PXE client is waiting for "approval" and the bottom half is what happens when it times out.

In this case, the displayed IP data is all valid, the architecture (x86) is correct, and the PXE Server IP address is good. The new PXE client is in a collection called Lifecycle which has an enabled Advertisement for the reference image Task Sequence.

Thumbnail Image

Attachment (1)

_____________________________

Let me know if this helped...

Rob Jarrett
SMS\VB Development

(in reply to wbracken)

Post #: 5

RE: PXE Boot - Contacting Server....Timeout - 3/17/2008 9:35:22 AM

callen416

Posts: 38
Score: 0
Joined: 9/21/2005
Status: offline

Ive had this happen also. After double checking everything(and finding nothing wrong) , I deleted the images from the pxe server, waited, then deleted the pxe service point , uninstalled wds. Rebooted pxe server. Installed and didnt config wds. Then I installed the Pxe Service point and resent the pxe boot images.

Be sure to check the registry and delete any outstanding entrys relating to wds and the pxe service point before you reinstall.

(in reply to rjarrett)

Post #: 6

RE: PXE Boot - Contacting Server....Timeout - 3/17/2008 2:08:09 PM

rjarrett

Posts: 571
Score: 17
Joined: 5/26/2004
Status: offline

Can you elaborate on the registry settings? Local Machine? Where?

_____________________________

Let me know if this helped...

Rob Jarrett
SMS\VB Development

(in reply to callen416)

Post #: 7

PXE Boot - Boot Image Will Not Import - 3/18/2008 11:24:17 AM

rjarrett

Posts: 571
Score: 17
Joined: 5/26/2004
Status: offline

Somewhere along the line, a post suggested deleting the boot images and reimporting them in order to ensure their permissions, etc. were good. Having made no progress elsewhere, I did. I deleted the boot images from the distribution points. Waited till they cleared. Then removed the boot images from OSD.

When I try to re-add them, I get the following failure. I am importing the EXACT same boot.wim files that were originally installed by SCCM. No permissions have been changed. In fact, I later added Everyone Full Control without success.

Ideas?

Thumbnail Image

Attachment (1)

_____________________________

Let me know if this helped...

Rob Jarrett
SMS\VB Development

(in reply to rjarrett)

Post #: 8

RE: PXE Boot - Boot Image Will Not Import - 5/1/2008 11:00:24 AM

rdangerfield

Posts: 13
Score: 0
Joined: 12/10/2007
Status: offline

Hey there,

I was having the same initial problem as you and I edited the PXEfilter.vbs. as the WDS was running on my confmgr server I removed the administrator name and password from the VBS script then everything was fine.

Hope this helps,

Ryan.

(in reply to rjarrett)

Post #: 9