Looing for PXE-Boot option on T430s

Hello
I am in the process of testing a Thinkpad T430s to possibly do a mass purchase for our company. We use SCCM
to manage imaging, patching / updates etc. I am trying to PXE boot but but I am getting an error which may have to do with
SCCM but as an extra measure I am trying to locate PXE Boot option in the BIOS but can't seem to find anything.
ANy suggestions would be appreciated

do you see Wake On Lan and/or Ethernet LAN Option ROM on the Network menu under the Config tab in your BIOS.
apologies if you don't. all i've got to check is my X220 in front of me, at the moment.
regards.
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество
Community Resources: Participation Rules • Images in posts • Search (Advanced) • Private Messaging
PM requests for individual support are not answered. If a post solves your issue, please mark it so.
X1C3 Helix X220 X301 X200T T61p T60p Y3P • T520 T420 T510 T400 R400 T61 Y2P Y13
I am not a Lenovo employee.

Similar Messages

Server 2008 configured for PXE boot with UIU and GhostCast

Right now, I am in the process of switching over from UIU 4, to UIU 5, and the implementation is completely different. We used GhostCast to push images out before, but the new UIU uses WIM files to pull the drivers off the server. I had a few
questions about reconfiguring the new server.
Currently, we have a server 2003 machine running ghost cast. It pulls its images off of a server 2008 machine. The server 2008 machine can be accessed remotely. So my first question is, can this be configured to allow remote connections
with the new setup?
The things I have been reading have said that you need to enable DNS, AD, and DHCP, however if we connect this to a WAN, will it conflict with that? Or can we configure only one of the ethernet ports to see this? Sorry kind of new to this.
I guess my main concern is, can we set up a separate domain for GhostCasting, while still being connected to an external domain?

Hi,
I’m not sure what you really want to do. For PXE boot, I think DHCP is always required just like Microsoft deployment solution WDS and MDT.
The two products are third products, so I don’t know the detail information about how they work. Based on my experience, they should be based on broadcast or multicast.
If so it could be a bad idea if you install it on a server facing the internet.
I think you can also ask in the third party forums that provide the products.
Thanks for understanding.

Capturing an image to use for PXE boot

I'm using Windows Deployment Services in conjunction with Windows Deployment Terminal (Windows Server 2008) to capture an image from one of our workstations to use as a PXE boot image for future computers. I've created the capture image and PXE booted
to that image, which brings up the "Image Capture" wizard. After capturing the image, I created an install image in WDS using the same .wim file. After trying to PXE boot, the workstation yet again brings up the "Image Capture" wizard.
I then right clicked the image under Boot Images (in WDS) and selected "Create Discover Boot Image." A loading window pops up, but always ends with an error saying something to the extent of the image doesn't have WDSClient Binaries. Does anyone
know what this is or how to fix this? Or even if I'm going about it the right way? If anyone has any advice, I'd appreciate it.

Hi,
Yes, you can.
Here are the rough steps:
1.
Install and configure the WDS Server.
2.
Add the Windows 7 boot image to WDS.
3.
Create a Capture Boot Image and add it to Boot Image.
4.
Create a reference Windows 7 computer (install Windows 7, Office and other applications as you like)
5.
Sysprep the Windows 7 computer.
6.
PXE boot the reference Windows 7 computer into capture image on the boot screen and then capture the image.
7.
Upload the captured image to WDS server.
8.
PXE boot clients, choose the captured image to install the system.
Please refer to this link
http://social.technet.microsoft.com/Forums/windowsserver/en-US/be3af7db-b71b-4b14-b166-fef83cde0ac6/deploy-windows-7-from-waik-with-some-application-added?forum=winserversetup
I had the similar problem couple of years back
UMESH DEUJA MCP,MCTS,MCSA,CCNA

Yoga 13 - Compatible USB to ethernet devices for PXE booting

Hi there,
I've recently been looking for a means to pxe boot the lenovo yoga 13 to enable me to then image it. After reading that pxe booting is possible I went out and bought a StarTech usb to ethernet adaptor (USB21000S2) but have had no luck so far.. In other postsI've read that pxe booting is only supported if using the official lenovo usb to ethernet adaptor. We're using FOG as our imaging solution (if thats of any use)
Please can someone confirm if only the official adaptor is supported.
Regards
Simon

