W530/T530 PXE boot problem again

Our latest W530s and T530s won't load the OS off the PXE server
Previously, we only had to set the bios as discussed here
http://forums.lenovo.com/t5/X-Series-Tablet-ThinkPad-Laptops/Can-t-PXE-boot-Windows-8-models/td-p/98...
Under Security, we turrn Secure Boot off
Under Startup, we st UEFI/Legacy Boot to both with legacy first and CSM on
Under restart, we turn the OS Optimized defaults off
That's been working for months.
Now, the W530 (and T530) find the PXE server, we select the remote boot options, and it just hangs before (or as) it loads the boot.wim
No error message, it just sits there.
Has anyone else experienced this? Is there some sort of bios upgrade that caused this?
Thanks.
Solved!
Go to Solution.

We are aware of the problem with LANDesk but I don't have any fix outlook. You can get previous BIOS versions from the download page:
http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS029170
Scroll to the bottom and you'll see all the previous versions. Note that to downgrade to a previous version you need to disable rollback prevention which is an option in BIOS Setup (look in the Security -> UEFI BIOS Update Option menu)

Similar Messages

PXE Boot Problem

Hello everyone!
I've got a PXE boot server running and I can boot my EEE 701 from it without issue, it gets to the installer but then I get asked for the source of the packages. Now, I don't have an Internet connection to the boot server, so that's not an option. I know I can mount something to /src to have the packages show up, but what am I supposed to mount, and where?
Thanks in advance!
P.S: If you're considering "rtfm" or "Google" as a response as some did on the IRC, don't bother wasting your time to type
I mounted a USB stick with all the packages on to /src (I knew that had to be done) but I thought perhaps the installer would have mounted the packages from the tftp server to /src automatically. So now I don't understand the point of the separate installer CD?
Last edited by scottuss (2009-12-17 12:44:55)

