Archlinux via PXE

Hello,
I'm trying to add the archlinux to a PXE. Archboot is already there, working, just like several other distros.
My PXE server (10.2.85.251) is running a debian stable with TFTPD-HPA and UNFS3.
Just added the uncompressed archlinux ISO to /var/lib/tftpboot/archlinuxlive201108 and put these rows to /var/lib/tftpboot/pxelinux.cfg/default:
LABEL archlinuxlive201108
menu label Arch Linux 2011-08 32-bit
kernel archlinuxlive201108/arch/boot/i686/vmlinuz
append initrd=archlinuxlive201108/arch/boot/i686/archiso.img rootfstype=nfs root=/dev/nfs nfsroot=10.2.85.251:/var/lib/tftpboot/allievi/archlinuxlive201108/ archisobasedir=arch archisolabel=ARCH_201108 ip=:::::eth0:dhcp -
NFS is working fine (I can mount 10.2.85.251:/var/lib/tftpboot/archlinuxlive201108) TFTP is ok too and I can reach arch files (manually tested it with atftp), but my clients won't boot Arch: "ERROR: '/dev/nbd0' found, but the filesystem type is unknown.".
Did anybody manage to add Arch to PXE?
I can see with wireshark that the machine I'm booting via PXE is trying to open a connection to NBD port; this fails since got no NBD server. Why is it doing stuff with NBD?
I'm afraid to be passing some wrong parameters to the kernel, but am not sure about how to change them.
Last edited by peoro (2011-11-19 19:42:15)

Uh, wait, so "rootfstype=nfs" is no more having any effect? Ouch!
Ok, I'm trying to set up NBD, thanks for your update at archwiki
NBD seems to work, I can mount the image with nbd-client from an installed Arch client, but Arch live (booted via PXE) cannot: server (tried both with nbd-server from debian stable repository and xnbd-server from testing) says that client closes the connection, while Arch live says "Not enough opts_magic".
Could find this error on a mailing list from 2010, but they aren't giving any info on how to fix it.

Similar Messages

OS reinstallation on Portege 2000 via PXE-LAN

Hello again,
So, as said before I am trying to reinstall Win XP from the provided Recovery CDs.
In fact, I have 4 CDs: One that contains only Windows 2000 Pro and 3 CDs containing Windows 2000 and Windows XP Pro. Of course, the 4 CDs were delivered with the computer.
I tried via FDD and CD-ROM which didn't work (see preceding topic), but I also tried via PXE-LAN.
So I installed a 3 month evaluation version of Windows Server 2003 on my desktop and ran the RIS (Remote Installation Service).
1- It accepted the Windows 2000 Pro CD as a Windows Installation CD, but when launching the Portege 2000, after a few step, when it looks for the computer configuration, I get an error message that the driver for the LAN Card is missing and that it cannot proceed any further.
2- When I run the RIS with the CD 1 of 3, it doesn't even recognise it as a Windows Installation CD!!
So I managed to install a Win XP Family Edition which I normally run on my desktop, but I don't have any driver installed (WIFI, Infrared, SoundCard, etc...) but also I have only 1 licence for the Family Edition.
Has anyone an idea on how to proceed with this method (I mean with the 3 CDs)??
Thanx a lot.

Hello Josey
As far as I know recovery images on recovery CDs for Portege notebook without ODD contains drivers for PCMCIA or PC-card used on Toshiba external ODDs. Because of that when you connect original Toshiba external ODD the delivered recovery media will be bootable and you can install OS anytime you want.
ODDs are not so cheap but if you like your notebook you should invest your money und buy original and compatible ODD. Other way you can contact service partner (if ASP is not too far from you) and ask them if they can install OS for you. They have those ODD in service. I am pretty sure they will do this for you. Pay them the coffee and problem is solved.
When OS is preinstalled install all stuff you need and configure the notebook how you want to have it. After doing this try to obtain applications to create your own image like Norton ghost. Install it and create own ghost image on second partition. On this way you will be able to install self created ghost image any time you want and also without external ODD. This image you can also save on external HDD and use anytime if something goes wrong. I do this for years.
It is very practical when the OS is infected by virus or when some tool does not work anymore. In just 20 min you can have all settings as before.
Sorry for long posting and good luck!

