|
rjarrett -> Out-of-the-box (9/26/2008 1:30:09 PM)
|
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
|
|
|
|