hokasch wrote:
Hmm, do you mean the one from here? If so, it says "ftp-installation only", but I maybe should have made that more clear. I planned support for mounting packages from the tftp-server later (you need to set up nfs for that), but never picked it up again.
It is stitched together rather imperfectly, I just made it because there was no other way of getting an install on an old laptop.
I've totally gone around the houses
yeah, you could just have booted from an usb-stick, right?
Actually no! I had problems with that (although I've done it before) I got an error: "Boot device didn't show up after 30 seconds" and the workaround(s) at http://bbs.archlinux.org/viewtopic.php?id=77815 didn't help, so I figured I'd try the PXE boot.
Look, I'll be straight, I use Arch on an old box as a testing / development server for odd jobs. I left Arch as a desktop user a long time ago for Ubuntu where things "just work" - I don't have time to fix things constantly breaking on my main desktop. I thought I'd give Arch another go as a desktop OS on my EEE but I don't have the time (or inclination) to mess around with it anymore.
Ubuntu is installing from a USB stick as we speak.
Don't get me wrong: I LOVE Arch, as a headless, non-important playing around OS, I don't think I'll be using it as a desktop
P.S: Using Ubuntu has NOTHING to do with the skill level of anyone who chooses to use it. I HATE elitism! (rant over!)
Last edited by scottuss (2009-12-17 15:08:40)

W530 cannot PXE Boot

I have just received a number of W530 that i need to configure with a new OS Image. They try to boot from LAN into PXE boot but finds no DHCP server.
I use a network cable that has been verified to give IP addresses from the DHCP server to other devices.
Any suggestions ?
Solved!
Go to Solution.

"our average home hardware router will 100% not work. Quite a few high-end home routers will not work. The PXE client has to receive an additional DHCP option that 99% of the routers you've seen do not support. I can't say I've ever touched a Cisco router, but chances are decent that it'll support PXE booting. Read the next section for a little more detail as to why. For a list of hardware that has what's needed to do PXE booting, see PXE Capable Hardware. "
Taken from: http://pxe.dev.aboveaverageurl.com/index.php/PXE_Booting
Read more there.

PXE boot problem: guest VM DHCP request packets not able to reach DHCP server

Hi Gurus,
I'm wondering if anyone could help me with this problem. I wanted to install Linux on Oracle VMs using PXE. I set up a DHCP server and the OVM running RHEL6.4 box. The DHCP server worked fine since other PHYSICAL servers could get IPs from this DHCP server. However, DHCP requests from Oracle VMs was not able to reach the DHCP server. So I suspect this is a VM-specific issue.
If I type in "dhcp net0" on gPXE prompt on the OVS machine(sappire), I can see the requests were being sent from the OVS server (sapphire):
gPXE> dhcp net0
DHCP (net0 00:21:f6:00:00:00) .............................................Connection time out (0x4c106035)
Could not configure net0: Connection time out (0x4c106035)
gPXE>
[root@sapphire ~]# tcpdump -i any -n udp dst portrange 67-68
tcpdump: WARNING: Promiscuous mode not supported on the "any" device
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
20:47:25.606400 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:21:f6:00:00:00, length: 387
20:47:25.606549 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:21:f6:00:00:00, length: 387
20:47:25.606559 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:21:f6:00:00:00, length: 387
^C
12 packets captured
14 packets received by filter
0 packets dropped by kernel
But if I snoop the same on the RHEL6.4 server running DHCP server and OVM, no request can be seen:
[root@bluestone Desktop]# tcpdump -i any -n udp dst portrange 67-68
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
^C
0 packets captured
0 packets received by filter
0 packets dropped by kernel
OVS(sapphire) and OVM(bluestone) are located in the same subnet:
[root@bluestone network-scripts]# ifconfig -a
eth0      Link encap:Ethernet HWaddr 00:14:22:72:7C:27
          inet addr:192.168.2.48 Bcast:192.168.2.255 Mask:255.255.255.0
          inet6 addr: fe80::214:22ff:fe72:7c27/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:106795 errors:0 dropped:0 overruns:0 frame:0
          TX packets:122056 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:59173975 (56.4 MiB) TX bytes:25362955 (24.1 MiB)
[root@sapphire ~]# ifconfig -a
10049df2fc Link encap:Ethernet HWaddr 8A:C5:05:83:AF:C9
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:80 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:33200 (32.4 KiB) TX bytes:0 (0.0 b)
eth0      Link encap:Ethernet HWaddr 00:1A:64:64:DA:64
          inet addr:192.168.2.202 Bcast:192.168.2.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:37664 errors:0 dropped:0 overruns:0 frame:0
          TX packets:38939 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4537897 (4.3 MiB) TX bytes:23127790 (22.0 MiB)
eth0:0    Link encap:Ethernet HWaddr 00:1A:64:64:DA:64
          inet addr:192.168.2.212 Bcast:192.168.2.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
[root@sapphire ~]# brctl show
bridge name    bridge id        STP enabled    interfaces
10049df2fc        8000.8ac50583afc9    yes        tap7.0
                            tap7.1
                            vif7.0
                            vif7.1
I turned off iptables and SELinux on the DHCP server, the issue still remained.
Any help will be highly appriciaited.
Thanks in advance,
Alex

Hi,
- Do you install Oracle VM Server (OVS) on an emulated environment like Oracle VM VirtualBox ? if yes so you can't do it.
- Don't forget to configure the Virtual Machines Network and also to add this network to this Virtual Machine.
I hope this can help you
Best Regards

Wds pxe boot problem

I tried to deploy remote os installation from wds on intel D915GAV board which has no builtin NIC, so first i install TP-Link Nic on one of PCI slot and add this NIC driver to Boot.wim on wds but still no booting from wds ............ pls help me anyone
thanks

yes already checked that firmware upgrade and PXE has enabled.............. i also try TP Link NIC in Intel DG41RQ board but same no booting from wds and error appear for media failure check cable etc. while on DG41RQ builtin NIC it boot from same wds

E540 PXE Boot problem

Hi ;
I just buy lenovo E540 and when I try to upgrad windows 7 to windows 8 which on cds that i get with the lap
i get this error message when i turn my laptop on intel
UNDI PXE-2.1 (build 083) Copyright (C) 1997-2000 This product is covered by one or more of the following patents:US5, 307, 434, 872, US5, 732, 094, US6, 570, 884, US6, 15, 776 AND US6, 327, 625 Realtek PCle FE Family Controller Series v1.23 (07/28/10) PXE-MOF: EXITING PXE ROM.
and plz I need contect number of custermer server in Egypt ..
plz I need help as fast as possible casue I have an assigmet to deliver plz
Moderator Note; subject edited

If you received the Windows 8 discs with the system from Lenovo there will be some instructions included on how to use thos discs and and changes which you may be required to make in BIOS before using them. The same or similar to these;
http://download.lenovo.com/pccbbs/options/en_sp40e37996.pdf
How to contact support; http://support.lenovo.com/en_GB/feedback/detail.page?LegacyDocID=MIGR-76613
Andy ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
Deutsche Community Comunidad en Español English Community Русскоязычное Сообщество
PepperonI blog

"Welcome to the Task Sequence Wizard" never shows on PXE boot, but does on Boot Media with prestart command

Hey guys, I have a fairly odd situation here. I have all OSD Task Sequence advertisements set to "PXE and Boot Media (hidden)" and all are optional
(not mandatory). I use a powershell form via prestart command to give the user a choice which limits what task sequences they choose. When everything is working, this process works. Unknown desktop-class systems see desktop task sequences,
and server-class systems see server task sequences.
Here's where it's different when I use different boot methods:
Boot Media
"Welcome to the Task Sequence Wizard" is presented. User hits or clicks Enter.
Powershell form is presented; user picks their task sequence
Confirmation screen is presented with the task sequence they selected (this is an OSD screen the same size as the "Welcome to the Task Sequence Wizard"
screen.
Dependency check screen is shown with a progress bar. If a package is missing from a DP, it will display an error here with the PackageID. This
looks the same as "Regular" OSD with standard non-hidden advertisements.
PXE Boot
"Welcome to the Task Sequence Wizard" is never displayed.
Powershell form is the first screen they see. They select it and it continues.
No confirmation screen is presented if the system is known; if it is an unknown system, a small dialog says there is a
*mandatory* task sequence about to be run and it will run in 180 seconds. Users can hit enter.
No dependency check screen is shown; and if a package was missing, instead of presenting an error, it simply reboots. However, if everything is there,
the process starts successfully.
While I have no problems with the first window never being displayed, not displaying the error dialog and simply rebooting is what is bothersome to me.
99% of our builds are from PXE boot.
Again, these task sequences are all 100% optional, NOT mandatory, and I've double checked this multiple times. Can anyone explain why we get different
behavior between boot media and PXE boot? Any way of getting PXE boot to "mimic" the Boot media behavior?
I followed the guide here:
http://www.mydreampage.net/2012/09/21/how-can-i-deploy-a-hidden-task-sequence-in-configuration-manager-2012-sp1/
If you see the image here:
http://www.windows-noob.com/forums/uploads/monthly_09_2012/post-1-0-29840100-1348236179.png
You'll see the "Retrieving policy for this computer..." dialog box - I never get that with PXE - just Boot Media.
Note that I am running 2012 R2, not 2012 SP1 - but I never got a chance to test this process with SP1.
Upon further experimentation, the "hidden" task sequence has nothing to do with this. If I change it to a normal, non-hidden advertisement, as
long as the "prestart" command in the boot image is used, we don't get those missing dialog boxes at all, with PXE.

Are both boot images the same for PXE and the boot media? Same package ID and all?
Boot media for us always shows the task sequence wizard first, while PXE always displays the pre-start command first.
Daniel Ratliff | http://www.PotentEngineer.com

P45 Platinum boot problem!!!

PC specs in signature below!!
Ok, this is a new system, and it has been running GREAT since I started it for the first time. I am running my RAM with manual settings of 5 5 5 18/1.8v/800. Nothing is overclocked!!
Anyway, this morning I get to the office anxiously anticipating starting up my new system for a day of pristine computing. It starts up, the screen appears where you can hit "delete" to enter the bios. The screen hangs there for allot longer than I remember. Then, I get this message popping up on the screen: ''Reboot and select proper boot device or insert boot media in selected boot device''.
The first thing I did was hit Ctrl/Alt/Del to reboot and enter the bios to check my boot order. Everything was set exactly the way it is supposed to be. CD/RW first, then my OS drive. I exit out, and it boots into windows just fine.
Ok, later I decide to run check disk on my OS drive, thinking that maybe it's going bad, and the bios is having trouble seeing it. Check disk finishes, and it goes to boot into windows, and I get the ''Reboot and select proper boot device or insert boot media in selected boot device'' message again.
So, once again I hit Ctrl/Alt/Del to reboot, and it hangs on the screen where you can enter the bios. I quickly hit delete this time to enter the bios to see if my operating system drive is recognized. When I do this, it enters the bios, but hangs for awhile where it detects the hardware. Finally I can get to all the features in the bios, so I check to see if my hardware is recognized. Both my SATA hard drives do not show up as being recognized. My SATA CD/RW shows up, but not my hard drives.
So, I exit out of the bios, and it boots to windows just fine. I restart my system again to see what happens, and it boot just fine into windows.
Anyway, I went ahead and shut down my system, pulled the power plug, and cleared the CMOS. I then started the system back, entered the bios and set up all my settings, and it boots right into windows fine.
What do you think happened here? At first I thought maybe my OS drive was going bad, but after discovering that the bios didn't see either one of my drives, I ruled that out. Plus check disk was fine on the OS drive.
Any ideas??

Ok, I am still having an issue with this boot problem described above. Now that I have used my system allot more, I have discovered some more details. This boot problem only occurs when I plug anything into the system that gets noticed in the "boot order" in the bios. Example: USB thumb drive, external hard drive, or even swapping out an internal drive. The next time I re-boot, it fails like I described above.
Ok, here are some more experiences I have had. My system had been running great, and boot ups were working perfect. I decided I wanted to add a 3rd internal hard drive for storage. I already had my C operating system drive, and a D storage drive. I bought a large Seagate for a 3rd F storage drive. My CD/RW is listed as my E drive. So, I power my system off, and turn off the switch on the back of the PSU. I then add my 3rd hard drive and hook it all up. I power on my system. It boots to the bios screen where you hit delete to enter the bios. I enter the bios and I see all three of my hard drives. I check to make sure my boot order is correct, and save and exit the bios. As it booting, this time it hangs for a longer time at the screen where you can enter the bios. I hit the delete key to enter the bios, but it once again hangs while it tries to list all the hardware. Finally I can get to the bios setup screen, and both my C drive and D drive are not recognized, but my new Seagate is. For the record, my C drive is connected on the #1 SATA connection, my D drive is on the #2 SATA connection, and my new Seagate drive is on the #3 SATA connection. So, I select optimized defaults, save, and exit the bios. I re-enter the bios just fine and in the normal timely fashion. Now all my hardware is recognized. I set up my RAM again and other settings, and save, exit, and my system boots perfect.
So, I go about a week of perfect boot ups and no problems. I decided to buy a new larger hard drive to replace my existing C operating system drive. My plan was to install the new drive, and simply restore from a current image made from my old hard drive. I get my new C drive installed, and plugged into the #1 SATA connection on the mobo just like before. Ok, same drill......I enter the bios, and all my drives are recognized. I set my boot order, save, and exit. AGAIN, when it gets to the bios screen where you hit delete to enter the bios.....it hangs for longer than usual. I know exactly what it's doing, so I hit delete. It lags again as it starts to list hardware. Again, when I get to the setup bios screen, my C drive, and D drive are not recognized, yet my F drive is......just like before. So, both the drives connected to the #1, and #2 SATA connections on the mobo are not seen in the bios, yet the hard drive on #3 is seen. I do the same thing again, which is load optimized defaults, save, exit, and re-enter the bios again just fine. All drives are seen, I set up my personal settings, and all is well again.
The last time it happened was when I connected my USB thumb drive. Same exact scenario. The thumb drive shows up, and my F drive with the C drive and D drive missing again.
Any ideas?? The system will run just great now the way it is. But, the second I stick my thumb drive in, or an external hard drive, my C and D drive will disappear on next boot. If I kept the thumb drive and external drive connected, and just loaded optimized defaults, then rebooted and loaded my personal setting, I would never have the boot problem again. It just doesn't like me disconnecting, and re-connecting hardware I guess.
About the only thing I can think of to try is connecting my C and D drive to different SATA connections. But, even if that worked, it wouldn't fix the problem.

Problems PXE booting Gen 2 Virtual Machines after Upgrading to Windows Server 2012 R2

My Current Setup:
I have two virtual machines set up with Hyper V on my Windows Server 2012 Server.
VM1: Configured to boot from an ISO file and runs Clonezilla server.
VM2: Configured to PXE boot using a legacy network adapter, and with a passthrough 250Gb hard disk.
These two VMs are connected to an external Virtual Switch, which allows physical machines to PXE boot to the Clonezilla server.
For the past few months I have been using this setup for two purposes:
1. To clone physical machines to the Clonezilla virtual server (as a backup).
2. To restore those image to the second VM if I find that need to get access to the files on the original image..
This has worked perfectly, except for the fact that the speed of the legacy network adapter on the second VM (which is required to PXE boot) is very slow. But I know this is because of the limitations in how the legacy adapter works...
Now my problem:
I found out that Gen 2 VMs allow you to PXE boot without having use a legacy network adapter, allowing me to image back to the VM faster. So I upgraded the Server to Server 2012 R2 . I then created the same two virtual machines on the R2 server. I can still
PXE boot the Gen 1 VM to the Clonezilla Server but I cannot get the Gen 2 VMs to PXE boot properly. They get an IP address from the Clonezilla Server but then just stop with the following screen. (note: I have disabled the Secure Boot).
Are Gen 2 VMs unable to pull down images from anything other than a WDS Server?

Hi J,
>>Unfortunately WDS is not a solution for us as it is dependent on the PC being part of a domain
If you would like to make the client not join to the domain, please check the box before “Do not join the client to a domain after an installation.” In addition, make sure not to set the client to the domain in the unattend file and do not prestage
the computer in AD. "
It is quoted from following thread :
https://social.technet.microsoft.com/Forums/windowsserver/en-US/1026c3a9-0a10-4a58-a48f-5391659a96c8/wds-set-unattend-file-for-workgroup?forum=winserversetup
Best Regards
Elton Ji
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.

Formatting the encrypted hard drive or intalling OS again with PXE boot can change TPM owner password file?

Hello,
1) I realized that when MBAM bitlocker encryption start both Recovery key and TPM owner password file are send to MBAM server. If we change the computername of the notebook, we can find out Recovery key from MBAM server with the KeyID as we can read it from
computer screen, but we can not find out TPM owner password file with the existing new computername information from MBAM server, so we have to know old names of all computers but it is impossible. So we have to do decryption and clearing TPM than we
can again encrypted it with its new name. is it right?
2) We will going to deploy mbam encryption to our notebooks. But sometimes when a person quit the job his notebook can given to another person or new employee and based to our procedure when a notebook will given to another user it should installed
OS again with PXE boot. I would to know will it be enough to installing with this method again with a diffrent computer name or should I firstly clear its TPM than install OS with PXE to keep TPM owner password file missing as item 1?
I hope i can explain what i mean :)
Regards,
SibelM

