Microsoft Windows Vista Community Forums - Vistaheads
Recommended Download



Welcome to the Microsoft Windows Vista Community Forums - Vistaheads, YOUR Largest Resource for Windows Vista related information.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so , join our community today!

If you have any problems with the registration process or your account login, please contact us.

Driver Scanner

Windows PE PXE integration - boot options

microsoft.public.windows.vista.installation setup






Speedup My PC
Reply
  #1 (permalink)  
Old 03-08-2007
=?Utf-8?B?bWlyZWQ=?=
 

Posts: n/a
Windows PE PXE integration - boot options
Hello,

we have successfully integrated Windows PE 2.0 in our existing pxelinux
based PXE environment - no major problems with that.

However, there is one point we did not achieve yet:
We want to be able to boot different Windows PE environments (eg. depending
on the IP address or a user selection).
For example, our default image is a very basic Windows PE without any major
modifications. However, in our labs we want to start an environment that
automatically reinstalls the computers. And other computers do not need the
x86 but the amd64 version of Windows PE.

Our problem is that we did not find a way to cleanly do this, as Windows PE
at least at one point seems to have a hard coded path entry and we do not
know how/if we can change this.

I will try to describe our installation and the PXE boot to make clear what
exactly our problem is:

To create the Windows PE image for a PXE deployment, we used the following
Technet article:
http://technet2.microsoft.com/Window...e06d91033.mspx

(with some help from
http://flimflan.com/blog/DeployAWinP...ndTheWAIK.aspx )

We copied the files to the right place at our TFTP server.

When a client boots, the following happens:
The client gets its TFTP server and the file to load using PXE. This way the
client boots a boot menu (using pxelinux and (vesa)menu.c32). In this boot
menu, a user can select different boot entries; the menu displayed depends on
the clients (eg. staff vs. computer labs).

Now one of these boot entries is Windows PE. If this is selected, the
following steps are run:
- the PXE boot system loads pxeboot.n12 (that we had to rename to pxeboot.0)
- pxeboot.n12 loads the boot manager, bootmgr.exe
This path (in the root of the TFTP server) seems to be predefined.
- the boot manager loads Boot\BCD
This path seems to bbe predefined, too.
- The boot manager reads the config file (BCD)
It loads the ramdisk boot.sdi and the WIM file (WinPE.wim).
The WIM file can be specified using the options ramdiskath and
device ramdisk= using bcdedit.
- Windows PE starts.

The problem is that the path to the BCD file is hard coded.
We could change the BCD file to provide multiple different WIM files.
However, this is one step too late for us:
The BCD file is not client specific. It is not possible to specify different
WIM files for different clients. Therefore we cannot boot different
environments on different hosts without user intervention.

Therefore, what we would need is a possibility to change the path to or the
name of the BCD file. Then we could load different Windows PE configurations
as needed.
The problem is, that the file- and pathnames up to this point are all fixed
- at least I did not find a documented way to change them.
I even had a look at bootmgr using a hex editor, but I could not find where
it is loaded there ...

Is there any way to change that filename or path?
Ideally this would be some kind of environment variable (passed using the
"append" statement of pxelinux).


Reply With Quote
Sponsored Links
  #2 (permalink)  
Old 03-08-2007
Daveg
 

Posts: n/a
Re: Windows PE PXE integration - boot options
Windows Deployment Services provides the functionality you are looking
for if I understand your post correctly and is free. It seems that
you are trying to troubleshoot this issue from the client instead of
the PXE server itself. This link below provides a summary of some WDS
features including X86 versus X64 etc.

http://www.microsoft.com/windowsserv.../services.mspx

Daveg

Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
PXE Booting Vista/PE 2.0 Using PXELINUX.0 =?Utf-8?B?TEFORGVza0xhYlJhdA==?= microsoft.public.windows.vista.installation setup 3 09-10-2008 18:57
Windows-Mail integration to sidebar alex speedy microsoft.public.windows.vista.mail 4 05-03-2007 00:46
XP & Vista Boot Options Andy Roberts microsoft.public.windows.vista.general 20 03-01-2007 03:13
Dual Boot Options =?Utf-8?B?SS4gUmF1?= microsoft.public.windows.vista.general 8 02-28-2007 23:02
XP & Vista Boot Options Andy Roberts microsoft.public.windows.vista.installation setup 20 01-29-2007 22:20




All times are GMT +1. The time now is 15:26.




Driver Scanner - Free Scan Now

Vistaheads.com is part of the Heads Network. See also XPHeads.com , Win7Heads.com and Win8Heads.com.


Design by Vjacheslav Trushkin for phpBBStyles.com.
Powered by vBulletin® Version 3.6.7
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.6.0 RC 2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120