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

Similar Messages

SCCM WDS PXE Boot Authentication

Hi All,
The ability to do domain authentication for a PXE boot in RIS could be achieved by modifying the security directly on the image folder on the RIS server - however, I can't seem to implement the same access control in SCCM 2007 SP1 using WDS.
I have set up the capability to build bare metal machines using the OS Deployment feature in SCCM. The image process is advertised to “All Unknown Computers” and starts with the “builder” hitting F12 on the workstation. The boot image is loaded from the DP share and then the process begins.
My question is: How can I protect the PXE boot process by having the system request a domain Username and Password in order to begin the PXE boot process and also limit who can see the advertisements for the avialable images.
Thanks,
phil

Hi,
You can specify a password for computers that boot to PXE.
For more info :
http://technet.microsoft.com/en-us/library/bb680668.aspx
http://blogs.technet.com/configurationmgr/archive/2009/07/27/a-step-by-step-for-using-osd-through-system-center-configuration-manager-2007.aspx
http://technet.microsoft.com/en-us/library/bb632767.aspx
Regards.
Bechir Gharbi. MCSA, MCSE M+S, MCITP Server/Enterprise Administrator, MCT, MCTS Configuration Manager/Forefront

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/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)

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.

WDS PXE Boot "Downloading NBP File..."

Have been able to boot and install from WDS VM. Had this happen once before as well but no idea how it resolved, just started working again.
I haven't touched the server since I last used it successfully.
Today when I attempted to boot a new VM from PXE I have been stuck at "Downloading NBP file..." during the PXE boot process. After about 5 minutes it comes to a "Contacting Server (192.168.4.108)" screen where again has sat so far for
around 5 minutes.
Normal behaviour is it just boots, downloads this file in seconds and is at the Windows Setup within a few more seconds.
I've restarted the WDS services on it's server and rebooted the client multiple times, no change. Checked Logs on the WDS (Application, System) and nothing, no clue where to check specific to WDS...
What am I missing here? This is completely vanilla WDS, installed, added files from 2012 R2 disk and that's it. As said worked fine in the past, now magically not working and not the first time it's done this.

Enabled all logging available.
Again, fuck MS not making copy and paste work within Hyper V console.
Have this listed followed by errors:
[WDSServer/WDSTFTP] TftpSession[0x00000026BA967730:192.168.4.101:1301] - Error: Received error from client. Code=8.
I can't find what Code=8 is meant to mean. Where is the Technet article or whatever listing the WDS TFTP error codes and their meaning? Why provide error codes if no such reference exists?
This is followed by:
[WDSServer/WDSTFTP] [base\eco\wds\transport\server\tftp\tfptsession.cpp:1636] Expression: , Win32 Error=0x4d3
[WDSServer/WDSTFTP] [base\eco\wds\transport\server\tftp\tfptsession.cpp:1636] Expression: , Win32 Error=0x4d3
[WDSServer/WDSTFTP] [base\eco\wds\transport\server\tftp\tfptserver.cpp:1211] Expression: , Win32 Error=0x4d3
and eventually after some more informational entries another informational "Max retries done, killing session".
I've enabled Verbose logging but really doubt that will help and really can't be assed typing out what is entered in text on another screen on the same PC but MS can't give a way to copy and paste from.
The whole idea with WDS was just a simple way to spin up new VMs when required, without using a ISO which can cause issues if not removed with Clustered Hyper V we've found. Can't believe something that should be so simple is leaving me scratching my head
for hours. Time to look at other products that don't do this to people I think.

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

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

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.

Type 2 Virtual Machine in Hyper-V will not PXE boot with WDS

