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

Windows 10 zero touch deployment

Scheduled Pinned Locked Moved
General
4
7
1.4k
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.
  • R
    Rizingknight72
    last edited by Dec 4, 2022, 5:46 PM

    Hello all,

    for my school assignment i need to make a Windows 10 zero deployment. I have tried this on a Windows server 2019 but i did not succeed. So this time i try to do this with FOG. I have no idea how to start with this so hope to some answers from here or a guide that will help met with this.

    I will do this all in Vmware workstation.
    The FOG Server will be build on a Centos 7 Machine.
    Does someone know how to do this?

    G 1 Reply Last reply Dec 5, 2022, 1:06 AM Reply Quote 0
    • G
      george1421 Moderator @Rizingknight72
      last edited by george1421 Dec 4, 2022, 7:06 PM Dec 5, 2022, 1:06 AM

      @rizingknight72 said in Windows 10 zero touch deployment:

      i need to make a Windows 10 zero deployment

      Might that be a zero touch windows 10 deployment?

      If yes that is more a windows thing than a deployment tool thing. You can surely do this with FOG, but you can also do this with Microsoft’s MDT (microsoft deployment toolbox). The key is to use an unattend.xml file. This unattend.xml file give windows setup all of the answers that it would normally ask during a normal OOBE windows install. You can use an online tool such as this one to give you a head start on building this unattend.xml file: https://www.windowsafg.com/win10x86_x64_uefi.html

      Once you have the file configured and put it the proper spot in the windows c drive, you will run the sysprep command and point to the unattend.xml file. The sysprep program will configure the computer for image capture. Then you can capture with fog and then deploy with fog.

      But before I would go the fog route. I would take a VM snapshot, then run sysprep and have sysprep power off the computer (with the command line parameter). The boot up the computer. This will test the unattend.xml file for completeness. If the computer doesn’t do a zero touch install by just running sysprep and rebooting thereis no need to capture with FOG. If the boot up winsetup/oobe fails use the vm and restore the snapshot and try again. That is the beauty of developing your golden image using a VM with snapshots.

      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!

      R 1 Reply Last reply Dec 13, 2022, 9:48 PM Reply Quote 0
      • R
        Rizingknight72 @george1421
        last edited by Dec 13, 2022, 9:48 PM

        @george1421 Thanks for the tip. I have a fog server installed and working windows machine. i still am stuck of how to sysprep properly. currently i am using the command:
        C:\windows\system32\sysprep\sysprep.exe /oobe /generalize /shutdown /unattend: C\temp\unattend.xml
        I got this from a college. I am not sure if this is the right way to use this. they also recommend admiin dosbox. any tips here for?

        G L 2 Replies Last reply Dec 14, 2022, 1:18 AM Reply Quote 0
        • G
          george1421 Moderator @Rizingknight72
          last edited by Dec 14, 2022, 1:18 AM

          @rizingknight72 I can’t seem to find my sanatized unattend.xml file that I posted here, but this one is based on my cleaned version: https://forums.fogproject.org/post/112434

          I would strongly suggest that you place your unattend.xml file in this path: C:\Windows\Panther\Unattend.xml

          Then use this command for sysprep

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

          What I do is build the golden image on a VM. Then take a snapshot of the VM just before sysprepping. Run sysprep and have it power off the VM. Now the first time through this process just boot the VM back up, if it runs through OOBE/WinSetup just fine then you know you have your golden image configured correctly. If the system doesn’t run oobe correctly there is no value in capturing it with FOG. Once your golden image is perfected then you can move on to capturing with FOG. If your OOBE fails, then just reset your VM to the last snapshot. If your golden image is perfect, then again revert to the latest snapshot, run sysprep, power off, then capture 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!

          R 1 Reply Last reply Dec 19, 2022, 2:02 PM Reply Quote 1
          • L
            lukebarone @Rizingknight72
            last edited by Dec 14, 2022, 11:31 PM

            @rizingknight72 said in Windows 10 zero touch deployment:

            @george1421 Thanks for the tip. I have a fog server installed and working windows machine. i still am stuck of how to sysprep properly. currently i am using the command:
            C:\windows\system32\sysprep\sysprep.exe /oobe /generalize /shutdown /unattend: C\temp\unattend.xml
            I got this from a college. I am not sure if this is the right way to use this. they also recommend admiin dosbox. any tips here for?

            I would take the space out between /unattend: and the path to the unattend.xml file.

            1 Reply Last reply Reply Quote 0
            • R
              Rizingknight72 @george1421
              last edited by Rizingknight72 Dec 19, 2022, 8:29 AM Dec 19, 2022, 2:02 PM

              @george1421 I have my golden image. everything got executed. but a new problem came up. for some reason i am unable to capture the image.
              df6811e1-0c41-41ea-973f-7468adaeb718-image.png

              9b67fc78-62bb-4b00-be9f-a75c17abdf5e-image.png
              229700f8-cdad-4d5e-bf0f-919d9be8b917-image.png
              This is a new install of FOG. Do you know what i have to do?

              T 1 Reply Last reply Dec 19, 2022, 3:30 PM Reply Quote 0
              • T
                Tom Elliott @Rizingknight72
                last edited by Dec 19, 2022, 3:30 PM

                @rizingknight72 You ahve to create an image definition and assign it to the host.

                Zero touch just means that the image you’re using doesn’t require the machine to be touched after imaging.

                Please review the FOG Documents as this is one of the first things discussed when dealing 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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

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

                159

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project