JoeDe

Member
  • Content count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About JoeDe

Profile Information

  • OS
    XP Pro x86
  1. OK... This is what I get for using a pre-release version of Windows 7. When I used the released version it works. Go figure.
  2. I need an explaination of what "Make Actvie" means. The format utility does not display the option and bootsect.exe is not on the machine (logged on as administrator). Is the format to be FAT32 or NTFS (Been through this on a 2008 server)?
  3. The stept you mention result in Status: 0xc000000f Info: The boot selection failed because a required device is inaccessable. Which is what started me down this road to begin with. That would be great if it were just that simple.
  4. That's where I'm at at the moment. I'm trying to build the BCD file just to get PE running. My problem is I don't know how the flash drive is referenced in BCD. It's not a partition and default is RAMDISK and no machinism for loading the image on to the RAMDISK. Simplest way is to load from the flash drive and in the Windows Boot Loader section I don't know what the device definition are. No appearent documentation on it either (atleast from MS).
  5. We have an open license agreement with Microsoft and have about 2500 machines in our organization. We have 4 technicians (need I say more). The purpose of this WDS server is to deliver windows operating systems to our machines with as little intervention as possible. I was attempting to use PXE and WDS to accomplish this goal. Our current automation process uses freeDOS and up until now has worked quite well. Newer laptop (US15) driver file are now using filename greater that 8 characters and as DOS really doesn’t support the namespace we need to handle this process differently. The WDS server is a VM server emulating a single Xeon CPU (E5430 @ 2.66GHz) with 1 Gig of RAM and 32-Bit architecture. I need to point out an error – the server is 2008 standard, not R2. DHCP and DNS are running on one of our Windows 2003 SP2 Domain controllers. Neither DNS nor DHCP are running on the WDS box. All the Nics are running 1 gig. It appears that Hostnames are used over IP, but as the question has not appeared in any of me research I can’t really give a definitive answer. The target machines are Dell Mini 10 laptops (Atom processor using US15 Chipset). I’m still open to suggestions, but the boss has instructed me to find an alternative – flash drive or DVD.
  6. Time to bail on deployment. 3 weeks of research on two platforms. This is too complicated and Microsoft's documentation leaves out too much info to actually make it work.
  7. It is possible the TFTP Block size is too large for the client. I'm testing that theory out now with some success. Looks like I have to increase the TFTP time-out period too. Something I'll save for the morning.
  8. Yes they are. The client is on the is on one of the production VLANs.
  9. This WDS process is becoming quite the challenge. I have a 2008 R2 server doing only WDS. DHCP is an MS DHCP server running on another box (Authorized for WDS, options 66 and 67 set appropriately). I have a boot.wim file configured and assigned. The Boot tab on WDS server properties is set for \boot\x86\wdsnbp.com as is option 66 in DHCP. When the client starts up it displays the following: Downloaded WDSNBP... Architecture: x86 Contacting server: 172.16.3.49. TFTP Download: Boot\x86\wdsnbp.com And it repeats forever... What have I missed???
  10. This WDS process is becoming quite the challenge. I have a 2008 R2 server doing only WDS. DHCP is an MS DHCP server running on another box (Authorized for WDS, options 66 and 67 set appropriately). I have a boot.wim file configured and assigned. The Boot tab on WDS server properties is set for \boot\x86\wdsnbp.com as is option 66 in DHCP. When the client starts up it displays the following: Downloaded WDSNBP... Architecture: x86 Contacting server: 172.16.3.49. TFTP Download: Boot\x86\wdsnbp.com And it repeats forever... I have all I can do to keep from going in circles. What have I missed???
  11. I have finished setting up a 2008 deployment server and instaled Windows OPK services, I started following the tutorial mentioned above. One of the first steps failed for what appears to be (atleast to me) an unknown reason. The commend: (Locations are taylored to my server) dism /mount-wim /winfiles:e:\pe\iso\sources\boot.wim /index:1 /mountdir:e:\pe\mount I should point out the correct files are actually in the locations specified. OK... dism returns with: "Error: 87 The /winfiles option is not recognized in this context". The dism log file displays 2 errors: 2010-05-20 07:51:33, Error DISM DISM WIM Provider: PID=3204 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:686 - CWimManager::InternalValidateOptions(hr:0x80070057) 2010-05-20 07:51:33, Error DISM DISM WIM Provider: PID=3204 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:513 - CWimManager::ExecuteCmdLine(hr:0x80070057) I found a typo in the original source. The original commend in the tutorial shows "/WinFile..." the actual parpmeter should be "/WimFile...". Moving on...
  12. Any idea want version of PE wil work to deploy XP Pro?
  13. I am Capturing Windows XP Pro SP3 from a Dell Mini 10 NetBook. The version of Windows PE is "Microsoft Windows [Version 6.0.6000]. The WDS server is on a Windows Server 2003 SP2.
  14. Spent the last several day going through MS documents, articles and discussion groups trying the get Windows Deployment Service to actually work. I have met with only partial success. I have managed to get the legacy portion to work in a blind one-shot manor. Seems limited. The next step was using the current deployment method to work. Documentation has been sufficient to capture the image and save it to a WIM file. I am unable to create a boot image that will actually install that image. Does anyone know how that's done? Anyone know or have complete documentation on this process? HELP!!!