PXE boot PXEfilter.vbs

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 PXEfilter.vbs

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 PXEfilter.vbs

Page: [1]

Message

<< Older Topic Newer Topic >>

PXE boot PXEfilter.vbs - 9/17/2008 8:04:39 PM

cjones464

Posts: 69
Score: 0
Joined: 7/23/2004
From: UK at the moment
Status: offline

10 intensive days later and I still don’t have it working.
I have SCCM RC SP1 in mixed mode on 2003 R2 sp2 server.

When I install everything on a single server PXE boot works fine. Despite errors in the PXEfilter.vbs
Capture and build XP sp2 (using Vista mini nt boot image)
This in itself has been a nightmare. With copious amounts of conflicting advice.

However I cannot get this to work once I move the move the PXE boot point to a DP
Under certain settings I can get the client to PXE boot but it never finds the boot image.
I’ve rebuilt the site and the dp from scratch - many times using slightly different build orders.
I’ve done all the removal and re-install of the WDS and PXE service point suggested here and else

When I compare the logs with my working single server site the glaringly obvious difference from my most successful build order is the lack of any entries referring to SMS PXE in the wds log

It appears that the pxefilter.vbs is not having any effect at all.
and what ever I do I still get the dreaded "fix all PXE errors before continuing" error when I try to install the PXE filter
(this also happens occasionally on the all in one server that actually works ok)
I cant find enough info about how this wretched pxeboot.vbs is working.

Can anybody point me in the right direction for the definitive explanation on pxeboot.vbs ?
Where is there info on what these PXE errors are/could be
Please.

_____________________________

Implementing SMS since 1995.
Dont ask me about scrips and stuff but if you wanna know how to bolt the tecky bits togeter with the business Requirement I could have some tips

Post #: 1

Why PXEfilter.vbs - 9/23/2008 5:12:28 PM

rjarrett

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

Are you going down the MDT\PXEFilter.vbs for a specific technical reason or because it seems to be the trend?

I ask because PXE can be made to work nicely, right out of the box. That is the route I went, so if you are open to trying it that way, maybe I can help. Otherwise, I don't have the familiarity to help with the MDT route...

_____________________________

Let me know if this helped...

Rob Jarrett
SMS\VB Development

(in reply to cjones464)

Post #: 2

RE: Why PXEfilter.vbs - 9/25/2008 7:17:36 AM

cjones464

Posts: 69
Score: 0
Joined: 7/23/2004
From: UK at the moment
Status: offline

Rob.
I am going the MDT\Pxefilter cause thats "what the book says" and to begin with I was not 100% certian about all the requirements to make it work and I needed to understand this.
No that I understand it I am leaning towards doing the same process but "outside" of the MTD control.

I have a requirement to be able to build and rebuild workstations at remote sites using close to zero touch PXE boot. (we have 30 sites with no onsite IT support) MDT and PXE DPs seemed to facilitate this.
Getting PXEfilter.vbs to install consistantly has been a nightmare and I am begining to regret this choice of approach.

I am very much open to trying an alternative "right out of the box" method an interested in what you have to say.
Though PXE MDT is still in my plan my pilot roll out dates are comming up on me fast and I have to look at sound technicle alternative.

Thanks for your input

(in reply to rjarrett)

Post #: 3

Out-of-the-box - 9/26/2008 1:30:09 PM

rjarrett

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

The out-of-the-box solution is providing me with the ability to do PXE imaging, PXE re-imaging, and a qualified Zero Touch deployment. What do I mean by a "qualified" hands-free deployment? It assumes the Name\MAC are added to a collection that regulates my PXE clients. This means, I add their Name\MAC to a collection before they are eligible for PXE support. After that, the PXE imaging and re-imaging are zero touch.

To some, this is an unacceptable burden. That's one of the big advantages to using a script. It can be used to automatically install an "unknown" machine into the collection, then proceed with the imaging. It is my understanding that SP1 may provides this capability, with some restrictions. Obviously, a case can be made for plugging in a machine and turning it on. On the other hand, if you wish to exercise some granularity in control, the out-of-the-box work with that one requirement to load the Name\MAC into a collection.

I won't go into every detail for the out-of-the-box solution here, but if you are able to do some additional testing, then the following may be useful. Typically, I have seen a variety of problems with getting clients to PXE image for:

Client Not Locating A PXE Server
This generally comes down to getting your DHCP to provide the PXE server address to the PXE booting client. The SCCM\PXE is optimized to work with Microsoft's DHCP. However, many do not use MSDHCP. Troubleshooting this topic is beyond the scope of this post, but suffice it to say that when it is working, the PXE booting machine will clearly announce in the command window that it is connecting to the PXE server for download.

Boot and\or Operating System Image Lacks Drivers
This generally means either NIC or mass storage drivers are not valid for the target machine. If either the Boot image or the Operating System image does not include the proper NIC drivers, then the client cannot connect to the network to download the image and\or to come on-line properly once reimaged. Similarly, if the either the boot or operating system image cannot "see" the hard drive, then it will fail.

Network Access Account Not Set
Resolution: Go into the Client Policy in SCCM and set a Network Access Account. It sometimes "disappears" even after everything has been working fine.
http://www.myitforum.com/forums/m_177370/mpage_1/key_/tm.htm#177370

PXE CERT Not Set
The client TSLog files suggest that the PXE cert is not set. Check the PXE Certificate in the SCCM console. Verify that the Root CA is trusted. Alternatively, reset the expiration date. Sometimes the PXE process stops liking the certificate.
http://www.myitforum.com/forums/m_177312/mpage_1/key_/tm.htm#177312

GetHostByName Failed
If the client cannot "ping" or resolve the PXE server's distribution point, the downloads fail. Ensure the FQDN is properly set.
http://www.myitforum.com/forums/m_177318/mpage_1/key_/tm.htm#177318

_____________________________

Let me know if this helped...

Rob Jarrett
SMS\VB Development

(in reply to cjones464)

Post #: 4