Diskless x86 solaris 10 (DHCP, PXE booting)

Has anyone gotten an x86 box to be a diskless client with Solaris 10?
I have a server setup(both jumpstart and diskless server) and booting sparc just fine, but I'd like to get an x86 machine working too (you know, for fun :)
I have my LX50 jumpstarting (standard install) just fine, but when I try to diskless boot it, it hangs with a "cannot mount filesystem" type error. I have a feeling it's because I'm using the standard netinstall nbp boot kernel in tftpboot.
So, what bootfile should I be using, what options do I need to set in my DHCP server (ISC DCHP version 3)
Thanks,
Chris

After the end of the kernel line in grub add "-v -m verbose" and see what gets printed during the boot before it hangs.
Darren

Similar Messages

X86: Solaris does not boot correctly?

I have installed Solaris on a second hard disk.
When I boot my computer on the second hard disk, I get the Solaris 10 emergency booting system which tries to find out on which hard disk I would like to boot Solaris 10.
Is there a possiblity to save my settings once for all time?
Because on every time I boot, I got the Solaris emergency boot manager to rechoose the disk on which I should boot.

Since a similar thing happens after other updates, it probably is not directly related to "uninstalling google desktop." Does the same thing sometimes happen when you do a regular restart (with no update or uninstall)?
You can try doing a SMU (power management) reset. Before you do that, reset PRAM.
http://support.apple.com/kb/HT1379
If that does not help, follow this procedure precisely to reset the SMU
http://support.apple.com/kb/HT1767
When you reconnect the power cord, if you were using an power strip of some kind (especially if it's old or overcrowded), try connecting it directly to a wall outlet by itself (at least initially). Start it up with only the power cord connected, then (if it starts up normally), add only standard USB keyboard and mouse. Use it that way for a while to see if there's improvement. If it's better, add your other peripheral devices back, one at a time, to see if the problem returns.

A question on Solaris 10 PXE boot, add_install_client error

Hello,
I am learning how to do network boot for x86 systems. I follow the Solaris 10 8/07 Installation Guide: Network Based Installation.
I would like to start from a simpler system, ie. client and install server are on the same subnet, thus, I don't need to configure a DHCP server. I follow the Example7-3 of the book, x86 Install Over the Same Subnet (with DVD media). However, I got stuck in adding client to the install server.
# ./add_install_client -e 00:14:5e:18:c5:b3 -i 172.17.139.165 net_test_6 i86pc
Adding Ethernet number for net_test_6 to /etc/ethers
enabling tftp in /etc/inetd.conf
Converting /etc/inetd.conf
enabling network/tftp/udp6 service
enabling network/rarp service
enabling network/rpc/bootparams service
enabling network/nfs/server service
updating /etc/bootparams
copying boot file to /tftpboot/pxegrub.I86PC.Solaris_10-1
ln: cannot create /tftpboot//pxegrub.I86PC.Solaris_10-1: File exists
Create a grub floppy and edit GRUB menu to contain
the following entry:
title Solaris netinstall
rarp
kernel /I86PC.Solaris_10-1/multiboot kernel/unix -B install_media=172.17.139.2
16:/export/home/sol10-x86-807
module /I86PC.Solaris_10-1/x86.miniroot
I don't know what does "Create a grub floppy" mean, can somebody tell me why I got such an error?
Thanks!
Tom

I ran into the same problem when I tried to activate the alternate boot environment. I deleted the file "packages_to_be_added" from the original boot environment. The file is in /var/sadm/system/data. Once the file is deleted try luactive again.

How to make a bootable copy of a x4-2 (x86) Solaris 11.2 boot disk

We have 58 X4-2 which will run identical software, one in each state and some territories, so need a way to copy the template system with all the apps loaded to the other systems. In the past we have used dd but that does not seem viable in the ZFS world on X86 hardware. Splitting a mirrored drive off also seems to be non viable, the split is not bootable after splitting.
Is there a 'ghost' like utility available? Any other methodology that will provide this functionality?

Hi,
this sounds like you might want to have a look at Unified Archives (maintained by archiveadm(1M)):
Using Unified Archives for System Recovery and Cloning in Oracle Solaris 11.2
Regards,
Ronald

PXE boot issue with DHCP and SCCM server on different subnets

I'm working with a client on the operating system deployment module of SCCM.
Their network configuration currently has a single large subnet for client
computers with a DHCP server on the same subnet. The SCCM subnet is
configured on a seperate subnet with no DHCP server on the subnet. We want to
configure client computers to be able to boot using the PXE client to deploy
OS images to the machines but can not get PXE-boot to work correctly.
Also, the client does not want to make changes to their network
infrastructure routers or switches to remedy this problem. Are there settings
on the DHCP or SCCM servers we can implement to make this work? If so, what
needs to be installed or configured on each server. We currently already have
WDS installed on the SCCM server and the SCCM server is configured as a PXE
Service Point within SCCM. Both WDS and the PXE Service Point seem to be working fine.
Any help would be appreciated.
Thanks,
Gary

I am Brazilian,
sorry for wrong english
My DHCP is on linux,
in my own structure VLANS
The system center is on the network
10.0.4.0/24
The machines on the network 10.0.5.0/24
The problem is that the machines that
are not on the same network system center
can not boot
I tried configuring / etc/dhcp3/dhcpd.conf
follows
option vendor-class-identifier "PXEClient";
option bootfile-name "\
\ SMSBOOT \ \ x86 \
\ wdsnbp.com";
option tftp-server-name
"10.0.4.101"; ---->
IP server
But it did not work, anyone know
how to configure?

PXE Boot a Hyper V Guest - Not receiving a DHCP IP Address

Hello Everyone,
I am trying to PXE boot a Hyper V guest, but am not getting a DHCP IP Address. Eventually the DHCP query times out and loads into the guest OS I have manually installed. See the PXE Boot Screen below. When in the installed guest OS, I do receive
a DHCP IP address as shown below. I am utilizing the Legacy Network Driver. I don't think it is related to VLAN identifier, but tried with/without and still no go. Any ideas what could be preventing this? Please let me know.
PXE Boot Screen:
CLIENT MAC ADDR: 00 15 5D F2 99 0C GUID: B366BBA1-D503-4D64-A77E-77474F3A2193
DHCP.........-
PXE-E51: No DHCP or proxyDHCP offers were received.
DHCP IPCONFIG in Guest OS:
Ethernet adapter Local Area Connection:
   Connection-specific DNS Suffix . : mywork.com
   IPv4 Address. . . . . . . . . . . : 10.242.242.251
   Subnet Mask . . . . . . . . . . . : 255.255.255.128
   Default Gateway . . . . . . . . . : 10.242.242.129
Thanks,
Ron

Hi Ron,
A solution is provided in this thread. You may need to have a look on the steps below:
• PXE-E51: No DHCP or proxyDHCP offers were received.
The client did not receive any valid DHCP, BOOTP or proxyDHCP offers. To resolve this issue, check each of the following network configuration items:
DHCP services are not available on the network to which the PXE-enabled NIC is connected.
A DHCP proxy or IP helper address is not configured for the subnet on which the PXE client is connected.
The switch port connected to the PXE NIC is running Spanning Tree Protocol, EtherChannel Protocol, or Port Aggregation Protocol and is thus not activated immediately when a link is detected. This forces the DHCP request from the PXE client to timeout.
DHCP is available on the network, but PXE is not.
The network cable is not attached to the PXE-enabled NIC on the target server.
See: http://social.technet.microsoft.com/Forums/en-US/d06413a4-af2b-4736-a510-c0a68eb880cf/cannot-get-certain-machines-to-pxe-boot
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]

