Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About richard612

  1. Anyone try PXE booting (using Windows Deployment Service) an IBM x3650 using Windows Server 2008 RTM's boot.wim? It freezes at the end of the progress bar (before the graphical logo screen). Not even sure how to start diagnosing this one as there are no logs to review so early in the boot cycle.
  2. One PE to Rule Them All?

    That's exactly what I'd like to do but I don't know what executables/packages are involved.
  3. One PE to Rule Them All?

    Today, we have four VistaPE boot images on our Windows Deployment Server: 1. WDS deployment 2. WDS capture 3. WinRE 4. A generic PE environment in which I can run our legacy Ghost-like utility (Rdeploy). Is there a way that I can create ONE boot image within WDS that can do all of these? I know that WinRE launches RecEnv.exe and that the sources folder is needed. What about the deployment and capture functions? It seems wasteful to have to maintain four boot images of essentially the same environment.
  4. Solved. Removing our Cisco WLAN drivers nukes layout.inf from \windows\inf. It's a known bug in the Cisco installer. WFP needs layout.inf. EM
  5. My troubles are back. WFP works great on my D400's and D600's. When I drop this image onto a GX110 (uses the same HAL as the laptops), WFP stops working. I know that it survives the sysprep process, just not the migration to foreign hardware. WTF?
  6. What prompted this question is my inability to get Windows File Protection working. For some reason, WFP would not recognize my i386 folder and would always prompt for a CD. Yes, I left off the trailing \i386 in the reg keys. Nothing I tried worked. SP1 reinstall, re-copying i386 from my media, etc etc. I ended up doing an in-place reinstall of Windows XP with integrated SP1 using source files on the local HDD. After all's said and done, WFP now works and I don't have to worry about the location of service pack files since it's been slipstreamed by Microsoft. Now my new challenge is to get sysprep to stop munching my default user profile. It didn't do this prior to the OS reinstall. I left out a few things in SYSPREP.INF (like the PC name and domain name) so that the tech could name the PC and join it to the domain during mini-setup. This worked perfectly in the past. Now when I run sysprep, certain things in SYSPREP.INF are being read but others are ignored and mini-setup is running fully unattended. The PC comes back up with a totally stock default user profile although the administrator's profile is fine. My intended default user profile has plenty of customizations (theme/icons/etc) but it vanishes after sysprep. Is there another answer file hiding out somewhere? RM
  7. Slightly OT here... I'm working with a corporate ghost image here (using sysprep) and I'm wondering about the correct way to include an i386 folder in the image for Windows File Protection to utilize. Copying a i386 folder to the HDD is simple, but to where should it be copied and how do I correct the layout.inf to reflect this source path? Simply pointing the SourcePath reg key to the i386 folder doesn't work. I strongly suspect that my layout.inf needs modification. Any thoughts?