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

    Automated Deployment

    Scheduled Pinned Locked Moved
    General
    6
    20
    5.1k
    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
      RLane @Tom Elliott
      last edited by

      @Tom-Elliott I didn’t think it would let you sysprep a machine without something defined. I’ll test over the weekend. I’d be curious to know what others use during their sysprep. I’m trying to set this up so once it’s on the login screen, it’s ready to go for the end user. It’s not the end of the world having a tech login to the local admin account to trigger the reboot/rename but this would be ideal to solve properly.

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

        @RLane In my case I don’t let the fog client name/rename the system or connect to AD. I let the sysprep unattend.xml file do that for me. I use a fog post install script to update the unattend.xml file with the machine name and I use a formula to determine the proper OU for the target computer based on the site its deployed at and the (fog) image name sent to the target computer.

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

        and throwing this one out there for good measure too.
        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!

        R 1 Reply Last reply Reply Quote 0
        • R
          RLane @george1421
          last edited by

          @george1421 For someone who is pretty scripting-illiterate, I’ll try to read through it. If anything, all I would do is have the $hostname set the name of the actual host. I have no problem with the client joining the domain. My groups in FOG correlate to the OU that the hosts end in so that shouldn’t be an issue. Interesting tutorials though, thanks for that.

          1 Reply Last reply Reply Quote 0
          • Wayne WorkmanW
            Wayne Workman @Tom Elliott
            last edited by

            @Tom-Elliott said in Automated Deployment:

            @RLane I believe * means random computer name, though I am not 100% sure of that.

            This is fact, an asterisk means unique random name.

            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!
            Daily Clean Installation Results:
            https://fogtesting.fogproject.us/
            FOG Reporting:
            https://fog-external-reporting-results.fogproject.us/

            R 1 Reply Last reply Reply Quote 0
            • R
              RLane @Wayne Workman
              last edited by

              @Wayne-Workman If the field is left empty, doesn’t the /oobe trigger prompt you for a computer name?

              1 Reply Last reply Reply Quote 0
              • x23piracyX
                x23piracy
                last edited by x23piracy

                Answer 2: http://superuser.com/questions/471070/automatically-generating-a-prefixed-hostname-during-sysprep

                If you set the RegisteredOwner & RegisteredOrganization in the “Microsoft-Windows-Shell-Setup” section under oobeSystem, then the auto generated name will be prefixed by the owner then the organisation.

                https://social.technet.microsoft.com/Forums/windows/en-US/604695dd-3ecb-4b8a-9735-21b557084013/windows-7-sysprep-randomly-generated-name?forum=w7itproinstall

                Should be the same as for 10

                Regards X23

                ║▌║█║▌│║▌║▌█

                1 Reply Last reply Reply Quote 0
                • R
                  RLane
                  last edited by

                  So excuse my ignorance here, I removed the ComputerName (*) from my unattend.xml file. After the image process completes, the computer reboots three times due to assorted FOG tasks I’m assuming.

                  The first reboot appears to be for system drivers, changes, etc. immediately after the completion of imaging. The second appears to be to add the computer to the domain. The third reboot is the hostname change.

                  If I could get it to stop here, that would be great. However, for some reason, once a user tries to log in for the first time, it will reboot the computer again.

                  Is this a me problem with a script/unattend issue or something by design of FOG?

                  1 Reply Last reply Reply Quote 0
                  • J
                    Joe Schmitt Senior Developer
                    last edited by

                    @RLane the client is not built to restart a machine on user log in. Perhaps you have a first-time login script that is running?

                    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.

                    R 1 Reply Last reply Reply Quote 0
                    • R
                      RLane @Joe Schmitt
                      last edited by

                      @Joe-Schmitt My SetupComplete.bat is setting my Windows 10 KMS, Office 2016 KMS – activating both. It starts the FOG service, and deletes three files/folders (unattend, etc.)

                      My unattend file has nothing that I can see that would cause a reboot… hmm.

                      1 Reply Last reply Reply Quote 0
                      • J
                        Joe Schmitt Senior Developer
                        last edited by

                        @Rlane could you send me the fog.log of a computer right after it does the user reboot? If you could also tell me at what time the user reboot happened so I can look at the fog.log at the time, it would help greatly.

                        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.

                        1 Reply Last reply Reply Quote 1
                        • R
                          RLane
                          last edited by

                          Welp, I’m sorry for bugging everybody. After working on this all day and night, I found that the wrong unattend file was being used… with a restart set to hit 25 seconds after the first user logs in.

                          On a happy note, my Win10 deployment is finalized, so thanks all for that.

                          Sorry @joe-schmitt @george1421

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

                          161

                          Online

                          12.1k

                          Users

                          17.3k

                          Topics

                          155.4k

                          Posts
                          Copyright © 2012-2024 FOG Project