Problems using PXE boot to jumpstart an HP client

Hello folks,
I have a Sparc jumpstart server that I am trying to use to jumpstart an HP with Solaris x86. I have gotten the x86 installation stuff installed by mounting the DVD on an x86 system and NFS exporting it to the jumpstart server. This seemed to work just fine.
My problem is PXE boot and DHCP. I have exported the appropriate directories, I have set up the DHCP service, and I can see on the client machine's console that it receives its IP address, but then I get the message "No filename or root path specified." I have a macro defined that points to the pxegrub file, and everything seems to be set up correctly. Does anyone have any thoughts on what I am missing?
Edited by: user13373794 on Feb 10, 2011 11:24 AM

Well, we managed to solve the problem with DHCP and PXE boot on the HP Proliant, at least the problem I first posted above. We have run into another problem. Apparently, the problem we had was twofold. First there is some sort of bug in the HP that if there is an LOM on the system you can't use the first network interface to PXE boot, it produces the error message about not finding the filename or root path. So the solution to that was to switch to the second network interface and change the DHCP server to answer that MAC address.
Making changes to the DHCP config on the Solaris jumpstart server somehow made it stop serving IP addresses to the client. As a last ditch attempt we shut down DHCP with the svcadm command and restarted it. This fixed that problem and now the PXE boot finds the pxegrub files and the installation starts up.
Now there is a new problem. We want to do a hands-off jumpstart, but the system pops up an X window and asks for keyboard type and some network and timezone info, and a root password. Then the install seems to proceed to use the profiles listed in the rules.ok file on the jumpstart server. So it does seem to be getting some config options from the jumpstart server, but not enough to be completly hands-off. Is there something we can add to the rules file or beginning script or something to fix this? Anyone have experience or even just a good guess?