Problems with *.zmg Image deploy via PXE

Hi all,
I am currently faced with the following problem unfortunately:
We use ZCM pre boot (pxe) to image our clients with a windows7.zmg image which was configured with sysprep.
The image is created on a PC, which has a 300GB HDD. The windows partition is over the total size of the hdd.
This imaging process on a new pc is as following script shows:
Code:
# Delete + MBR partition table
dd if = /dev/zero of=/dev/sda bs=512 count=1
# partition
fdisk /dev/sda << EOF
w
EOF
# imaging
img rp server IP path/to/image.zmg
This works quite well so far, with the only problem, that the partition on the new PC has the maximum of 300 GB. So if I image this image on a pc, which hdd has 500 GB, 200 GB will remain unpartitioned.
I have redesigned the imaging now follows:
Code:
# imaging
img pc1 NTFS
img rp server IP path/to/image.zmg a1: p1
img pa1
Now the entire HDD is used for the partition, but after the imaging the PC doesn`t boot, and stops with a black screen and a blinking cursor.
I am typing this on a problem with the mbr, but does not know how to fix it: (
I have to modify the imaging-process, that i can use the image on every HDD size with the result, that always the max partitionsize is used.

hi all, i am having an issue where found out that Imaging Script cannot be used to multicast so i am running in to a problem now. If i push out an image via zcm script bundle it works fine with your suggestions but i cannot seem to figure out why the image wipes out all the hard drives in the systems during multicast image set or a single image load via pxe boot.
First problem:
if i push out an image via Zenworks Image preboot bundle file set is set to 1 it wipes out all the hardrvie in the system (tow hard drive, disk 0 and disk 1. i can certainly fix the disk resizing issue by adding a script to unattaned file after the image is loaded to resize the disk automatically using diskpart commands. which works fine.
Second problem:
here is what i did:
1. created an multicast Image Set
2. number of clients needed set to 1
3. Time out in five minutes
It does not load the image znd waits for session to start.
how can i automate this via zcm to make sure on pxe boot the both pcs receive the image as scheduled in zcm.
Please assist.
thank you.

Multicast WDS Imaging Not Working - Doesn't show up when booted via PXE..?

I have a lab environment setup specifically for imaging laptops via WDS. I have a stand alone Windows 2012 server connected directly to an 8-Port Cisco SG-220 8 Port switch. Nothing else is connected to this server and it is not being
used for anything else. The server is running DHCP and WDS. I can boot laptops via PXE and connect to the WDS server to deploy the images through standard WDS imaging. However, I have not been able to get Multicasting to work. I
have never used Multicasting before and have read through the documentation but must be missing something. This is what I've done:
1. In the WDS server I right click on my deployment image and select 'create multicast image' then go through the prompts to create an auto-cast image.
2. The Multicast image is created and shown as 'waiting' on the WDS server.
3. The Cisco router is brand new out of the box, the only configuration I did was to enable IGMP snooping. I did not make any other changes to the setup of the switch.
4. I boot a target machine via PXE using the same Boot Image that I always use. It loads to the screen where I can select the image I want to deploy but it never shows the multicast image as an option. I only see the regular image I had previously
been using.
I'm not sure what else I'm missing in order to get the target machine to connect and image using the multicast image.
Here are a few screen shots of what I have setup:
Here is the multicast image created on the server
Here is the Cisco Router configuration:
Here is the NIC card configuration on the server:
This is the target laptop booted via PXE but it never shows the multicast image as an option.
/>

Hi AdamNYC31,
The multicast feature used by WDS uses Internet Group Management Protocol (IGMP) version 3. Your network switches will need to support this, and you’ll need to configure them
for multicast. Please refer the following similar thread check each step Aaron Tyler and Ron St and Ankit Oberoi offered solution.
Multicast issue: Always "Waiting"
https://social.technet.microsoft.com/Forums/windowsserver/en-US/18122b39-e707-455d-b22f-956ebfb95e40/multicast-issue-always-waiting?forum=winserversetup
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Problem deploying OS via PXE - SCCM 2012 R2

Unable to deploy OS via PXE. This is what I'm getting on the unknown client machine when initializing PXE:
Downloaded WDSNBP from "IP"
Architecture x64
The details below show the information relating to the PXE boot request for this computer. Please provide these details to your Windows Deployment Services Administrator so that this request can be approved.
Pending Request ID: 13
Message from Administrator: Configuration Manager is looking for policy.
Contacting Server: "IP"
TFTP Download: smsboot\x64\pxeboot.com
Press F12 for network service boot
PXE-M0F: Exiting Intel PXE ROM
Operating System not found
Here are the entries in the SMSPXE.log file when I PXE boot the client machine. It stays at "Looking for bootImage"
<![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
]LOG]!><time="09:12:33.711+360" date="01-13-2014" component="SMSPXE" context="" type="1" thread="6028" file="libsmsmessaging.cpp:6346">
<![LOG[00:50:56:80:10:C0, 82760042-6D77-B44D-A365-52574A518CCB: device is not in the database.]LOG]!><time="09:12:33.711+360" date="01-13-2014" component="SMSPXE" context="" type="1" thread="6028"
file="database.cpp:483">
<![LOG[Getting boot action for unknown machine: item key: 2046820352]LOG]!><time="09:12:33.711+360" date="01-13-2014" component="SMSPXE" context="" type="1" thread="6028" file="pxehandler.cpp:231">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>7ecc18a2-e0a0-4f63-a1e1-418366a7289f</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="DCC2000E" OfferIDTime="1/13/2014 8:11:00 AM" PkgID="DCC0001B" PackageVersion="" PackagePath="http://vmsccm001.dcci.internal/SMS_DP_SMSPKG$/DCC0001C"
BootImageID="DCC0001C" Mandatory="0"/></ClientIDReply>
]LOG]!><time="09:12:33.802+360" date="01-13-2014" component="SMSPXE" context="" type="1" thread="6028" file="libsmsmessaging.cpp:6544">
<![LOG[00:50:56:80:10:C0, 82760042-6D77-B44D-A365-52574A518CCB: found optional advertisement DCC2000E]LOG]!><time="09:12:33.803+360" date="01-13-2014" component="SMSPXE" context="" type="1" thread="6028"
file="database.cpp:483">
<![LOG[Getting boot action for unknown machine: item key: 2046820353]LOG]!><time="09:12:35.821+360" date="01-13-2014" component="SMSPXE" context="" type="1" thread="6028" file="pxehandler.cpp:231">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>44fa2ff5-160c-4896-bc9b-397c10e4414b</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="DCC2000E" OfferIDTime="1/13/2014 8:11:00 AM" PkgID="DCC0001B" PackageVersion="" PackagePath="http://vmsccm001.dcci.internal/SMS_DP_SMSPKG$/DCC0001C"
BootImageID="DCC0001C" Mandatory="0"/></ClientIDReply>
]LOG]!><time="09:12:35.919+360" date="01-13-2014" component="SMSPXE" context="" type="1" thread="6028" file="libsmsmessaging.cpp:6544">
<![LOG[00:50:56:80:10:C0, 82760042-6D77-B44D-A365-52574A518CCB: found optional advertisement DCC2000E]LOG]!><time="09:12:35.919+360" date="01-13-2014" component="SMSPXE" context="" type="1" thread="6028"
file="database.cpp:483">
<![LOG[Looking for bootImage DCC0001C]LOG]!><time="09:12:35.919+360" date="01-13-2014" component="SMSPXE" context="" type="1" thread="6028" file="bootimagemgr.cpp:1774">

The TS is deployed to the All Unknown Computers group. The client machine I'm trying to install the OS is a VM with no OS currently installed so I'm assuming SCCM would see it as an Unknown Computer. How would I verify that SCCM doesn't currently
hold any data for this client?
Also, I noticed the following in the SMSPXE log: <![LOG[Client boot action reply: <ClientIDReply><Identification
Unknown="0"
Does Unknown="0" mean SCCM is not recognizing the client as being unknown?

Zcm imaging via pxe

hi all, i am having an issue where found out that Imaging Script cannot be used to multicast so i am running in to a problem now. If i push out an image via zcm script bundle it works fine with your suggestions but i cannot seem to figure out why the image wipes out all the hard drives in the systems during multicast image set or a single image load via pxe boot.
First problem:
if i push out an image via Zenworks Image preboot bundle file set is set to 1 it wipes out all the hardrvie in the system (tow hard drive, disk 0 and disk 1. i can certainly fix the disk resizing issue by adding a script to unattaned file after the image is loaded to resize the disk automatically using diskpart commands. which works fine.
Second problem:
here is what i did:
1. created an multicast Image Set
2. number of clients needed set to 1
3. Time out in five minutes
It does not load the image znd waits for session to start.
how can i automate this via zcm to make sure on pxe boot the both pcs receive the image as scheduled in zcm.
Please assist.
thank you

arahman147,
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/

Thinkpad T440s BIOS update via PXE fails with "invalid system disk"

Hi,
I'm trying to boot via PXE to the BIOS 2.24 update ISO image because the T440s comes without a DVD drive. The Thinkpads are running RHEL 6.5 workstation installed. I'm using syslinux 6.02 and the following menu entry:
label lenovo_t440s
    menu label Lenovo Thinkpad T440s BIOS 2.24 Update
    kernel memdisk
    append initrd=lenovo/t440s/gjuj11us.iso iso
The ISO gets loaded via TFTP and seems to boot, but then an error message appears:
Loading boot sector... booting...
Lenovo Group Limited
Invalid system disk
Replace the disk, and then press any key.
The Thinkpads come with the following SSD drive: SAMSUNG MZ7TD256HAFV-000L9.
Anyone had luck with updating BIOS via PXE boot?
We also have Thinkpads T430s. There the BIOS update ISO image loads, displays the menu, but when one presses "update firmware" then it freezes.
Regards,
Bernd

Same behaviour when I try without PXE and load memdisk and ISO file directly via GRUB using this entry in /boot/grub/grub.conf:
title ThinkPad BIOS Update
root (hd0,1)
kernel /memdisk iso
initrd /gjuj11us.iso

Lenovo Yoga 2 Pro Installing Windows OS via PXE SCCM

Hello everyone,
I have 2 Lenovo Yoga 2 Pro here in our company environment, because our CEO really like using touchpads with pens =).
Since the Yoga 2 does not have a LAN connector i have been unable to install windows via our SCCM Server.
I contacted telephone support and basically got told, this is a consumer device and pxe is not prossible. Which seems weird since there are pxe drivers and a management driver pack for the yoga 2 available.
What I tried this far.
Use the One Dock -> Doesnt recognize lancard
Use USB Networdcard Startech USB21000S2 (7500 chipset) -> Not recognised by BIOS
Use pptical boot media -> boots to pxe environment but cant connect to the server and aborts
SCCM 2012 SP1 CU4
OS to install: Windows 7 Ent
All standard and pxe drivers are incorporated into the install image.
Does anybody know, if or how it is possible to get this Notebook integrated in my SCCM environment?
Thanks in advance

Hi Jerry133, welcome to the forums,
the following thread may be of interest to you; it would appear the USB ethernet dongle for the ThinkPad X1 Carbon works with the Yoga 2 Pro for PXE boot.
http://forums.lenovo.com/t5/Idea-Windows-based-Tablets-and/Yoga-2-Pro-PXE-boot/m-p/1516628#M20051
The part number for the dongle is 4X90E51405 and should be the first article on the following page;
http://lenovoquickpick.com/deu/accessorycategory/33/networking-i-o
More Info on the dongle can be found here;
http://support.lenovo.com/en_US/detail.page?DocID=PD029741
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

Only seeing 1 Boot Image via PXE

When I boot up through PXE I've always only seen the 32 bit boot image which has always worked fine. However, we now have a need to use the 64-bit boot image. I checked the properties and everything looks the same as the 32 bit one but it doesn't
show up when I boot to PXE.
Anyone know if there's something I need to do in order to make both images show up? When we had SCCM setup we were told that the boot image didn't really matter since our OS image was 64-bit anyway, but our Surface Pro 3s that we're testing can't seem
to boot since they are only 64-bit (at least that's our working theory).
Thanks!

I'm obviously not understanding something as this prompt comes up before I ever get to the point of choosing a Task Sequence.
These are Dell Laptops and the process I go through is:
Boot up and press F12
Choose Network Boot
Then I get the prompt in the picture above
I press Enter on the Boot image above and this takes me to a SCCM Screen that starts the Task Sequence Wizard
I then get a list of all my Task Sequences and can choose the one I want to run for the machine I'm on
This then starts up the image process
Maybe we're not doing things the normal way but I just need to know how to active or create or whatever a 64-bit version of the boot image... I think... ?

Restore image via PXE to vm

Trying to set up a VM on ESX4 host by creating a new VM (XP 32bit) then booting to PXE and letting zenworks image it. Having some problems doing so..
Firstly.. sometimes during the initial download of the linux/initrd file, etc.. it says "Heap:dispose fail" but seems to continue on..
Then, the automated script runs, seems to push out the image successfully. VM restarts, and I get a "No OS Found" then the imaging process restarts itself. Infinite loop. If i boot into maintenance mode and "mount /dev/sda1 /mnt/harddisk" and then do a "dir" i see "Windows" "Program files" etc..
Any clues as to why it wont boot up?

Originally Posted by joebrug
..Any clues as to why it wont boot up?
No clue to this specific issue... but I've had some strange results with placing back a Windows template (image dump) I had originally created with ESX 3.5. The image looked ok but would not boot.
I managed booting it by chucking the guest configuration (keeping the disk), creating a new custom vm machine using the (older) version 5 type vm configuration.
Could be that helps?
If the image boots you can update the configuration to version 7 by shutting down the vm, right clicking and choosing upgrade hardware.
Just a thought,
Willem

WDS for custom image deployment via PXE

I've recently spun up a 2012R2 server and I'd like to use it so I can netboot clients to it and install a custom image on the machine, no hassle. I have figured out how to take an image from a Windows 7 install disk and add drivers to it.
However, I'm wondering the best way that I could configure an image to use that has all programs, profiles, updates, and drivers on it for a 'universal' install. Is this possible?
For example, can I have a 32-bit image that has Chrome, FireFox, and some other programs on it, complete with any drivers that might be needed for NIC and WLAN cards, graphics adapters, etc? And then a 64-bit image for the same thing. Ideally, these
would house drivers for any of our machines, so I could PXE boot a 64- or 32-bit desktop or laptop, regardless of the model (They're all one manufacturer) and have them install the image and be configured, ready to go?
I would also like to know how I could create a custom image/ISO from a machine that is already ready-to-go as a template.
Thank you for answers in advance.
If it helps, i'm on a Windows 8.1 x64 machine myself, but the machines I'd like to image are Windows 7 (both x86 and x64).

Yea. In a nut shell:
1. Do the install and create the needless account the setup process forces you to create.
2. On first log in enable the original default Administrator account and give it a password
3. Log in with the default Administrator account.
4. Delete the local account that setup forced you to create
5. Go to Advanced system Settings --> User Profiles, and remove the profile for that account. This is important,...this removes the registry entries for the Profile as well (just deleting the folder structure under "C:\Users" does not,
and problems can result).
6. Build your image model from this point using the original default local Administrator account. This is the only account that Sysprep will leave on the machine when it is run. Note the machine is not a Domain Member when I am at this point.
I only join the machine that I apply the image to when I finally deploy the machine to be used .
7. Run Sysprep on the machine to prepare it for duplication, then shutdown or reboot. When starting up you do not want to allow it to boot into the OS or you will have to rerun Sysprep again. You can use WDS to "capture" an image
after doing a network boot from the Nic. You can also boot the machine using a Windows PE bootdisk and manually capture an image with ImageX (comes with WAIK for Win7). But ImageX is commandline only and annoying,...there is a GUI alternative called
GImageX (google it). Then manually copy the captured image to the WDS Server. Note when you capture an image,..you are only capturing the Boot Partition,...not the entire drive.
The details of all this you can sort out by studying "how to use" WDS and WAIK (Win7). That should put you on the right track.
A source for creating a bootable Windows PE disk is here.
http://winbuilder.net/

Booting from CD autmatically attempts to intsall via PXE

And I don't want that. I just want to do a normal netinstall from the CD.
But when I boot from disk, PXE starts, tries to connect and I get two errors
PXE-E53: No boot filename received
PXE-M05L Exiting PXE Rom
What do I need to do. I did sha1 checksum and the image is okay.
Any help would be appreciated.

2010-05-netinstall-i686
That's what I was starting to think. But I don't what I should change in my BIOS and I'm definitely not familiar enough with BIOS to feel comfortable changing any settings without instructions from a stranger from the internet.
checksum also verifies that the image is okay.

Windows 7 Deployment via PXE to an UEFI + secure boot enabled Lenovo system.

Hi Everyone,
I was wondering if above was possible?. I have not yet put much energy this uefi and secure boot thingy - so just told our supporters to change bios settings back to Legacy with secure boot disabled on the pre Windows 8 delivered Lenovo systems.
Deployment system :
SCCM 2012 SP1 is running on a Windows Server 2008R2
Regards
Anders Jensen
Solved!
Go to Solution.

Thx

SCCM 2012R2 PXE via IpHelper

Hi Everyone,
I'm trying to deploy SCCM2012R2 task sequence via PXE with IpHelpers.
I've configured the IPHelpers to point to the SCCM DP PXE and the DHCP, but nothing happen.
Has someone a quick guide on how to configure SCCM2012 and iphelper?

Hi,
Have you resolved this issue? If not, please try to use Network Monitor to check whether the IP Helper works fine.
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.

8.1 PXE via WDS, MDT, and ADK

Hi, all:
Looking for some help troubleshooting a PXE issue. Thus far, I have set up WDS, MDT 2013, and ADK 8.1 and can successfully capture/deploy a Windows 8.1 image by running the Lite Touch.vbs script from my deployment share. While deploying in this method isn't
terrible, the goal is to ensure that it can be done via PXE. I had previously been able to successfully PXE boot Windows 7 machines with WDS, MDT 2012 Update 1, and ADK 8.0, but recently had to upgrade to roll out 8.1 images. Now I can't get the new 8.1 machines
to boot via PXE. System in the example is prestaged in ADDS. Options 60 and 67 are unchecked on WDS server as DHCP and DNS are on another server.
I've enabled logging in WDS in an effort to figure out where the PXE is failing, but it doesn't tell me much. Events only indicate that wdsnbp.com was downloaded via TFTP successfully. The machines attempting to boot say the same thing. I receive the following
when booting:
>> Start PXE over IPv4.
Station IP address is 10.1.50.129
Server IP address is 10.1.1.216
NBP filename is boot\x64\wdsnbp.com
NBP filesize is 30832 Bytes.
Downloading NBP file...
Succeed to download NBP file.
System automatically reboots and goes straight into existing deployment of Windows. It's almost as if there's no boot image being referenced in the NBP file, but I've checked my Boot Images in WDS to ensure that an 8.1 image exists. I replaced the 8.1
boot image just in case and the issue is the same.
Any thoughts? Your help is appreciated!

Try a Win7 boot image. Then choose the Win8.1 Install image you want when you get to that point. The boot image only gets the machine running so you can choose the install image,...it doesn't have to be a 8.1 boot image to install 8.1 AFAIK

Archlinux via PXE

Similar Messages

Maybe you are looking for