I would suggest you to first decrypt the laptop and then follow the process:-
- Clear the TPM
- Encrypt the type.
- Check for the encryption behavior.
Cause I have found on some model that if the OS drive is encrypted, PXE boot fail on that machine even though I also did a direct PXE on an encrypted machine with clearing the TPM.
TPM ownership password is a hash file that gets generated with a set of algorithm. SO each time when you PXE boot, by clearing the TPM, the TPM hash password for the TPM will change. This has been done for security measures.
Gaurav Ranjan

When i want to install windows7 on my snow leopard(10.6.4) with boot camp assistant,said that you must update your mac,i do this and try to install windows7 again but i have this problem again?what can i do?

when i want to install windows7 on my snow leopard(10.6.4) with boot camp assistant,said that you must update your mac,i do this and try to install windows7 again but i have this problem again?what can i do?

Graham Giles wrote:
Have you seen this type of problem before? I think it could be a serious issue for anyone in a similar position.
No; but then, I've not had occasion to use TDM. I've been using firerwire drives for over 10 years, both FW400 and FW800, with no issues except a bit of instability using a B&W G3 machine.
TDM should be safe. Using cautious, manual copying of files from the Target machine to the Host machine should not result in unexpected loss of files or damage to the Target drive's directories. It should behave exactly the same as if it were an external (to the Host) firewire drive.
• I don't suppose there is anything I can do to 'put back' lost items from a separate Time Machine drive which has an up to date backup on it.
There is probably a way to do that - seems to me that's one of the reasons for a Time Machine volume.
On the other hand, if the Time Machine volume is rigidly linked to the now-absent OS on the original drive, there may be no way to effectively access the files in the TM archive.
I know that using a cloned drive would work well in this instance.
I have no experience with Time Machine, so perhaps someone who has will chime in with suggestions.
With the machine in TDM with the other machine, have you tried running Disk Utility to see if you can effect repairs to the drive?

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?

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