Machines cannot PXE boot using SCCM 2012 DP

There are a lot of posts about PXE boot, but I can't find the common thread to tie them all together. My test machines cannot PXE boot.
My lab environment is very simple:
10.10.0.0/24 subnet
10.10.0.10 = W2k8 R2 DC, DHCP, DNS
10.10.0.11 = SCCM2012 (on W2k8R2 with SQL Server 2008 SP3 and CU4)
All machines are Hyper-V virtual machines connecting through the same virtual network.
Setup the PXE service from DP properties. I let SCCM install WDS. WDS in Server Manager does not have a server node, but the WDS service is running. DP PXE tab is configured as follows:
"Enable PXE support for clients" is checked
"Allow this distribution point to resond to incoming PXE requests" is checked
"Enable unknown computer support" is checked
"Require a password when computers use PXE" is not checked
"User device affinity" is set to "Allow user device affinity with automatic approval"
PXE is configured to respond on all network interfaces
The PXE server response delay is 0 seconds
The DHCP server has options configured as follows:
Option 66: 10.10.0.11
Option 67: smsboot\x86\wdsnbp.com
Both DP and MP on SCCM server are configured for HTTP.
Both x86 and x64 boot images have been distributed to DP. The media was updated after PXE was enabled on the DP.
Both x86 and x64 boot images have "Deploy this image from the PXE service point" enabled on the Data Source tab of their properties.
I have tried both unknown computer task sequence and a computer import task sequence (old computer association). They all end in abortpxe.com
Complete PXE response is as follows:
=================================================================
PXE Network Boot 03.23.2009
(C) Copyright 2009 Microsoft Corporation, All Rights Reserved
CLIENT MAC ADDR: 00 DD CC BB AA 00 GUID: 532D27E3-A184-4D27-A822-30A8B6F4A39D
CLIENT IP: 10.10.0.106 MASK: 255.255.255.0 DHCP IP: 10.10.0.10
GATEWAY IP: 10.10.0.5
Download WDSNBP...
Architecture: x64
WDSNBP started using DHCP Referral.
Contacting Server: 10.10.0.11 (Gateway: 0.0.0.0)
The detalis below show the information relating to the PXE boot request for
this computer. Please provide these details to your Windows Deployment Services
Administrator so that this request can be approved.
Pending Request ID: 6
Contacting Server: 10.10.0.11
TFTP Download: smsboot\x64\abortpxe.com
PXE Boot aborted. Booting to next device
===========================================================
From the smspxe.log:
]LOG]!><time="16:31:39.445+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6402">
<![LOG[Client Identity: {C9929C4D-735A-4973-8659-4D3D5D5E4F92}]LOG]!><time="16:31:39.445+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6428">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:31:39.480+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:31:39.505+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:31:39.505+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:31:39.533+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="16:31:39.553+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="bootimagemgr.cpp:1736">
<![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="16:32:00.963+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="bootimagemgr.cpp:1736">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:32:01.008+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:32:01.027+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.027+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.084+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777218" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
]LOG]!><time="16:32:01.108+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6402">
<![LOG[Client Identity: {C9929C4D-735A-4973-8659-4D3D5D5E4F92}]LOG]!><time="16:32:01.108+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6428">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:32:01.151+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:32:01.174+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.174+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.209+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="16:32:05.230+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="bootimagemgr.cpp:1736">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:32:05.290+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:32:05.325+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:05.325+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:05.366+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777218" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
=============================================================================================
I've been hammering this for about 10 hours now (or to be honest, it's been hammering me) and it must be something very simple I'm missing. I have a feeling that I'm doing something I used to do in 2007 and whatever that is, it does not work in
2012.
If I connect using boot media, Task Sequences execute perfectly.
TIA,
Tom

