Hello dear guest!

Boot Land is a community driven pc software site established since 2006 and focused on recovery/backup boot disks, research of Microsoft Windows 2000/XP/2003/Vista/7 install/deployment/lease/antivirus/antispam tools, customizing Microsoft Windows PE administration systems and even learning how to recover computer data from disaster situations!

How about joining our boot disk community? So do it. Life's short!

  - You get free access to our newsletter with all the interesting buzz about boot disks
  - We share publicity revenue with everyone who wishes to participate at the forums
  - Publicity is never, never, never displayed to members (along with many other cool things)
http://boot-land.net/register


 PXE Boot Guide using Windows XP server, Install 2K/XP/2K3 (RIS), Vista/2008/7 + boot PE, WinPE, Parted Magic
Rating 5 V
post Aug 20 2009, 10:41 PM
Post #1
diddy
Member   **
Group: Tutorial Writer

  Joined: 3-July 08
Posts: 78
Thank(s): 43


New draft completed - available here

Draft v2 includes instructions for using grub4dos as the PXE boot loader/file.

Setting Up A Windows XP PXE Server (DRAFT v2)

Guide covers -
  • Install Windows 2000/XP/2003 (RIS)
  • Install Windows Vista/2008/7 from a network share
  • Boot disk images
  • Boot WinPE (XP/2003 based - e.g. LiveXP, PEBuilder)
  • Boot WinPE 2.*/3.0
  • Boot Linux (Parted Magic example included)


Includes download link for an offline version of the guide (in .htm format). Some scripts are included (in the offline download) for automating various sections.

Feedback welcome - please remember it is still in draft.



Enjoy,

diddy


--------------------


3 user(s) said "Thank you!" to diddy for this fantastic post:
maanu, rsuren, wjoe
+Quote Post
2 Pages V   1 2 >  
Start new topic
Replies (1 - 9)
post Nov 28 2009, 04:55 PM
Post #2
allanf
Gold Member   *****
Group: .script developer

  Joined: 5-June 07
Posts: 1,116
Thank(s): 73


Hi diddy

Thanks for the guide.

I have been trying to PXE Boot WinPE 2.1 (bootfile pxeboot.n12) in VirtualBox with little success - a 'Windows failed to start... \Boot\BCD... 0xc0000001" screen.

Researching the matter, I came across a message by Bubble here relating to the problem with Boot Manager entry names, i. e. "Ramdisk options" for all entries.

QUOTE
The solution? Delete '{ramdiskoptions}'s description, something like:

> Bcdedit /store /deletevalue {ramdiskoptions} description

And now, the boot entries have no description to inherit, and so display their own.

I haven't tried it, so can't vouch for it - just stumbled across it and recalled the note in your guide.

Also, I can't seem to locate your batch files in the downloadable version of the guide. In particular, I was wanting to look at your 4a_WinPE.cmd and 4b_WinPE.cmd. How do I find them?

Regards smile.gif


--------------------
Reminding lancelot: You know what a "bugie" is.
It's not a bug; it's that green thing hanging out of your snotty nose.
... :rofl: ...
+Quote Post
post Nov 28 2009, 05:06 PM
Post #3
was_jaclaz
Finder   ******
Group: Advanced user

  Joined: 14-July 06 From: Gone in the mist

Posts: 7,227
Thank(s): 562


Italy


QUOTE (allanf @ Nov 28 2009, 06:55 PM) *
Researching the matter, I came across a message by Bubble here relating to the problem with Boot Manager entry names, i. e. "Ramdisk options" for all entries.


Interesting.

Just for the record, it seems that different versions of BOOTMGR behave differently:
http://www.msfn.org/board/multi-boot-and-tftp32-t125543.html
http://www.msfn.org/board/winpe-v2-1-usb-hdd-t114711.html

cheers.gif

jaclaz


--------------------

Light Blue Ribbon Campaign for Freedom of Skin

But ... then, why?
+Quote Post
post Nov 28 2009, 08:49 PM
Post #4
cdob
Frequent Member   ***
Group: Advanced user

  Joined: 7-November 07
Posts: 295
Thank(s): 62


Yes, Windows 7 bootmgr list {ramdiskoptions} description, if available.

http://diddy.boot-land.net/pxe/files/winpe.htm
remove /d "Ramdisk options"
CODE
bcdedit.exe /store C:\PXE\tftpboot\Boot\BCD /create {ramdiskoptions} /d "Ramdisk options"
CODE
bcdedit.exe /store C:\PXE\tftpboot\Boot\BCD /create {ramdiskoptions}


In addition you may use different {ramdiskoptions} parts.
Imagine there are different \boot\boot.sdi used in future, this is not required so far.

{ramdiskoptions} is a predefined guid variable.
Use "BCDedit.exe /create /device" to create a second {ramdiskoptions} guid.

Example
CODE
call :add_W7RE \sources\BOOT7_86.WIM x86

:add_W7RE
for /f "tokens=1-3" %%a in ('BCDedit.exe /store %BCD% /create /device') do set guid_options=%%c
BCDedit.exe /store %BCD% /set %guid_options% ramdisksdidevice boot
BCDedit.exe /store %BCD% /set %guid_options% ramdisksdipath \boot\boot2.sdi