Were you able to find any? I am also very interested in finding one. I just ordered one of these the lenovo 0A36322 to see if it will work, but it is only 100mb and not sure if it will work or not.

Issue getting WDS to Install for PXE in SCCM 2012 SP1 Primary Site

Hi All
I'm trying to get PXE boot working from our SCCM 2012 box but it never actually gets to the point of installing WDS when I check the box for PXE booting. I don't have SMSPXE.log since it never gets to that point and the distmgr.log never reaches
that point either. I've tried
uncheck pxe boot option - restart - re-check
uncheck pxe-boot - restart - install wds - leave it unconfigured - reboot - check pxe boot
uncheck pxe-boot - uninstall the vcredist 2008 packages - rebooting - install vcredist - check pxe boot option
the above with installing wds unconfigured
Below is the relevant portions of the distmgr.log file after I enable the pxe boot option no matter what manner of software is installed. We are running it on a VM in a Hyper-V 2012 enviornment in Windows 2008 SP2 x64. This issue is similar to this link
WDS PXE Secondary Site Issues but mine is on the Primary Site.
ConfigureDP SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:09 AM 4008 (0x0FA8)
DP registry settings have been successfully updated on TUSC2012.TALISKERUTAH.LOCAL SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:10 AM 4008 (0x0FA8)
STATMSG: ID=9500 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TUSC2012.TALISKERUTAH.LOCAL SITE=001 PID=2728 TID=4008 GMTDATE=Thu Mar 28 17:48:10.083 2013 ISTR0="["Display=\\TUSC2012.TALISKERUTAH.LOCAL\"]MSWNET:["SMS_SITE=001"]\\TUSC2012.TALISKERUTAH.LOCAL\" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\TUSC2012.TALISKERUTAH.LOCAL\"]MSWNET:["SMS_SITE=001"]\\TUSC2012.TALISKERUTAH.LOCAL\" SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:10 AM 4008 (0x0FA8)
STATMSG: ID=9503 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TUSC2012.TALISKERUTAH.LOCAL SITE=001 PID=2728 TID=4008 GMTDATE=Thu Mar 28 17:48:10.084 2013 ISTR0="["Display=\\TUSC2012.TALISKERUTAH.LOCAL\"]MSWNET:["SMS_SITE=001"]\\TUSC2012.TALISKERUTAH.LOCAL\" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\TUSC2012.TALISKERUTAH.LOCAL\"]MSWNET:["SMS_SITE=001"]\\TUSC2012.TALISKERUTAH.LOCAL\" SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:10 AM 4008 (0x0FA8)
ConfigurePXE SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:10 AM 4008 (0x0FA8)
CcmInstallPXE SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:10 AM 4008 (0x0FA8)
RegQueryValueExW failed for Software\Microsoft\SMS\DP, PxeInstalled SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:10 AM 4008 (0x0FA8)
RegReadDWord failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:10 AM 4008 (0x0FA8)
Running: C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist_x64.exe /q /l C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist.log SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:10 AM 4008 (0x0FA8)
Waiting for the completion of: C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist_x64.exe /q /l C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist.log SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:10 AM 4008 (0x0FA8)
Run completed for: C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist_x64.exe /q /l C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist.log SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
Created the DP mutex key for WDS. SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
Finding Wimgapi.Dll SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
GetFileAttributesW failed for SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
FindWimgapiDll failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
Running: msiexec.exe /quiet /i c:\program files\microsoft configuration manager\wim\wimgapi.msi /log c:\program files\microsoft configuration manager\wim\wimgapi.log SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
Waiting for the completion of: msiexec.exe /quiet /i c:\program files\microsoft configuration manager\wim\wimgapi.msi /log c:\program files\microsoft configuration manager\wim\wimgapi.log SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:29 AM 4668 (0x123C)
Created policy provider trigger for ID 16777217 SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:29 AM 4656 (0x1230)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:34 AM 4668 (0x123C)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:39 AM 4668 (0x123C)

HI again, sorry for the late reply.
By saying that WDS don't get configured, I mean that when i enabled the PXE functionality, the WDS role got installed but the folder remote install wasn't created.
I ahve now actually gone back to an earlier snapshot from before I started play with the PXE settings of the VM and now nothing happens when activating PXE on the distribution point, but not even the smspxe.log is created.
The Account used is a local admin and the distribution point is located on the primary site server.
EDIT: in the events log, it states the following:SMS_SITE_COMPONENT_MANAGER on computer XXX.XXXX.XXX reported: SIte comoponent Manger failed to to install on this site system.
On error (source: MsiInstaller) below:
Product Application Web Service -- Internal Error 25001. 80070490
I havent mentioned it earlier, but the Server OS is Server 2012.
I hope this might help you help me :)