Option 66: 10.10.0.11
Option 67: smsboot\x86\wdsnbp.com
Pending Request ID: 6
Contacting Server: 10.10.0.11
TFTP Download: smsboot\x64\abortpxe.com
PXE Boot aborted. Booting to next device
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777218" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
Those options are fine when using DHCP options. They must be configured right because ConfigMgr does send a reply to the client ("abortpxe"). It basically tells you that ConfigMgr knows the MAC address and/or SMBIOSGUID of the client, but cannot find
a deployment for it.
Just find ResourceID 16777218 in the console (you might have to add the ResourceID column) and double check if there's an deployment available (properties of the client with resourceID 16777218).
Torsten Meringer | http://www.mssccmfaq.de
Your answer really helped me. I was searching for 2 days trying to find a computer in Config Manager. Your suggestion to "Just
find ResourceID 16777218 in the console (you might have to add the ResourceID column) and double check if there" was the trick to finding the computer in Config Manager. Thanks for all of your help
Gregory Campbell System Administrator

SCCM 2012 pxe boot issue

My test machines cannot PXE boot.
My lab environment is very simple:
10.10.0.0/24 subnet
10.10.0.5 = Server2012, DHCP, DNS, SQL Server 2008 R2 Sp2
10.10.0.7 = Server2012, SCCM2012
All machines are Oracle VM Box virtual machines connecting through the same virtual network.
Setup the PXE service from DP properties. I let SCCM install WDS. WDS in Server
Manager does not have a server node, but the WDS service is running. DP PXE tab is configured as follows:
"Enable PXE support for clients" is checked
"Allow this distribution point to respond to incoming PXE requests" is checked
"Enable unknown computer support" is checked
"Require a password when computers use PXE" is not checked
"User device affinity" is set to "Allow user device affinity with automatic approval"
PXE is configured to respond on all network interfaces
The PXE server response delay is 0 seconds
The DHCP server has options configured as follows:
Option 66: 10.10.0.7
Option 67: smsboot\x86\wdsnbp.com
Both DP and MP on SCCM server are configured for HTTP.
Both x86 and x64 boot images have been distributed to DP. The media was updated after
PXE was enabled on the DP.
Both x86 and x64 boot images have "Deploy this image from the PXE service point" enabled on the Data Source tab of their properties
SMSPXE.Log
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
]LOG]!><time="15:05:09.346-330" date="07-07-2014" component="SMSPXE" context="" type="1" thread="13592" file="libsmsmessaging.cpp:6544">
<![LOG[08:00:27:61:59:79, BF2ACCDD-1455-E149-963C-9A845B9C111E: no advertisements found]LOG]!><time="15:05:09.346-330" date="07-07-2014" component="SMSPXE" context="" type="1" thread="13592"
file="database.cpp:483">
<![LOG[08:00:27:61:59:79, BF2ACCDD-1455-E149-963C-9A845B9C111E: No boot action. Aborted.]LOG]!><time="15:05:09.441-330" date="07-07-2014" component="SMSPXE" context="" type="1" thread="13592"
file="database.cpp:483">
<![LOG[08:00:27:61:59:79, BF2ACCDD-1455-E149-963C-9A845B9C111E: Not serviced.]LOG]!><time="15:05:09.441-330" date="07-07-2014" component="SMSPXE" context="" type="1" thread="13592" file="database.cpp:483">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
]LOG]!><time="15:05:09.705-330" date="07-07-2014" component="SMSPXE" context="" type="1" thread="13592" file="libsmsmessaging.cpp:6544">
<![LOG[08:00:27:61:59:79, BF2ACCDD-1455-E149-963C-9A845B9C111E: no advertisements found]LOG]!><time="15:05:09.705-330" date="07-07-2014" component="SMSPXE" context="" type="1" thread="13592"
file="database.cpp:483">

