Deman

Hi, Not sure which build of WAIK I used sorry, it came with the beta version of BDD 2007 which I installed on a removable drive (that has subsequently been wiped) I have the RTM of WAIK installed now but haven't used it The Vista version I used was Release Candidate 2 for Vista Enterprise and Vista Business as well as Enterprise RTM. The same XML file worked for all

Here's a few more Help files actually stepping you through the process (not telling you where to click but showing you) Able to see what programs you regularly run at particular times and then prepare things so it starts quicker There's no more sluggishness once it comes out of sleep/hybernation (I'm told anyway) Dumps graphics management on the graphics card, not the CPU Finally introduces raise priviledge level linux (and Mac?) users enjoy. Dubbed User Account Control There's parental control including control over what Games can be played (R16 not allowed or whatever) Fast User Switching now available for Domain users ReadyBoost and ReadyDrive (basically speaking enables Windows to dump some cache in Flash instead of the HDD to speed things up) Internet Explorer 7 runs in protected mode, apparantly it means it has as much rights to the O/S as say Firefox would Windows Backup has been given a proper overhaul and made much more powerful and easy to use (uses imaging etc) Instant search, far far quicker than XPs Vista x64 contains PatchGuard preventing programs from patching the kernel Address space layout randomizer, ensures system files load at random memory locations instead of being loaded to the same location (Good defense against attackers) There are loads of changes, this time it really is the biggest release since Windows 95. And so it should be, they took long enough. You can read more into it here

Aha, I've swapped from the Windows TFTP service to TFTPd32 with logging functionality and have found what it can't find. But I can't understand why it can't find it That's all very well and good but the bootmgr file is certainly there. Bizzare Edit: I'm an id***, the bootmgr.exe file should of been in the tftp root directory.

Not that i've seen yet. I've looked in the Event viewer but I suppose with Microsoft they could be logging anywhere. Plus I've had it working with just directly linking \Boot\pxeboot.n12 to the PXE bootfile option in DHCP. Thanks anyway

Weird, it should work. It doesn't need to boot from the floppy or USB it just needs to be able to see it and read from it From memory Windows setup looks for a file moments before it opens the setup Window. It should be AutoUnattend.xml (I don't think casing matters) Does the Windows setup take anything from the AutoUnattend into account or does it do the full blown setup asking everything? Or is it not possible to tell? My AutoUnattend for example doesn't include the HDD setup but includes everything else so I reach the HDD prompt but aftwards it goes away on its own

Hmm, the second one (without the .net) is most similar to mine which works (I use .local and left it out of the join domain procedure). Are you entering it in the specialize area? i.e. <settings pass="specialize"> Also does the user account you're using to join the domain have rights to?

Hi, of course. Sorry I should of included it before Unfortunetly I don't have a TFTP server log (that i'm aware of anyway). It's the Server 2003 TFTP service pulled out of the RIS installation The structure is TFTP root D:\Imaging\TFTP Relevent Files and Folders \Boot \pxelinux.cfg \Sources memdisk menu.c32 pxelinux.0 The root folder has Windows deployment services & BDD folders etc in there too Inside Boot is bcd, boot.sdi, bootmgr.exe, hdlscom1.com, hdlscom1.n12, hdlscom2.com, hdlscom2.n12, pxeboot.com, pxeboot.0, WdsConfig.inf, wdsnbp.com & winpe.wim Inside the Sources folder is BOOT.WIM and the pxelinux.cfg\default file is currently Hope this helps

Hi there, I was originally using Windows Deployment Services to provide the booting but thanks to you guys I'm able to cut all that out in favour of something giving me far greater control. Anyway for whatever reason I'm unable to load WinPE 2 through pxelinux. I've tried appending KERNEL \Boot\pxeboot.0 (renamed pxeboot.n12) to the default.0 config file but all I end up getting is tftp download failed, press any key to reboot. I've even tried using /Boot/pxeboot.0 to see if that would work, but still came with the same error Remembering unix/linux is case sensitive I checked the casing of both the command and filename but that's fine If I cut out pxelinux completely and simply set the DHCP bootfile name to be \Boot\pxeboot.n12 it works fine so TFTP is definetly able to find the file, it's just there seems to be a broken link of sorts when pxelinux gets involved. Does anybody have any ideas?