• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. zguo
    3. Topics
    Z
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 14
    • Best 1
    • Controversial 0
    • Groups 0

    Topics created by zguo

    • Z

      Unsolved Error messages, Windows 11, Sysprep

      Windows Problems
      • • • zguo
      2
      0
      Votes
      2
      Posts
      473
      Views

      george1421G

      @zguo There are two things I can think of to create the initial error message.

      You have the fog client installed and the services hasn’t been disabled before image capture. The fog client is starting to do its action before windows is fully installed. You have a driver install that is forcing a spontaneous (all of a sudden) reboot of the computer before windows is installed.
    • Z

      Unsolved Sysprep cleared most of the configuration on Win10

      Windows Problems
      • • • zguo
      2
      0
      Votes
      2
      Posts
      505
      Views

      george1421G

      @zguo Here is an unattend.xml file that I used back with windows 7 and later with windows 10. I have to be clear I don’t do as much imaging as I did back in 2022, so I don’t know if this unattend.xml file is still valid. It should be, but start with it and see where it takes you. https://forums.fogproject.org/post/87392

      Staring with a proper unattend.xml file is the key to getting a good target deployment. You will want to use this command when you call sysprep. c:\windows\system32\sysprep\sysprep.exe /quiet /generalize /oobe /shutdown /unattend:C:\Windows\Panther\Unattend.xm

      Sysprep will still remove something out of your target image. But you can put most back on a deployment by using the unattend.xml file to create user accounts, connected to AD, and name the system as well as changing the local. If the option is not avaialble in the unattend.xml file, there is a batch file that gets called at the end of winsetup called setupcomplete.cmd you can put commands there to create users or install software that must be installed after imaging is complete, or use the first run section of the unattend.xml file with the auto login option for the first time windows boots, auto login to the desktop, run the first run section of the unattend.xml file then reboot.

    • Z

      Cannot PXE boot on Client PCs

      General Problems
      • • • zguo
      20
      0
      Votes
      20
      Posts
      3.1k
      Views

      Z

      @george1421 Cool! After reinstalling FOG, ipxe.efi has file sizes now so the ASUS PC can PXE boot with ipxe.efi. Thank you very much!

    • 1 / 1