for /f "tokens=1-3" %%a in ('BCDedit.exe /store %BCD% /create /application OSLOADER') do set guid=%%c
BCDedit.exe /store %BCD% /set %guid% description "Windows 7 Recovery Console %2"
BCDedit.exe /store %BCD% /set %guid% osdevice ramdisk=[boot]%1,%guid_options%
BCDedit.exe /store %BCD% /set %guid% device ramdisk=[boot]%1,%guid_options%
BCDedit.exe /store %BCD% /set %guid% systemroot \windows
BCDedit.exe /store %BCD% /set %guid% path \windows\system32\boot\winload.exe
BCDedit.exe /store %BCD% /set %guid% detecthal Yes
BCDedit.exe /store %BCD% /set %guid% winpe Yes
BCDedit.exe /store %BCD% /displayorder %guid% /addlast
goto :eof


Or use different {ramdiskoptions} always.
Set description to both ramdiskoptions and OSLOADER section.
This should work at all different bootmgr.
1 user(s) said "Thank you!" to cdob for this fantastic post:
diddy
+Quote Post
post Mar 24 2010, 01:30 PM
Post #5
itcrew
  
Group: Members

  Joined: 17-January 08
Posts: 1
Thank(s): 0


South Africa


Hey Diddy


Greate Guide, there is no cmd scripts though. Please can you update
+Quote Post
post Mar 24 2010, 09:07 PM
Post #6
Tense
Newbie   *
Group: Members

  Joined: 12-March 10
Posts: 24
Thank(s): 1


United States


I second that. There are no scripts in the download. Can you readd them?
+Quote Post
post Mar 24 2010, 10:46 PM
Post #7
diddy
Member   **
Group: Tutorial Writer

  Joined: 3-July 08
Posts: 78
Thank(s): 43


Sorry for the mix up with the scripts.

I've re-uploaded the guide - scripts are included this time.

diddy

p.s. Child commitments continue to keep me busy so appologies for lack of responses over the past few months.


--------------------
+Quote Post
post Mar 26 2010, 08:23 PM
Post #8
Sha0
Frequent Member   ***
Group: Advanced user

  Joined: 1-August 07 From: Boot-Land Forums

Posts: 403
Thank(s): 109


Canada


A very nice guide. The RIS "INF file XXX is corrupt or missing, status 21." error has been addressed in Syslinux 3.83, so anything newer should be fine.

http://syslinux.zytor.com/archives/2009-August/013127.html
http://git.kernel.org/?p=boot/syslinux/sys...c135cb5793d847e
+Quote Post
post Mar 27 2010, 04:21 PM
Post #9
Aviad Raviv
  
Group: Members

  Joined: 19-June 08
Posts: 8
Thank(s): 0


Israel


ok, i don't wanna sound rood and trash all your hard work.

but all of this has been done before into a very well working virtual appliance call UDA.

the creator has incorporated a lot of the stuff you show in your guide into a Linux free VM that can be used using a simple webGUI.

with that said, both I (as a long time user of this product) and its creator have moved on because we found two things to be true:

1. if your going to install windows with a flat install over the network (witch both of us no longer recommend) your better off using MSs RIS\WDS as reverse engineering the process doesn't bring anything new to the table, and doing it just gets harder with every new release and you can implement the additions done with PXElinux like boot ubuntu and acronis just fine on a server thats hosting WDS\RIS with a regular MS server.

2. flat installs are a thing of the past... images are way easier to get running with less effort and take a fraction of the time to deploy.

i have moved from the UDA project to the FOG one because of these two reasons and i have added to it all the additions i have done to UDA in my youtube films.

my youtube channel (shameless self promotion):
http://www.youtube.com/watch?v=mJZsDQtmQvg...&playnext=1

the UDA home page (homage):
http://www.ultimatedeployment.org/

the FOG page (recommended):
http://www.fogproject.org/
+Quote Post
post Mar 27 2010, 07:23 PM
Post #10
RCollewijn
  
Group: Members

  Joined: 21-December 08
Posts: 1
Thank(s): 0


Netherlands


QUOTE
Note - due to an error the menu entries created above will not display properly when bootmgr.exe (the WinPE boot loader) loads the BCD store. The entry for x86.wim should display WinPE (x86) and amd64.wim should display WinPE (amd64), however both entries read as Ramdisk options


You can solve this by using the bootmgr.exe from vista rtm

Robert Collewijn
Deployment Solutions
+Quote Post

2 Pages V   1 2 >
Reply to this topic
3 User(s) are reading this topic ()



Collapse

  Topic Replies Topic Starter Views Last Action
No new Boot windows from extended partition
55 xpt 2,638 Yesterday, 06:29 PM
Last post by: Wonko the Sane
No New Posts Windows 7 64 bit repair disk problem
Windows 7 64 bit repair disk fails to load - Solved -
6 dagar7 177 Yesterday, 08:17 AM
Last post by: Wonko the Sane
No New Posts Boot-loader for INT 0x13 mapping non-contiguous files
8 supaJ 376 18th June 2010 - 08:01 PM
Last post by: sebus
No new Topic has attachmentsXP styles in PE
179 MedEvil 17,363 17th June 2010 - 09:20 PM
Last post by: Crextis
No New Posts Boot with SYSLINUX
9 mrt_doulaty 664 16th June 2010 - 07:04 AM
Last post by: mrt_doulaty







  
Display Mode: Switch to: Standard · Linear+ · Switch to: Outline

Track this topic · Email this topic · Print this topic · Subscribe to this forum