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

    Windows Fails to Install

    Scheduled Pinned Locked Moved
    Windows Problems
    6
    29
    10.0k
    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
      zpoling @Quazz
      last edited by

      @Quazz

      Yes, we use /oobe /generalize /reboot in that order.

      So this is a known issue?

      9am-5pm Eastern | Monday-Friday

      Q 1 Reply Last reply Reply Quote 0
      • Q
        Quazz Moderator @zpoling
        last edited by

        @zpoling That makes a driver issue unlikely, so most likely it’s an issue with an unattend.xml file, at least in my experience.

        Z 1 Reply Last reply Reply Quote 1
        • Z
          zpoling @Quazz
          last edited by

          @Quazz

          Hmm, we’ve always used the same unattend.xml file for all of our images without issue. I actually created another image today that used this unattend file. Uploaded the image and pulled it back down without any issue. It’s a very basic unattend to my understanding.

          I’ll keep trying to image other G1’s and see if one finally works. If it does, I’ll see if there are some hardware differences.

          9am-5pm Eastern | Monday-Friday

          Q 1 Reply Last reply Reply Quote 0
          • Q
            Quazz Moderator @zpoling
            last edited by

            @zpoling For a test, you could try to remove the file before sysprep and capture and see if that resolves the problem.

            Z 1 Reply Last reply Reply Quote 1
            • Z
              zpoling @Quazz
              last edited by

              @Quazz I’m sorry, do you mean remove the unattend file and upload the image without syspreping?

              9am-5pm Eastern | Monday-Friday

              Q 1 Reply Last reply Reply Quote 0
              • Q
                Quazz Moderator @zpoling
                last edited by

                @zpoling You can sysprep, just with the unattend file removed.

                1 Reply Last reply Reply Quote 0
                • M
                  michael_f @zpoling
                  last edited by

                  @zpoling I think I ran into the same problem:
                  As I move fog to a new server I took the chance to upgrade Fog from 1.2 to trunk.

                  With Fogserver 1.2 I used to install the legacy fog client in the image which worked without problems.

                  The new fog client, at least v0.10.6 seams to break windows setup. Uninstalling the client in the image solved the problem with the windows setup for me.

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

                    @michael_f said in Windows Fails to Install:

                    The new fog client, at least v0.10.6 seams to break windows setup. Uninstalling the client in the image solved the problem with the windows setup for me.

                    Ah. We’ve seen this before. The answer is to disable the FOG Service before you take the image, and then in your unattend.xml file re-enable the service after the unattend file is done with everything else.

                    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/

                    B 1 Reply Last reply Reply Quote 0
                    • B
                      boeleke
                      last edited by boeleke

                      Hi there!
                      I’m beeen searching for a sollution since 04/05/2016!
                      Didn’t find any solution & now you guys got the same problem as me!
                      I also think it is the FOG client. I prepped more images , and after the install from deepfreeze / fog client i get this error to.

                      Big big problem 😉 Tomorrow is my last day of internship so i can’t image 🙂 ^^

                      1 Reply Last reply Reply Quote 0
                      • B
                        boeleke @Wayne Workman
                        last edited by

                        @Wayne-Workman

                        How do you disable? Just in the “services”?
                        What line do you need to add in the XML - file to activate this?

                        Crap! I’m searching for a week behind this error and its FOG client grrrr

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

                          Yes, just disable it in service before taking the image.

                          Here’s a post that shows how, This particular person was experiencing a particular problem in this post, but these issues have since been resolved in the current FOG Client. What he says about enabling the service is still valid.

                          @boeleke @Psycholiquid said in Rename fails but adds client to domain.:

                          Ok using SVN 3702 with Client 0.9.0 I am getting the following happening:

                          I create the image in Audit mode
                          Install all software and updates Install FOG Service software 0.9.0

                          In the SetupComplete.bat I have the following commands

                          sc config FOGService start= auto
                          net start FOGService

                          Set windows to OOBE and reboot uploading image to FOG server.

                          Once complete I push the image out to one of the hosts I have setup in FOG right now. IT runs through the whole image setup and completes to the Desktop.

                          From there is joins the domain without trying to rename the computer at all. This create a problem as there will be multiple computers all trying to join the domain under the same name causing a trust issue in the process.

                          Here is the log from the computer I just did. Keep in mind this one is constantly rebooting due to it trying to change the name after it has already joined the domain:

                          fog.log

                          Source: https://forums.fogproject.org/topic/5490/rename-fails-but-adds-client-to-domain/27

                          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/

                          B M Z 3 Replies Last reply Reply Quote 1
                          • B
                            boeleke @Wayne Workman
                            last edited by

                            @Wayne-Workman said in Windows Fails to Install:

                            sc config FOGService start= auto
                            net start FOGService

                            Sooo only this 2 lines :

                            “sc config FOGService start= auto
                            net start FOGService”

                            in my setupcomplete.cmd and it will work?
                            Oh my!

                            Is it possible to remove this bug from the installer?
                            Its weird because the old V0.9 fog didn’t gave any problems to me 🙂

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

                              @boeleke All I can say is try it and see.

                              To explain the problem in more detail, when your sysprep stuff is happening after deployment, the fog client starts up and does it’s thing too (rename, reboot, etc.), and breaks the unattend.xml and setup complete stuff. The simple answer is just to disable the service before taking the image, and set up your golden machine so that it re-enables the service after all your stuff is done.

                              Also - it’s not a bug. The FOG Client is designed to do it’s job.

                              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/

                              B 1 Reply Last reply Reply Quote 2
                              • B
                                boeleke @Wayne Workman
                                last edited by

                                @Wayne-Workman said in Windows Fails to Install:

                                @boeleke All I can say is try it and see.

                                To explain the problem in more detail, when your sysprep stuff is happening after deployment, the fog client starts up and does it’s thing too (rename, reboot, etc.), and breaks the unattend.xml and setup complete stuff. The simple answer is just to disable the service before taking the image, and set up your golden machine so that it re-enables the service after all your stuff is done.

                                Also - it’s not a bug. The FOG Client is designed to do it’s job.

                                But maybe a tip , put it in the wiki.
                                i searched like i was crazy last week to all forums. But maybe i’m wrong , i’m just going to try it out. I’ll update this tomorrow when i can test! Thanks!

                                1 Reply Last reply Reply Quote 1
                                • M
                                  michael_f @Wayne Workman
                                  last edited by

                                  @Wayne-Workman OK, I thought about installing the fog client after imaging by calling the msi-package from setupcomplete.bat, but this way is even easier.

                                  I can confirm this working for me.

                                  Thank you!

                                  1 Reply Last reply Reply Quote 1
                                  • B
                                    boeleke
                                    last edited by boeleke

                                    I can confirm its also working for me :).
                                    But if I was you guys , i would put this on the FOG-WIKI. @Developers

                                    This is going to be a problem for many of us & maybe they stop earlier with FOG because that and the don’t know it 😉
                                    But thumbs up for the good work ;)!

                                    1 Reply Last reply Reply Quote 1
                                    • Wayne WorkmanW
                                      Wayne Workman
                                      last edited by

                                      @boeleke @michael_f Ask and you shall receive.
                                      https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

                                      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/

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

                                        Hi,

                                        do you try to restore to vm? i’ve seen several error for example with virtual box when trying to restore an earlier captures sysprepped image.
                                        If yes try the same image on real pyhsical hardware please.

                                        Regards X23

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

                                        1 Reply Last reply Reply Quote 0
                                        • Z
                                          zpoling @Wayne Workman
                                          last edited by

                                          @Wayne-Workman This fixed my original issue as well. Thanks for the help!

                                          9am-5pm Eastern | Monday-Friday

                                          1 Reply Last reply Reply Quote 1
                                          • Wayne WorkmanW
                                            Wayne Workman
                                            last edited by

                                            TO clarify, are you guys putting this in setupcomplete.cmd or setupcomplete.bat ?

                                            I’ve not done this myself yet, so I’m just going off of what you all say.

                                            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/

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

                                            215

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project