Hi
Bit of a wierd scenario this but I'm doing a bit of a lab experiment kind of thing. The setup is as follows:
VMWare Workstation 10 with Windows Server 2012 R2 running as a virtual machine. In VMW10 I have a NAT network interface and a Bridging interface set to load with the virtual machine. These seem to work fine (although the NAT doesn't seem to want to connect
to the internet but that's why the bridging one is there in addition).
Server 2012 is configured with the following roles:
ADDS, DHCP, DNS, Hyper-V, Printer, WDS
I have correctly configured WDS to work on the same machine as DHCP and I can get PXE boot working with WDS on a Type1 Virtual Machine in Hyper-V using the Legacy Network adapter. My problem is when I try and PXE boot on a Type2 Virtual Machine (this type
is new in R2 and should eliminate the need for a legacy network adapter) using the same network interface that I used for the Type1 machine, I get an IP address from DHCP but WDS doesn't seem to respond. Instead I get the "PXE-E16: No Offer Received"
message. I have tried just about everything I can think of and spent the whole day trying to figure out why this is the case but came up with nothing. Has anyone else encountered this or can anyone shed any light on the matter?
Many thanks in advance

"VMWare Workstation 10 with Windows Server 2012 R2"and "Server 2012 is configured with the following roles: ADDS, DHCP, DNS, Hyper-V, Printer, WDS"
Hyper-V is not supported to be run as a VM. It is a Type 1 hypervisor, which means it works on the bare metal. You have it running as a VM on a Type-2 hypervisor, so it has no access to the bare metal. Yes, VMware may have made it so some
things work in that environment, but it is not a supported (or tested) environment for Hyper-V.
.:|:.:|:. tim

WDS PXE Problems on 1 model of PC only - The following Client failed TFTP Download - Error Code 1460

Hey all,
I am experiencing a problem with my WDS PXE Environment, with 1 specific model of PC's only. This is a Dell XPS machine with an Intel e1000 nic in it.
The problem is that when you PXE Boot, it starts off fine, and I reach a menu that has all of my boot images listed, but as soon as you pick one it hangs on a black screen.
From the event viewer on the server I can see the following entry:
The Following Client failed TFTP Download:
IP: 10.130.148.211
Filename: \Boot\Boot.SDI
ErrorCode: 1460
I've done some google searching and found some topics that could be related, but none of the fixes mentioned helped me. This is the one I tried:
http://social.technet.microsoft.com/Forums/en-US/winserversetup/thread/a1246f62-6a8a-482b-9323-7e02dfeab196/#52aaf6fb-9494-4327-bbc3-8afe3e78905c
The problem I had was that the link they gave to the Hotfix, doesnt actually have anyway to download the hotfix!!
http://support.microsoft.com/kb/975710
Although
I am not convinced that packet size is the problem here, more likely some network or disk controller driver issues??
No
idea at all where to go from here. It is only this one model of PC that fails, and all others work fine. If someone can point me in the right direction it would be very greatly appreciated.
I
would be happy to provide you with any additional details you may require.
Thanks,
-Ben

You need to contact CSS to get this fix.
Hotfix Information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore,
if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2008 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers
and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
John | Program Manager | System Center Configuration Manager

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

Screen resolution when PXE boot from WDS vs Install Windows 8.1 from USB

Hi all
I own a Lenovo ThinkPad T430s, X230 Tablet, and now have my hands on a T440. All three machines have UEFI Secure Boot enabled properly, i.e. Windows boot screen shows Lenovo logo instead of Windows logo.
However, if I do a PXE boot (using Windows Deployment Services from Windows Server 2012, not R2) and boot to the same boot.wim provided on a Windows 8.1 ISO image, the boot screen resolution turns crap, and the WinPE environment runs in 640x480. Also, as opposed
to the Lenovo logo showing on the boot screen, the Windows logo shows up instead, indicating it's not doing a secure boot?
When booting from a USB stick however, using the same Windows 8.1 boot.wim (copied from ISO), the screen resolution in Windows Setup is detected correctly, and the Lenovo logo shows up.
This occurs on all three machines since MDT was upgraded to MDT 2013 or when I replaced Windows 8 boot.wim with Windows 8.1 boot.wim (as the Windows ADK 8 --> ADK 8.1).
Is there a fix for this? Do others have the same problem elsewhere?
Many thanks

Hi,
When boot UEFI-based computer from PXE you should take more into consideration.
For some computers, you might have to perform additional steps to make sure that Windows is installed in UEFI mode, and not in legacy BIOS-compatibility mode.
Some computers might support UEFI. However, they do not support a PXE-initiated boot when in UEFI mode.
How to Create a PXE-Initiated Windows 8 Deployment for UEFI-Based or BIOS-Based Computers in Configuration Manager
http://technet.microsoft.com/en-us/library/jj938037.aspx
Especially for “Pre-Deployment Considerations”
If you still cannot find a way to make it boot from UEFI mode, you should contact with manufacture to confirm if PXE-initiated boot is supported.
Hope this helps.

The Open Procedure for service "WDSTFTP" in DLL "C:\Windows\system32\wdstftp.dll" failed. WDS not PXE booting!

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?
tconners

Hotfix 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

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?

Wds pxe boot problem

Similar Messages

Maybe you are looking for