• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. lkrms
    L
    • Profile
    • Following 0
    • Followers 0
    • Topics 0
    • Posts 2
    • Best 0
    • Controversial 0
    • Groups 0

    lkrms

    @lkrms

    1
    Reputation
    241
    Profile views
    2
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    lkrms Unfollow Follow

    Latest posts made by lkrms

    • RE: After deploye grub fog 1.2.0

      In case it helps someone else, I just had this problem while a USB stick was connected to the computer. Removing it solved the problem.

      Buggy? Yes, but at least it makes sense, I guess 🙂

      posted in FOG Problems
      L
      lkrms
    • RE: Windows 7 Without SysPrep?

      I’ve had the same problem here, because I like to do most of my Win7 image preparation in VirtualBox, then clone my generic VirtualBox image to specific hardware BEFORE running sysprep. [Finally I install hardware- or classroom-specific software, run sysprep and capture.]

      But this winload.exe error has been forcing me to “recover” each pre-sysprep clone, which is time-consuming (and labels every system here as “recovered” in the boot loader). After trying every combination of fogprep, bcdedit and regedit I could find, I did some deeper investigation (including trawling through the BASH scripts that make FOG work, comparing MBRs byte-by-byte, etc.), and I determined that the problem was in the BCD (Boot Configuration Data). The bcdedit commands described here and elsewhere don’t work, because they don’t instruct the boot loader to search anywhere for anything.

      I wasn’t able to find bcdedit commands to replicate what sysprep does to the system BCD store, but here’s what I did to achieve the same result (using VirtualBox snapshots):

      1. Capture a snapshot of a working audit-mode Windows 7 machine. 32-bit or 64-bit doesn’t matter - the BCD data seems to be interchangeable.
      2. Boot your machine, open a command prompt and run: “C:\Windows\System32\sysprep\sysprep /generalize /quit”. The /quit is important; you want the machine to stay up after sysprep so you can collect the BCD store as sysprep leaves it.
      3. If curious, run: “bcdedit /enum”. You’ll see what sysprep has done to your BCD store.
      4. Capture your BCD store: “bcdedit /export C:\generalized.bcd”. Save the resulting file with your other deployment files; mine ends up living in C:\Windows\System32\sysprep alongside my unattend.xml etc.
      5. Feel free to discard the sysprep’d virtual machine. Restore to your step 1 snapshot or similar.
      6. As part of your FOG pre-capture workflow, when not using sysprep, run “bcdedit /import generalized.bcd”.

      I hope this helps someone!

      posted in Windows Problems
      L
      lkrms