Resource ID is already present in the Unknown Computer (Windows 7) Properties please look into it and
OSD Task Sequences is there :(.

Pxe boot sun x4170-m2 LSI raid 5 disks issues 2.10_u9 rel

Hi Gurus,
I am trying to image sun fire x4170-m2 series servers with Latest solaris 10.u9 patch set using Raid-5 disks setup with one hot-spare. Pxe boot works but i minboot not able to find raid-5 disks which is about 1.2 TB disks size. Where as if i used DVD to boot the servers it works properly. What i am missing. Here is my pxe entry and menu.list<mac-address> entry. I tried to insert driver LSI megraid driver with x86.miniroot, but it's already available into kernel/drv.
-dhcpd.conf entry.
host foobar { hardware ethernet 00:21:28:8E:3D:F2; fixed-address 10.228.150.14; next-server 140.87.100.21; filename "010021288E3DF2"; option host-name "foorbar.us.oracle.com";}
menu.1st.<mac-address>
cat /tftpboot/menu.lst.010021288E3DF2
default=0
timeout=30
min_mem64 1024
title Solaris_10 install_x86_64_2.10_u9
kernel /I86PC.Solaris_10-9/multiboot kernel/unix - install - nowin -B console=i86pc,install_config=140.87.100.21:/export/jumpstart_x86_64_2.10_u9,sysid_config=140.87.100.21:/export/sysid_2.10_u9/10.228.144,install_media=152.68.248.67:/vol/local/x86/solaris/100/base/u9/mar2011,install_boot=140.87.100.21:/export/install_x86_64_2.10_u9_new/boot -v -m verbose
module /I86PC.Solaris_10-9/x86.miniroot
Please let me know if you have any solution for this issue.
Thanks & Regards,
-Sunil.

Hi.
Read thread:
X4x70 (M1) with extremely slow disk I/O
Try workaround the problem by adding the following line to /etc/system and then reboot:
set idle_cpu_no_deep_c = 1
Regards.

SCCM 2012 R2 Won't PXE Boot

I'm trying to get PXE booting to work on our SCCM 2012 R2 server and am getting the dreaded "PXE-E53: No Boot file Name Received." DHCP server is in same subnet on a different machine, so supposedly no DHCP options or ip helpers are necessary. I'm
testing using a client VM with the legacy adapter for the NIC, and that machine PXE boots fine from our SCCM 2007 server.
When I test, I've been shutting down the SCCM 2007 server so that the 2012 machine is the only PXE server on our network.
In a nutshell, I'm trying to deploy Windows 8.1 using
this as a guide. The x86 and x64 boot images are enabled for PXE distribution and I've deployed the task sequence for the 8.1 OS image to all unknown computers. The DP shows content for the OS image and the boot images. PXE on the DP is enabled
and checkmarked to listen for PXE requests on all interfaces and for unknown computer support.
For troubleshooting I've tried unchecking all the PXE settinging in the DP, which removes WDS and then putting it back, as well as removing the MP role and putting it back (see attached snippet of SMSPXE.LOG).
I feel like I'm missing something basic here. Can anyone help?
Thanks!

Thanks, Jason. Yes, the MAC addrss is the client I'm trying to PXE boot.
I've reviewed the health in the monitoring section. No issues in System Status, and in Content Status there is only one error regarding the DP trying to contact an old SCCM 2007 distribution point at a branch office. This
appears to be a leftover from the migration process from SCCM 2007. This old distribution point is no longer in use and I can't seem to find any references to it on my SCCM 2012 R2 installation. Not sure if this is significant or not.
I've attached a snippet of the error:

Wds pxe boot - tftp download loop - 4 times F12

Hi
I just set up a new wds server 2012
When trying to pxe boot a client, it loops like this:
Downloaded WDSNBP from...
WDSNBP started using DHCP referral.
Contacting server...
Architecture...
Contacting server...
TFTP download: boot\x86\wdsnbp.com
Downloaded WDSNBP from ...
Architecture...
Contacting Server...
TFTP download: boot\x86\wdsnbp.com
Then it goes on 4 times in a row:
"TFTP Download: Boot\x86\wdsnbp.com"
With Option "Require the user to press the F12 key..." enabled,
I have to press F12 4 times, which is 3 times too many.After the x-th download of wdsnbp.com the client continues the boot process
normally and the rest works fine.
Any help is greatly appreciated.
Michael

We are experiencing the same thing.
This started after enabling scope option 67 to solve this error: PXE-E53: No Boot filename received.
This only occurs on selected machines. We do employ IP Helpers and are thinking this could be an issue.

Issues with Boot Images & PXE Booting Since SP1 Install

Good Afternoon All -
I recently updated to SP1, had some issues, but they got resolved. Now, though, I'm having an issue booting to PXE as well as updating any boot images created
before SP1 was installed. Booting to USB Bootable media using a newly created boot image seems to work fine.
Boot Images
When I update my DPs for any of my boot images in SCCM, they fail and i get the below error:
Error: The wizard detected the following problems when updating the boot image.
• Failed to install required components into the boot image
The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
• Description = "Failed to insert OSD binaries into the WIM file";
• ErrorCode = 2152205056;
• File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
• Line = 4566;
• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage.PackageID=\"BBS0012F\"";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889;
I've even gone as far as removing all drivers from the boot image, but still get the same message. I was able to create a couple of
new MDT boot images which seem to work fine, though. I am not sure which log file is for boot images, but nothing appeared in distmgr.log.
PXE Booting Issue
After trying many things, I removed PXE config from my site and uninstalled WDS then started all over again. Here's what I did and my results. Please tell me what I'm missing...
After uninstall & server reboot, I enabled PXE + every option in DP tab in SCCM
It automatically installed WDS (same server) and added the two boot images I had checked for PXE use. one x64 and one x86.
I checked my DHCP Scope whose values hadn't changed sine it worked (that I know of). They are:
Option #66: 192.168.20.37 (SCCM Server/DP/PXE)
Option #67 \boot\x86\wdsnbp.com. I've tried \boot\x86\pxeboot.com as well as each of these with x64.
When I PXE boot from a workstation, I receive an IP, a bit of info, then it goes to Contacting Server.... When trying one of the boot files above, I was prompted for F12, but receved a blue screen with error. When trying all other boot files,
they just hang at Contacting Server until they timeout.
I looked at SMSPXE.log and found something interesting...
The IDs for the two boot images I have assigned to PXE are ABC003B3 & ABC00B36. In the smspxe.log, though, it keeps repeating "could not find boot image ABC0012F! 12F does exist and is a boot image,
but not the one I want to use by any means and does not have PXE checked.
I went ahead and checked 12F, updated DPs (which failed - see above); unchecked it; then updated the DPs again. PXEBoot.log showed that it was trying to remove the 12F files from RemoteInstall which was a good sign. I then restarted the WDS service
and tried PXE booting again. Yet again, it failed and was still looking for 12F.
Any suggestions / Ideas??? Thanks!
UPDATE 1
I just changed option #67 to \smsboot\x86\pxeboot.com then restarted the WDS service. I booted to PXE and this time was asked to hit F12. I did so and it looked as if it would work.
Instead, I got a blue screen with the following error:
Recovery
Your PC needs to be repaired
The boot configuration disk contains errors or is missing
file: boot\BCD
Error Code: 0x000000f
I think that it's the same error as before, but is blue instead of black due to new Win8ADK perhaps. Thanks
Ben K.

Update 4
Sorry to make this the longest post ever :)
I just read that others with this error checked DISM.log. I did so when running a DP update for the boot image and got the below errors:
2013-01-11 16:27:04, Info DISM DISM Provider Store: PID=1636 TID=5104 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2013-01-11 16:27:07, Info CBS Failed to find a matching version for servicing stack: C:\Windows\TEMP\BootImages\{DADCFE01-3557-4058-99CC-2A15EDF905AF}\mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810b\
[HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2013-01-11 16:27:07, Info CBS Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2013-01-11 16:27:07, Warning DISM DISM Provider Store: PID=4104 Failed to Load the provider: C:\Windows\TEMP\0555ABC5-006D-4C3F-B79F-EA0E723FA971\MsiProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-01-11 16:27:07, Warning DISM DISM Provider Store: PID=4104 Failed to Load the provider: C:\Windows\TEMP\0555ABC5-006D-4C3F-B79F-EA0E723FA971\TransmogProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-01-11 16:27:07, Error DISM DISM Package Manager: PID=4104 The package WinPE-Scripting-Package is not applicable to the image. - CPackageManagerCLIHandler::Private_ProcessPackageChange
2013-01-11 16:27:08, Info DISM DISM Package Manager: PID=4104 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
2013-01-11 16:27:08, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/TEMP/BootImages/{DADCFE01-3557-4058-99CC-2A15EDF905AF}/mount/Windows/System32/config/SOFTWARE,
the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
(The above one appears 8 times - almost in a row)
2013-01-11 16:27:08, Error DISM DISM Package Manager: PID=4104 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081e)
Help! Thanks :)
Ben K.

