can you post the command you ran to generate the winpe image, and an ls -lR on your tftproot directory ?
My last attempt was using the Provisioning Manager GUI to generate the WinPE tools using the following settings;
Image Toolkit Host = HOU-WINXP-PRO
Image Type = WinPE 2.0
Architecture = X86
Win AIK Directory Path = C:\Program Files\Windows AIK
CreateWinPE Script Directory Path = c:\Bladelogic\745-753-provision-files\provisioning\winpe
Boot Image Target Directory = //HOU-BLAPP/usr/nsh/tftproot
My current tftproot contents look like;
so my tftproot looks like:
drwxr-xr-x 2 root root 4096 Nov 16 2007 boot_2_0
-rwxr-xr-x 1 root root 417896 Nov 13 2007 bootmgr.exe
drwxr-xr-x 3 root root 4096 Feb 28 2008 X86PC
r1 root root 262144 Nov 13 2007 BCD
r1 root root 3170304 Nov 13 2007 boot.sdi
r1 root root 167468307 Nov 13 2007 WinPE.wim
drwxr-xr-x 9 root root 4096 Jul 26 20:32 pxelinux
r1 root root 25068 Nov 13 2007 pxeboot.0
-rwxr-xr-x 1 root root 44 Jul 26 20:32 pxeboot.msg
-rwxr-xr-x 1 root root 13472 Jul 26 20:32 pxelinux.0
drwxr-xr-x 2 root root 4096 Aug 4 15:19 pxelinux.cfg
so i think you've got the BCD, WinPE.wim and boot.sdi in the wrong place.
Also, i've seen that the WinPE.wim is case sensitive so it needs to be named like that - WinPE.wim.
also, when you generate the pe image, - the target dir should be like //foo/bar/tftproot/boot_dir - i've found if you try and change the path of that 'boot_dir' location, the pe boot fails, so i think that has to stay the same (the relative path, not the whole thing)
Those two items seemed to help...
I removed all the previous WinPE files from my tftp server root. Then;
1) Run the "Image Creation" from the gui again
This time using //HOU-BLAPP/usr/nsh/tfproot/boot_2_0 as the "Boot Image Target Directory". The files were created in tftproot on the pxe server using the same layout as shown in the working tftproot example.
2) I changed the winpe.wim file as suggested to WinPE.wim
I am now able to PXE boot up to the WinPE bootstrap, it's running the disk partition phase now. Waiting to see if the entire provisioning will now run using WinPE
On to the next problem...
WinPE disk partition completed and it moved through the other stages and rebooted the Windows installer, and that failed with;
On the Provision Manager status - At step 14 of 16, Phase 1 OS Installation
On the target system console;
Exiting PXE boot
BOOTMGR is missing
Press CtrlAltDel to restart
So, I assume there was supposed to be a "bootmgr" found on the local drive?
there was a post in the forums or kb about registry entries in the pre-script in the system package you need to put in, or you might run into this problem - i think that's the problem. look for like 'registry system package'
and then re-run the provision job.
I ran a test provision run with the pause between stages option so that I could see what fails and I found;
dskprt-post.bat calls "bootsect.exe /nt52 c:" and drive c: cannot be found even though the previous disk partition step claims success and 100% format completion. The bootsect error message is;
"Could not map drive c: to an associated volume device object"
A ctrl-C to get a prompt and a quick test of;
fails as there appears to be no C: drive.
Any clue as to why the c: drive that was just formatted is "gone"?
Problem appears to be no assigned drive letter in diskpart
I broke to the command prompt and ran diskpart. The disk appeared OK and the volumes were created, but I noticed volume 1 did NOT have the assigned drive letter "C:" in diskpart. I assigned LETTER=C using diskpart, rebooted and the dskprt-post ran OK and the installation continued.
So now the question is, why did dskprt not assign the drive letter correctly using diskpart?
A bit more research seems to indicate...
select disk 0
create partition primary
select partition 1
FORMAT fs=NTFS label="SYSTEM"
I assume the drive assign letter command is missing? Perhaps;
inserted between the "select" and "active" lines?
how many disks are in this system?
you should file a defect w/ support for this.
I am getting the same problem as Dan on 7.5.0. what creates part.txt? I have created a support call 33086 for this
BladeLogic auto generates this based on what you enter in for your disk partitions, unless you manually specify the diskpart commands in that section ( 'use script for disk partitioning')
I am also receiving this error. Did you get a resolution to the call?
You should try manually specifying the partitioning in the system package and use diskpart commands. that will be a quick workaround, and then follow up w/ support to see if they have a fix.