Does SCCM 2012 R2 supports PXE boot from Unix servers.

Does SCCM 2012 R2 supports PXE boot from Unix DHCP servers.
The client has DHCP on Unix servers. There are no Windows DHCP servers in the environment. Do we need Windows DHCP server for PXE boot.

You can use any modern DHCP server in your environment. DHCP is just used to help point the BIOS/Network Card to the right server, which in this case is your ConfigMgr Distribution Point with PXE Enabled.
It is strongly recommended to use IP Helper Addresses instead of the DHCP options though.
I hope that helps,
Nash
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
If you found a bug or want the product to work differently,
share your feedback.
<-- If this post was helpful, please click the up arrow or propose as answer.

Pxe boot hp mini

We have quite a few HP Mini 1101's that need imaging. I can't see how to set the bios for pxe boot. Any help out there?
Bios is American Megatrends ver F.16
Thanks

korpx,
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://support.novell.com/forums/

No boot option after Windows 7 install on Mac Pro

Hi,
I have problem and it is very frustrating.
My configuration
Mac Pro 1.1 2x2.66
RAM 5 GB
HDs
Bay1 500GB (have a Mac OSx 10.6)
Bay2 250GB (install Windows 7 Ultimate 64bit)
Bay3 250GB (in raid Mac OSX 10.6.6) primary system
Bay4 250GB (in raid Mac OSX 10.6.6)
I have install Windows 7 via Bootcamp from system 10.6.6 and format and install Windows 7 on HD in Bay2. After installation I try to choose which operating system I want to run (with option key) but nothing happen.
It was grey screen without apple logo and system boot to Windows 7 only.
I try everything to boot with different options (key shift,x,c,...) but nothing happen. I can only boot with windows 7 and if is the windows 7 DVD in drive first ask to boot with DVD, after that boot on Windows 7.
I try to put Mac OS system DVD but still don't want to run.
I also try to remove HD from Bay1(macosx) and Bay2 (windows7) and boot from Raid HD and I have error that there is no boot system.
In windows 7 I run Paragon HFS+ and I can see HD500 in Bay1 but cant see in Bay3 and 4 (RAID hd). In disk utility I can see all hard drives.
I try to reset PRAM but while booting what ever I press nothing happens and boot only windows 7.
I need solution for this problem, please help me with this issue, thx

Another thing that might be close...
I've installed Win7 64-bit on a second HDD. It is Ok to choose boot with 'option' key, but another option is missing: while in win7 apple's bootcamp control panel shows both MacHD and Win7 bootable partitions, so I can tell 'software way' to boot to win or to Snow Leo. It's OK. However when I open 'startup disk' in OS X there's only Mac HD so if I need to reboot to windows I can't just do it with several clicks. I actually have to shut down OS X, wait for boot screen, press option and then wait for the boot options to appear and them choose. It's 'a bit' annoying, let alone windows version of bootcamp seems to do the job smarter. And it really is a good thing to choose "reboot into desired OS" with a click and go to kitchen for tea or something and not seat in front of the machine waiting for boot screen...
Am I missing something? Is it done the other way then 'system preferences>startup disk'?

Pxe-boot uses wrong filename

Hello,
I have a working setup for pxe-boot.(testet with my Desktop).
My DHCP-Server supplies as filename "pxelinux". My new Thinkpad S531 is unable to boot.
The log of my tftp-server shows, that my TP adds a sign at the end of the filename on request, and of couse,
my tftp-server is unable to find that file.
The added sign ist not from the alphabet, so I cant put it in here. If I change the filnename on my "filename"-diretive of my dhcp-server p.e. to "pxelinux.0" an other sign is added to the filerequest of my TP.
Secure boot ist off.
Is this a bug in my efi?
Thanks for reading

Thanks to both for replies. Correcting the default boot order was easy but getting the internet connection to work took a little longer. I solved it by changing the device name as suggested here:
https://wiki.archlinux.org/index.php/Ne … evice_name
There was nothing in /etc/udev/rules.d so I created the file 10-network.rules and used the enp2s0 device name which was working with the older kernel.
I'm still wondering why this mixup happened in the first place but anyway, it's working now so many thanks for your replies.

