• Register
    • Login
    • Search
    • Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Solved FOG + Sysprep + Windows 10 1803

    General
    2
    26
    4104
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      Florent @george1421 last edited by

      @george1421
      Thanks, i will do new test with this next week.

      Actually i use this sed to modify xml :

      sed -i "s/UCXXXX/$hostname/" /mnt/win/Windows/System32/Sysprep/sysprep.xml
      sed -i "s/ouxx/$hostadou/" /mnt/win/Windows/Panther/unattend.xml
      

      Florent
      Bretagne, FRANCE

      george1421 1 Reply Last reply Reply Quote 0
      • george1421
        george1421 Moderator last edited by

        @florent Well I have found that you will have better success with Win10 to place the unattend.xml script in the Panther’s directory than in the older Sysprep directory. Also make sure that you only have one unattend.xml in your computer. Windows 10 looks in panther first.

        Look at the fog.ad script here: https://forums.fogproject.org/topic/8889/fog-post-install-script-for-win-driver-injection/3

        I do have other scripts that perform other actions, but in this script you see how to update the unattend.xml file in a post install script.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        F 1 Reply Last reply Reply Quote 0
        • F
          Florent @george1421 last edited by Florent

          @george1421
          Hi,
          Yes same problem today even with your sysprep 😞
          I take everything from scratch

          Only difference is i do this command :

          c:\windows\system32\sysprep\sysprep.exe /generalize /oobe /shutdown /unattend:C:\Windows\System32\Sysprep\sysprep.xml
          

          And in my post deploy script i copy and sed to this

          C:\Windows\System32\Sysprep\sysprep.xml
          

          and

          C:\Windows\Panther\unattend.xml
          

          I go to try same command like you (in your command and FOG script it’s unattend.xml or Unattend.xml ?).

          After doing your sysprep command and shutdown, you upload your image on FOG ?
          In your post deploy script you use only sed or you use other tricks related to your image ? (cleanup files or folder or other)

          Thanks

          Florent
          Bretagne, FRANCE

          1 Reply Last reply Reply Quote 0
          • george1421
            george1421 Moderator @Florent last edited by

            @florent Yes works with 1803

            Here is my sysprep command
            c:\windows\system32\sysprep\sysprep.exe /quiet /generalize /oobe /shutdown /unattend:C:\Windows\Panther\Unattend.xml

            Ah I now see you are a back working on the same problem again:
            https://forums.fogproject.org/topic/11920/windows-10-1803-sysprep-problem/6

            What I do in fog post install script is to call sed to run on the unattend.xml script as referenced above to search for “<ComputerName>W10CBB</ComputerName>” and replace it with “<ComputerName>${hostname}</ComputerName>” where ${hostname} is supplied by FOG.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

            F 1 Reply Last reply Reply Quote 0
            • F
              Florent last edited by

              Thanks for your response.
              Your method works on Windows 10 1803 ?
              Have you an example of your template of unattend.xml ?

              Florent
              Bretagne, FRANCE

              george1421 1 Reply Last reply Reply Quote 0
              • george1421
                george1421 Moderator last edited by

                Fogprep, NOT to use anymore.

                In my company’s case we don’t use the FOG Client to connect the computer to AD. We use the unattend.xml file. When we sysprep before capture we run the sysprep command and point to our custom unattend.xml file. We also use the unattend.xml file to name the computer.

                I give examples of using a FOG Postinstall script to “change” the unattend.xml file settings after FOG puts the image onto the target computer’s hard drive and before windows starts for the first time.

                https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script

                There are additional examples of post install scripts here.
                https://forums.fogproject.org/topic/7391/deploying-a-single-golden-image-to-different-hardware-with-fog

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                1 Reply Last reply Reply Quote 0
                • 1
                • 2
                • 2 / 2
                • First post
                  Last post

                133
                Online

                10.4k
                Users

                16.4k
                Topics

                150.5k
                Posts

                Copyright © 2012-2023 FOG Project