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

    Sysprep cleared most of the configuration on Win10

    Scheduled Pinned Locked Moved Unsolved
    Windows Problems
    2
    2
    504
    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.
    • Z
      zguo
      last edited by

      Knowing that sysprep would solve the SID & GUID issue, so I would like to implement sysprep before capturing a Win10 image. However, I found that sysprep constantly cleared most of the configuration and only kept the installed software.

      Even though I just tried an audit mode, it still cleared some configuration. That means I have to do lots of manual work after deployment. But the point I wanna use FOG is to avoid lots of manual work. I heard that an alternative solution which is new SID is no longer available.

      I have lots of configurations in detail here, including things like network adapter configuration. What should I do before sysprep so ALL the configuration on the PC can be held?

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

        @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.

        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 / 1
        • First post
          Last post

        195

        Online

        12.0k

        Users

        17.3k

        Topics

        155.2k

        Posts
        Copyright © 2012-2024 FOG Project