PXE Boot/Ip helper address for staging OS-es
Hi,
In our production environment there is already a PXE-server SCCM 2007. Now, we're setting up an SCCM 2012-server which we would like to test staging/OS-deployment also.
Is it safe to say we need to add the ip of the SCCM 2012 "066 Boot Server Host Name" to stage. Note: on switches (Cisco) this is ip helper address, correct?
Please clarify.
NOTE: is there an option to make it work WITHOUT needing a new VLAN?
J.
Jan Hoedt
DHCP options and IP helper addresses have the same end goal but are completely different things.
IP Helpers automatically forward broadcast requests to a destination system thus "bridging" subnets for services like DHCP and PXE.
DHCP scope options directly instruct the NIC to boot from a specific PXE server.
So, yes, it is possible to manipulate where a client PXE boots from, but it takes an integral understanding of how PXE works, of how IP Helpers work, and of how NICs initiate a PXE boot when either IP Helpers or DHCP scope options are in place (and
thus DHCP also). Because *none* of this really has anything to do with ConfigMgr or even Microsoft itself, there really is no Microsoft guidance except that IP Helpers are preferred and are the Microsoft supported solution. A great starting reference
is at http://en.wikipedia.org/wiki/Preboot_Execution_Environment
Jason | http://blog.configmgrftw.com
Is there any official Microsoft documentation that outlines why IP Helpers are preferred over scope options?
Similar Messages
-
Hi,
I just centralized our dhcp server to HQ server, and zdm pxe boot stopped working.
HQ dhcp server is oes2 sp3 on sles10sp3.
zdm7 is on oes2 sp3 and sles 10 sp3
HQ dhcp is on site A
and zdm imaging server is on site B (WAN)
Where I have configured ip-helper address for dhcp server on the router at site B.
setup before centralized dhcp.
zdm worked as dhcp server and proxydhcp for the site B, where in the novell-proxydhcp.conf was edited to contain LocalDHCPFlag = 1.
question: Do I also add the ip-helper addresse of proxydhcp server (HQ proxydhcp, which is zdm imaging server for HQ) in the router. or do I configure the router differently?
Hope I get a reply quick.
PilutakPilutakdahlnukissiorfiit,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/ -
Hi,
Is it advisable to use two ip helper-address in my network? And if possible how will set it up?
Thanks.John
I will take a different tack in answering your question than Arvind did. I will start by saying that whether it is advisable or not depends on your local situation and what set of requirements you are trying to achieve. Arvind's response is based on the assumption that you are forwarding to 2 DHCP server (which may or may not be the case). I worked, at one time, with a customer who was very concerned about providing redundancy and eliminating single points of failure. They deployed 2 DHCP server serving addresses for each subnet in their network. In that situation having 2 helper-address configured is possible AND desirable. (Arvind is correct that there is some additional overhead in having 2 DHCP servers for a subnet - but there is a trade off of overhead and the advantage of eliminating single points of failure, where would your organization be in balancing those aspects?)
And there is the situation to consider where the 2 helper-address may not be both for DHCP. Perhaps you have an environment where some devices send requests for TFTP to the local broadcast but the TFTP server is not on the local subnet. In that case you might have a helper-address for the DHCP server and another helper-address for the TFTP server. So you might have this configured:
! helper for the DHCP
ip helper-address 172.16.1.51
! helper for TFTP
ip helper-address 172.16.2.45
So - is it possible to have 2 helper-address configured? Certainly it is. Is it desirable to have 2 helper-address configured? That depends on your local situation.
HTH
Rick -
Unattended PXE boot? Envy laptop, FX-8800P Radeon 7 processor
I have a brand new laptop that I'd like to integrate into a Jenkins setup for running benchmarks. We have Clonezilla and an MS corporate license server. I want the Envy laptop to come up and do a PXE network boot. Clonezilla will serve it the right Windows image, optional driver(s) and Jenkins then applies and runs the benchmark. My first problem is in booting. I have found how to disable CD/DVD Rom boot, and the network boot, but not how to disable the local mass-storage boot. The environment I'm using has power switches and the conventional setup is PXE boot on power-up, but I can't find any controls in BIOS (f10) or boot menu (f9) to cause PXE boot on ppowerup. If I press F12 manually, PXE boot starts and runs for a while. Next problem, the images I'm restoring are made from "sda" and have "sda" in their names. My new laptop came with a disk named "HGST HTS541075A9E680" My new computer hasn't gotten "sda", so the network boot is rejected. I get a message telling me that I could use "CVNT-OCS-DEV to change the image file's name, but what do I change it to? HGST?" Very Best Regards!Bill
I have a brand new laptop that I'd like to integrate into a Jenkins setup for running benchmarks. We have Clonezilla and an MS corporate license server. I want the Envy laptop to come up and do a PXE network boot. Clonezilla will serve it the right Windows image, optional driver(s) and Jenkins then applies and runs the benchmark. My first problem is in booting. I have found how to disable CD/DVD Rom boot, and the network boot, but not how to disable the local mass-storage boot. The environment I'm using has power switches and the conventional setup is PXE boot on power-up, but I can't find any controls in BIOS (f10) or boot menu (f9) to cause PXE boot on ppowerup. If I press F12 manually, PXE boot starts and runs for a while. Next problem, the images I'm restoring are made from "sda" and have "sda" in their names. My new laptop came with a disk named "HGST HTS541075A9E680" My new computer hasn't gotten "sda", so the network boot is rejected. I get a message telling me that I could use "CVNT-OCS-DEV to change the image file's name, but what do I change it to? HGST?" Very Best Regards!Bill
-
PXE across subnets using IP Helper Address
For 10 years I have been trying to get my network engineers to add an IP Helper address of our SCCM PXE Server in order to provide an Enterprise PXE service for our campus (Large University). And every year they keep telling me
they won’t do it due to security concerns. I’m not exactly sure what they mean or what they are afraid of but I am looking for others who have been in this same situation and have been able to accomplish what has been a never ending exercise in futility for
me. I am looking for a white paper or a case study that I can use to help build my case and hope that someday I can convince our engineers that the world won't come to an end by adding IP Helper addresses... they won’t do it due to security concerns. I’m not exactly sure what they mean or what they are afraid of..
You need to get to the bottom of their specific concerns....
PXE involves the use of TFTP (to download the NBP + boot.sdi + boot.wim).
TFTP is neither robust/resilient nor particularly secure.
But I'm guessing that the concern must surely be more related to the payload/content (i.e. what is within the boot image itself) that might be the worry?
The boot image (potentially) contains licensed products (not directly a security concern), and certificates, accounts, passwords, scripts ?
If you have the F8 debug feature enabled in your boot image, it could be used to "live boot" a computer, access the filesystem on that computer, and basically provide uncontrolled access to the files/documents/data on that computer (assuming that your computers
are not using any form of disk encryption).
For this last reason, F8-debug should not remain enabled for "normal" operation.
In our organisation, we mitigate that risk with disk encryption. We also don't distribute boot media nor full media - PXE is the only way we deploy OS (well, outside of the datacentre, that is).
Our networking team were initially concerned about PXE - but not from the security aspect, more from the capacity/bandwidth perspective. So we worked with them to plan/design/place the boot servers, and the DP's placement.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!) -
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,
RonHi 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] -
New Dell Lat e6440 Laptop - no IP address when PXE boot w/ WinPE
PXE booting is working fine with all other Dell models. PE environment loads, OSD password prompt is displayed. Task sequences are displayed.
With just this model, Dell Latitude e6440, it gets to the point where we should be prompted for a password, hangs and then reboots. When I hit F8 and enter ipconfig it shows no ip address If I do ipconfig /renew i get "The operation failed as no adaptor
is in the state permissible for this operation." If I boot the computer into Windows (OOBE as shipped by Dell) it gets an IP successfully. I've updated our WinPE boot image with every network driver I can find from Dell for this model. Any other suggestions?
We are booting with a x86 WinPE wim file.
I have injected the latest kernel mode driver framework into our WinPE wim used for PXE boot.Hi,
Any useful information in smspxe.log?
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
This morning came in to find clients were not getting there bootfiles through PXE. I checked the logs to find the following events related to WDS.
The Open Procedure for service "WDSTFTP" in DLL "C:\Windows\system32\wdstftp.dll" failed
The Open Procedure for service "WDSServer" in DLL "C:\Windows\system32\wdssrv.dll" failed
The Open Procedure for service "WDSMC" in DLL "C:\Windows\system32\wdsmc.dll" failed
Has anyone seen this or have a link to a resolution?
tconnersHotfix loaded but didn't help.
Found a few articles referring to rebuilding the perf counter library. I ran "lodctr /R" failed first time then worked the second time. I believe the errors:
The Open Procedure for service "WDSTFTP" in DLL "C:\Windows\system32\wdstftp.dll" failed
The Open Procedure for service "WDSServer" in DLL "C:\Windows\system32\wdssrv.dll" failed
The Open Procedure for service "WDSMC" in DLL "C:\Windows\system32\wdsmc.dll" failed
Are gone but PXE boot still fails.
Do you think I might have to uninstall WDS and reinstall? "Using SCCM console to just remove PXE"
tconners -
T61s, T60s & older model unable to PXE boot to SCCM (MAC address problem)
Hi,
We have a series of T60, T61 & older machines that are unable to PXE boot to SCCM. The T400 & X series & other newer models can boot just fine.
After checking further, we realised that only a certain range of MAC addresses are unable to pxe boot i.e
00-1A-XXXXXXX
00-1C-XXXXXXX
range.. all the other range of MAC addresses are fine to boot via network.
The error when doing network boot is "bad or missing discovery server list"
Also, we are running on SCCM 2012 at the moment. Our branch office who is running SCCM 2008 can have all the machines - regardless of models & brand boot just fine.
Any ideas? Much appreciated.did it obtain IP address from DHCP server? is DNS server address is configured in DHCP scope? can you ping using IP address?
if drivers are proper will suggest to update it in boot media & enable command line support to make it easy for deployment & troubleshooting.
Prashant Patil -
Policy retreiving for client that is pxe booting
Wanna ask, to which management point server does a client will retrieve its policy prior to executing the TS? Does it based on the ip address boundary range?
Which logfile I can see to reoubleshoot client pxe issue? is it smspxe.log?Short answer is: it doesn't. But we have to break down what's happening.
Remember when you PXE boot you are actually operating at Layer 2 still, and the WDS services are answering a broadcast. So no MP enters the picture before a TS runs _at_all_, instead it's the Distribution Point (which controls the WDS/PXE services
in 2012) that is connecting to the client and providing the TS.
You can actually see this happening on the SMSPXE.log (I'm going from memory on the log name, sorry if i got it wrong) in the SMS_DP$\sms\logs when the PXE servive gets the mac, matches it against the DB then provides the TS available.
Again we are basically doing this at layer 2, even though the client will eventually get an IP and use said IP to TFTP download said image...
More depth here:
http://blogs.technet.com/b/pingpawan/archive/2014/01/12/deep-dive-pxe-boot-flow-for-sccm-2007-2012.aspx
EDIT: to speculate on your question a bit: so if there are multiple DPs in the same subnet, or there is possibly IPHelper in the picture in some way ... the DP that answers is basically random unless a response delay is set (can be done on the DP in
in the MMC). -
MDT boot image and when we try to PXE boot it won't get the IP Address.
We created a custom MDT boot image and when we try to PXE boot it won't get the IP Address.
I press F8 and type IPCONFIG we get Windows IP Configuration. We are using vmxnet3 network adapter.
I think I need to inject 32-bit vmxnet3 driver to the custom MDT boot image which is 32-bit.
We are using it to deploy Windows Server 2008 R2 with SP1 operating System.
Can I just use the 32-bit custom MDT boot image or do I need to use 64-bit Custom MDT Boot Image?
Also Is there a blog on how to inject vmxnet3 driver to boot image?You can try this:
http://mwesterink.wordpress.com/2013/12/03/configmgr-2012-obtaining-vmxnet3-nic-drivers-for-vmware-virtual-machines/
Honestly, your best bet is to use a different adapter (E1000). I personally have had no luck getting the vmxnet3 driver to work properly in WinPE. It's either really, really slow or it simply doesn't load at all. -
OSD: pxe boot fails with "failed to get infromation for MP:/"
Hi,
We face an issue on pxe boot. It boots into pxe then tries to apply network settings but then reboots.
Ipconfig is ok, smsts.log says "failed to get information for MP:/oursccmserver.
Troubleshooting:
*PXE is working fine when client as well as sccm-server are in same subnet, it fails when in different subnets.
*Firewall is fully opened, no connections blocked.
*Ping to sccm-server works fine on dns
Please advise.
J.
smsts.log:
Missing root CA environment variable from variables file TSPxe 26/03/2014 16:37:11 288 (0x0120)
Support Unknown Machines: 0 TSPxe 26/03/2014 16:37:11 288 (0x0120)
Custom hook from X:\\TSConfig.INI is TSPxe 26/03/2014 16:37:11 288 (0x0120)
No hook is found to be executed before downloading policy TSPxe 26/03/2014 16:37:11 288 (0x0120)
Authenticator from the environment is empty. TSPxe 26/03/2014 16:37:11 288 (0x0120)
Need to create Authenticator Info using PFX TSPxe 26/03/2014 16:37:11 288 (0x0120)
Initialized CStringStream object with string: {40AB3050-A926-4BA5-9D17-7423F93CBCD5};2014-03-27T00:37:11Z. TSPxe 26/03/2014 16:37:11 288 (0x0120)
Set media certificate in transport TSPxe 26/03/2014 16:37:11 288 (0x0120)
Set authenticator in transport TSPxe 26/03/2014 16:37:11 288 (0x0120)
CLibSMSMessageWinHttpTransport::Send: URL: oursccmserver.ourcompany.com:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONMEDIA TSPxe 26/03/2014 16:37:11 288 (0x0120)
[TSMESSAGING] AsyncCallback(): ----------------------------------------------------------------- TSPxe 26/03/2014 16:37:11 288 (0x0120)
[TSMESSAGING] AsyncCallback(): WINHTTP_CALLBACK_STATUS_SECURE_FAILURE Encountered TSPxe 26/03/2014 16:37:11 288 (0x0120)
[TSMESSAGING] : dwStatusInformationLength is 4
TSPxe 26/03/2014 16:37:11 288 (0x0120)
[TSMESSAGING] : *lpvStatusInformation is 0x8
TSPxe 26/03/2014 16:37:11 288 (0x0120)
[TSMESSAGING] : WINHTTP_CALLBACK_STATUS_FLAG_INVALID_CA is set
TSPxe 26/03/2014 16:37:11 288 (0x0120)
[TSMESSAGING] AsyncCallback(): ----------------------------------------------------------------- TSPxe 26/03/2014 16:37:11 288 (0x0120)
WinHttpReceiveResponse (hRequest, NULL), HRESULT=80072f8f (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,8927) TSPxe 26/03/2014 16:37:11 288 (0x0120)
failed to receive response with winhttp; 80072f8f TSPxe 26/03/2014 16:37:11 288 (0x0120)
m_pHttpTransport->Send (0, 0, pServerReply, nReplySize), HRESULT=80072f8f (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,5159) TSPxe 26/03/2014 16:37:11 288 (0x0120)
MPKeyInformation.RequestMPKeyInformationForMedia(szTrustedRootKey), HRESULT=80072f8f (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,9410) TSPxe 26/03/2014 16:37:11 288 (0x0120)
Failed to get information for MP: http://oursccmserver.ourcompany.com. 80072f8f. TSPxe 26/03/2014 16:37:11 288 (0x0120)
Jan HoedtHi,
Have you check Mpcontrol.log on the MP server and Smspxe.log?
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
I am taking over OSD for an SCCM 2007 R2 environment, existing Operating System Images have been created (Win 7 x64), Boot.wim images, drivers, etc and it all works fine for existing models of PCs. A NEW model of machine has been purchased and
is being deployed that we need to PXE OSD but the NIC drivers for this machine we're not loaded. I followed the MS KBs to obtain and extract the correct driver INF files from the vendor site to the drivers folder on the SCCM network share, add the
drivers in configman console, update the driver package, edit the task sequence and update the WIM image. Everything went successful (assuming that's all that needs to be done). However, when I PXE boot one of these new machines out of the box
I get the following error during boot after pressing F12: Pending request ID: 5306 contact your administrator (which sadly is me now). when this error passes, the splash screen loads and then I get a no NIC drivers error. I cant seem to locate
a 5306 error code message, can anyone help or provide any insight? Thanks,Apologies, my fault. I'll describe this as best as I can based on what I know/have in front of me. This is a pre existing environment successfully doing OSD via PXE with existing hardware and images, I'm simply adding a new HP model and
need to add the drivers for this new model so I can PXE this like the rest. Within the console (2007 R2) beneath 'Operating System Deployment' there is 'Boot Images' which has the x86 and x64 boot images which they are using. Beneath 'Operating
System Images' there are Win 7 x64 images (I'm using the one with the most current date) Beneath 'Drivers' are all the existing NIC drivers and this is where I imported the new HP NIC driver I downloaded for the new HP Model machines we bought.
The drivers (extracted INF etc) are in the SCCM server 'DRIVERS' folder on the server where all the other drivers are, I added this driver to the x64 BOOT Image noted above, updated all DPs. Beneath 'Driver Packages' I also created a new package
for this new driver the same as all the existing ones are. So in terms of steps, I've obtained the new 64 bit NIC drivers and copied them to the LAN, updated the drivers, created the driver package, updated the task sequence, updated
the driver to the .wim boot image, updated all DP's. So assuming I've done all the above correctly and not missed anything, when I boot up the new machine and do an f12, it craps out and I get the 'aportpxe' error followed by NIC driver not found
when the wim is loading.
Appreciate your patience and any assistance. -
I own a MacBook Pro 2.4 ghz non unibody. I turn on my laptop for ten seconds and it freezes. It boots perfectly and runs for ten seconds until everything freezes. Please help!
See if you can boot into single user mode with Command S.
-
I am trying to use my usual e-mail address for Cloud but it is not being accepted. Any help?
I understand that I can use my usual e-mail address for Cloud but when I enter it, it is not accepted. Any ideas why?
Hi gms12286!
This article should be able to help you achieve this goal:
Apple ID: Changing your Apple ID
http://support.apple.com/kb/ht5621
Thanks for coming to the Apple Support Communities!
Cheers,
Braden
Maybe you are looking for
-
win7 Pro. has been running firefox ok. but lately with 25 and now 26, the firefox won't start. I can see firefox is running in task manager. but it just won't pop up. if I download it again and install it, it will run, but every time I reboot the sys
-
Hi Folks, We are working on Payment Release workflow in AR module. Once the invoice is posted, workflow is able to block the payment, but not sending mails to the agent for approval. For testing, i have entered a dummy user
-
Print Layout Difficulties - printing in landscape mode
Haven't upgraded to Pages 2 yet; in the meantime, here's a question related to Pages 1: How does one properly print in landscape mode directly from Pages? I'm trying to print a simple CD booklet, but all I get when printing directly from Pages is my
-
Why does my powerbook screen look inverted(256 colors)
when I powered off my PB after it locked up and re started it goes to the mac OS blue screen and starts loading normally,then all of a sudden it goes goes grey and inverts all images loading on the desktop. When I check the displays screen under syst
-
I get the following error message when I connect a usb ethernet adapter to my new MacBook Pro: Unsupported - You cannot use an Apple USB Modem with this computer. I live where we only have dial-up and the Apple Store said this is what I need. In addi