PXE Boot with UEFI. WDS not sending WinPE wim

I am trying to test PXE booting on devices that only have UEFI and no CSM support.
We are running Windows Server 2008 R2 in our environment.
On the DHCP server, we have option 66 and 67 set. If I change option 67 to SMSBoot\x86\wdsnbp.com and boot a traditional BIOS system (non UEFI) the SCCM server responds and gives me the option to hit F12 and PXE boot. This works without issue and can deploy
images.
I then change option 67 to SMSBoot\x64\wdsmgfw.efi and use a machine that is pure UEFI (meaning UEFI without any legacy support / CSM). The system appears to successfully download the wdsmgfw.efi and font file via TFTP as shown in the WDS logs. However, it
then goes to the next sreen where it is trying to contact the WDS server. AFter retrying for a while it will error out with error 0x102 which I believe translates to ERROR_TIMEOUT
The SMSPXE.log repeats the following:
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>8908f9c4-c345-49ba-b137-af7b0b983584</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="GAS20043" OfferIDTime="7/24/2013 3:12:00 PM" PkgID="GAS00037" PackageVersion="" PackagePath="<a href="http:///SMS_DP_SMSPKG$/GAS00038">http://<IVE
REMOVED THIS>/SMS_DP_SMSPKG$/GAS00038" BootImageID="GAS00038" Mandatory="0"/></ClientIDReply>
SMSPXE 7/24/2013 7:14:58 PM 7724 (0x1E2C)
00:50:56:01:00:82, DF6A0C42-F909-B518-7B44-3150B662200B: found optional advertisement GAS20043 SMSPXE 7/24/2013 7:14:58 PM 7724 (0x1E2C)
Looking for bootImage GAS00038 SMSPXE 7/24/2013 7:14:58 PM 7724 (0x1E2C)
Any idea what may be going on?