SCCM 2012 PXE boot

Hi All,
I have some weird issue in which i am trying to image Esprimo C720 desktop.
It is working perfectly fine if i create a standalone image via USB and build it.
But when i try to PXE boot the same device, it takes ip and boots up after windows screen it restarts. I thought it wud be network drivers and i have updated the same in winpe but still it doesnt work.
I feel Esprimo C720 is not supported for PXE boot. Can any one advice me if you wud have come across this issue
Regards, Pratap

Hi,
I recommend you check the log file smsts.log.
This can be found in one of several locations depending on the progress of the build and the architecture of the OS:
Windows PE before HDD format: x:\windows\temp\smstslog\smsts.log
Windows PE after HDD format: x:\smstslog\smsts.log and copied to c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
Full version Windows before SCCM agent installed: c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
Full version Windows after SCCM agent installed: c:\windows\system32\ccm\logs\Smstslog\smsts.log
Full version Windows (x64) after SCCM agent installed: c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log
After Task Sequence has finished running: c:\windows\system32\ccm\logs\smsts.log
After Task Sequence has finished running (x64): c:\windows\sysWOW64\ccm\logs\smsts.log
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.

EliteBook 8460p "factorycontrolcommand set: 5 "Pxe boot enabled, wwan override mode""

A message appears on screen during post "factorycontrolcommand set: 5 "Pxe boot enabled, wwan override mode"".
What does it mean, how can I fix it, please help! I disabled pxe boot option in bios, but it doesn't help!
This question was solved.
View Solution.

Bios update solved the problem. Thanks to hp instant support!!!!

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.

DHCP Scope Options for PXE on swtiches

Hello,
I am trying to get PXE support for OSD in a sccm 2012 environment.
WSD resides on the same server as my SCCM 2012 Primary server.
I currently have one dp with PXE enabled.
My networking team asked what I needed for PXE support.
I responded:
DHCP discover package contains option 60
DHCP discover uses port 67 UDP
DHCP Offer uses port 68 UDP
Server ack from PXE server including options 66 and 67
Client unicast request for options 66 (boot server) and option 67 (boot file) (port 4011 UDP)
They responded with what do I need from below
The above response
was from a different job and location. Now they are asking for info on boot file and hostname. Hostname I would think be the dp or in our case, the sccm primary server. The boot file, I have no idea
Thanks so much for your help,
Mark

Ok, networking agrees to use IPhelpers, but needs "official documentation" of exactly what to do. Does anyone have a link that I may give to network to use. I really do appreciate it. I never thought I would have to do the network
part for them. :(
Thanks,
Mark
The general gist is that your router interfaces need to relay/forward bootp/dhcp "discover" & "request" to *both* your DHCP and your PXE-enabled DP.
This will cause the DHCP-client's discover/requests to be relayed to both, but the PXE-enabled DP won't respond to the initial discover/request because it can't issue IP addresses.
But once the client *does* have an IP address, and it issues a PXE request, the PXE request will be relayed to both, the DHCP server will ignore it but the PXE-enabled DP will process it and offer the NBP and then the TFTP of the boot image etc.
This is recommended/preferred over using DHCP options 66/67.
It's recommended in lots of places, but here's a great reference:
http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2011/10/14/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx
For "official documentation" on how to configure the router, the router manufacturer will help with that.
Cisco refer to their implementation as "ip helper-address", which is why the feature is often referred to as "iphelpers".
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/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?

A friend bought second hand macbook air mid 2011 with crossed circle on the display, we tried recovery from partition and same thing happened, after internet recovery it stays the same except now it asks for password for boot option, what happened?

A friend bought second hand macbook air mid 2011 with crossed circle on the display and give to me to try to recover the system, I tried recovery from partition and same thing occured, after internet recovery it stays the same-crossed circle after reboot, then we tried to boot from USB with mac os 10.8 on it, it installs something,like it has being finishing installation, rebootes, and now it asks for password for boot option.We have no idea what that password could be.What happened!!!

I forgot to write down my computer specs:
iMac 27 Mid 2011
2.7 GHz Intel Core i5
4 GB 1333 MHz DDR3
AMD Radeon HD 6770M 512 MB
OS X 10.9.2

Looing for PXE-Boot option on T430s

Similar Messages

Maybe you are looking for