Problems with PXE boot for clients

Hi,
I have an environment where I have clients on av VLAN connected to a Cisco 2960X (WS-C2960X-48LPD-L ) with layer 3 configuration. The clients do a PXE boot to get configuration. The thing is that this does not work on all switches. The switches have the exact same configuration, the only thing that differs is Hardware Board Revision Number. (That I can find..) The ones that works has 0x05 and the ones that doesn´t work has 0x12. The PXE server is connected on a different VLAN in the same switch.
I have configured spanning-tree portfast on the interfaces. I have ip-helper on the VLAN. The PXE server is also the DHCP server.
Any suggestions?
Regards,
Carina

It seems NIC teaming was configured really incorrectly in this case. Different switches require different configuration with specific settings on the Windows Server side. Sometimes incorrect configurations work when network traffic is low but start behaving
funny when it increases. The reason behind this is Windows hosts sending back answers to its peers via different physical links, and the switch doesn't expect it and drops "incorrect" frames.
You can find detailed description of different teaming modes here:
http://www.aidanfinn.com/?p=14004
If you use LACP, be sure to set up port channel on Cisco switches or LACP trunk on HP switches. Otherwise you might want to use the Switch Independent mode.
Evgeniy Lotosh
MCSE: Server infractructire, MCSE: Messaging

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

W530/T530 PXE boot problem again

Similar Messages

Maybe you are looking for