Hey,
I am having the following situation:
DP1 = Windows Server 2008 R2 SP1 (Standalone Primary Site Server SCCM 2012 SP1 CU2)
DP2 = Windows Server 2012
UEFI Client: Microsoft Surface Pro (with Microsoft Surface Network Adapter)
BIOS Client: HyperV Virtual machine with Legacy network adapert
DP1; DP2 and DHCPServer all in Subnet1.
(IP Helper is set for DHCPServer for DHCP and for DP1 & DP2 for DHCP and BootP - I checked serveral times if everything is right here)
UEFI Client and BIOS Client in Subnet2.
Situation1 -- Using no DHCP Options and both DPs(DP1 and DP2) WDS running:
UEFI Client - Boots perfectly (contacting Server DP2)
BIOS Client - Boots perfectly (contacting Server DP2)
Situaion2 -- Using no DHCP Options and WDS just running on DP1:
UEFI Client - Does not boot (no error information is provided)
BIOS Client - Does not boot (no Bootfilename recieved)
Situation3 -- Using DHCP Options(Option 66="IP of DP1" Option 67="SMSBoot\x86\wdsnbp.com") and WDS just running on DP1:
UEFI Client - Does not boot (no error information is provided)
BIOS Client - Boots perfectly (contacting Server DP1)
Situation4 -- Using DHCP Options(Option 60="PXEClient" Option 66="IP of DP1" Option 67="SMSBoot\x86\wdsnbp.com") and WDS just running on DP1:
UEFI Client - Boots perfectly (contacting Server DP1)
BIOS Client - Does not boot (taking hours to recieve dhcp options..)
My problem is i am having a lot of location with 2008 R2 SP1 server only (this is why situation 1 is not enough for me :-( ).
Based on this article:
http://ccmexec.com/2013/05/configmgr-2012-uefi-and-pxe-boot-support/
x64 UEFI Devices should work with Server 2008 R2 SP1 (not only Server 2012).
Interesting is I am having ALL files on Server 2008 R2 SP1 like they are on Server 2012 (in SMSBoot\x86 folder, too!)??
Some more ideas?
Thank you for help

Lenovo X1 Carbon PXe boot errors with SCCM 2007

I know there are many posts on this and I've gone through them all, but I am still having issues PXe booting a X1. I have a USB ethernet dongle (the new type with the rounded edge). the part number is 0b67708. It's branded Lenovo but when I pxe it recognises it as ASIX AX88772b. So far so good. It picks up an IP from DHCP ok, recognises the hardware as x64 and then tries to download the \smsboot\boot.sdi file from the SCCM 2007 server. It waits for 20 seconds then falls over with the following:
Status: 0xc0000001 - Info: The boot selection failed because a required device is inaccessible.
Now, I have the the following drivers in the boot.wim file:
x86 -
1. Lenovo USB2.0 Ethernet Adapter 5.12.7.0
2. PCI bus
3. Intel ICHR/DO/DH SATA AHCI Controller
4. Intel USB 3.0 Root Hub
5. Intel USB 3.0 eXtensible Host Controller
x64 -
1. Lenovo USB 2.0 Ethernet Adapter 5.14.4.0
2. PCI Bus
3. Intel ICHR/DO/DH SATA AHCI Controller - 2821
4. Intel USB 3.0 Root Hub
5. Intel USB 3.0 eXtensible Host Controller
I have tried using the ASIX drivers, all previous driver version, adding in the mass storage drivers, adding in the USB 3.0 drivers, praying to the PXe gods but nothing works.
All other hardware works fine. Any suggestions greatly welcomed.
Cheers - Mark.

Make a USB recovery drive before reinstalling.Thats the only option with a preload. With a retail serial number, you can download an iso with the upgrade assistant.
Also, how much ram do you have. If yopu have more than 4GB, you will need 64 bit XP, or the performance will take a hit. I tried XP on my W530, but I had to change several settings in the BIOS/UEFI.
W530(2436-CTO): i7-3720QM, nVidia Quadro K2000M,16GB RAM, 500 GB hard drive, 128GB mSATA SSD, Ubuntu 14.04 Gnome, Centrino Ultimate-N 6300.
Yoga 3 Pro: Intel Core-M 5Y70, Intel HD 5300, 8GB RAM, 128GB eMMC, Windows 8.1, Broadcom Wireless 802.11ac.

Diskless x86 solaris 10 (DHCP, PXE booting)

Similar Messages

Maybe you are looking for