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

Computers not joining our Domain during Sysprep

Scheduled Pinned Locked Moved Solved
FOG Problems
5
60
17.3k
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.
  • K
    kyle.heath
    last edited by Jan 9, 2017, 5:45 PM

    I’m also using this command to run sysprep.

    cd c:\windows\system32\sysprep
    sysprep.exe /generalize /oobe /shutdown /unattend:unattend.xml

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by Jan 9, 2017, 6:04 PM

      Is your Windows 10 image an OEM type or Volume License type?

      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

      K 1 Reply Last reply Jan 9, 2017, 6:47 PM Reply Quote 1
      • K
        kyle.heath @Tom Elliott
        last edited by Jan 9, 2017, 6:47 PM

        @Tom-Elliott It’s a Volume License . Windows 10 EDU we use a KMS key.

        1 Reply Last reply Reply Quote 0
        • K
          kyle.heath
          last edited by Jan 9, 2017, 9:04 PM

          Been messing with the setupcomplete and nothing I change fixes the issue?

          T 1 Reply Last reply Jan 9, 2017, 10:02 PM Reply Quote 0
          • T
            Tom Elliott @kyle.heath
            last edited by Jan 9, 2017, 10:02 PM

            @kyle.heath Where is your setupcomplete.cmd file located on the post-sysprepped system?

            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

            K 1 Reply Last reply Jan 9, 2017, 11:17 PM Reply Quote 0
            • K
              kyle.heath @Tom Elliott
              last edited by Jan 9, 2017, 11:17 PM

              @Tom-Elliott I stick it in the C:\Windows\Setup\Scripts folder

              W 1 Reply Last reply Jan 10, 2017, 12:54 AM Reply Quote 0
              • W
                Wayne Workman @kyle.heath
                last edited by Jan 10, 2017, 12:54 AM

                @kyle.heath as Joe said, please post the entire C:\fog.log We can’t help much without knowing what’s in it.

                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/

                K 1 Reply Last reply Jan 10, 2017, 1:34 AM Reply Quote 0
                • K
                  kyle.heath @Wayne Workman
                  last edited by Jan 10, 2017, 1:34 AM

                  @Wayne-Workman I did. There was very little in the FOG log.
                  0_1484012082320_upload-a5d27ea9-098a-4fcb-9f1e-3d96f3cf7cef

                  That’s all that was in it.

                  W 1 Reply Last reply Jan 10, 2017, 1:59 AM Reply Quote 0
                  • K
                    kyle.heath
                    last edited by Jan 10, 2017, 1:55 AM

                    Also…not sure if this matters but I am trying to “capture” my image from my VM. I created a windows 10 VM and set it up the way I wanted it. I fully registered it…and I chose join domain as 1 of the options it gives you when your full register a client. I put the unattend.xml in the sysprep folder and the setupcomplete in the scripts folder.

                    1 Reply Last reply Reply Quote 0
                    • W
                      Wayne Workman @kyle.heath
                      last edited by Jan 10, 2017, 1:59 AM

                      @kyle.heath And you’re looking at c:\fog.log ? If that’s literally it, reinstall the fog client. You should have more in the log just from when you installed it and rebooted before capture.

                      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/

                      K 1 Reply Last reply Jan 10, 2017, 2:06 PM Reply Quote 0
                      • K
                        kyle.heath @Wayne Workman
                        last edited by Jan 10, 2017, 2:06 PM

                        @Wayne-Workman I reinstalled FOG and now there is no file at all. I’ll post a pic. Since I reinstalled FOG should I try to recapture now?

                        0_1484057157004_upload-7cd25363-275c-4590-b26e-8a97d9d689ba

                        W 1 Reply Last reply Jan 10, 2017, 2:08 PM Reply Quote 0
                        • W
                          Wayne Workman @kyle.heath
                          last edited by Wayne Workman Jan 10, 2017, 8:09 AM Jan 10, 2017, 2:08 PM

                          @kyle.heath No. One of the steps you should always do before capture is verify the FOG Client is functioning properly. The way you would do this is look into the fog log for errors. You should see a normal log before you start preparing the system for capture.

                          Check inside of Program Files for a folder called fog, one of them should have it. Look for a fog.log in there.

                          Also what version of Windows? And is this a fresh installation of windows or an upgrade or an old image you updated?

                          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/

                          K 1 Reply Last reply Jan 10, 2017, 2:12 PM Reply Quote 0
                          • K
                            kyle.heath @Wayne Workman
                            last edited by Jan 10, 2017, 2:12 PM

                            @Wayne-Workman Alright the only .log file in the FOG folder is one called zazzles. Here is what’s inside.

                            0_1484057564448_upload-818b3226-54b3-4251-b775-f868a854a5a1

                            W 1 Reply Last reply Jan 10, 2017, 2:14 PM Reply Quote 0
                            • W
                              Wayne Workman @kyle.heath
                              last edited by Jan 10, 2017, 2:14 PM

                              @kyle.heath Please if you are able, copy/paste the logs. This makes the errors you post search-able so others can find them. Plus I can’t see the entire error in that photo.

                              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/

                              K 1 Reply Last reply Jan 10, 2017, 2:16 PM Reply Quote 0
                              • K
                                kyle.heath @Wayne Workman
                                last edited by Jan 10, 2017, 2:16 PM

                                @Wayne-Workman Here is the full log. I can’t copy and paste because it’s from a VM.

                                0_1484057800769_upload-dccd29e9-94fe-4d6c-b395-8d663ea1f331

                                W 1 Reply Last reply Jan 10, 2017, 2:17 PM Reply Quote 0
                                • W
                                  Wayne Workman @kyle.heath
                                  last edited by Jan 10, 2017, 2:17 PM

                                  @kyle.heath What distribution and version is your FOG Server running on?

                                  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/

                                  K 1 Reply Last reply Jan 10, 2017, 2:25 PM Reply Quote 0
                                  • K
                                    kyle.heath @Wayne Workman
                                    last edited by Jan 10, 2017, 2:25 PM

                                    @Wayne-Workman 0_1484058031470_upload-f2f641de-82c5-4045-8a8f-c824e5a262e2

                                    and we are using Ubuntu 14.04.2

                                    W 1 Reply Last reply Jan 10, 2017, 2:26 PM Reply Quote 0
                                    • W
                                      Wayne Workman @kyle.heath
                                      last edited by Jan 10, 2017, 2:26 PM

                                      @kyle.heath See if you have firewall or apparmor on the server. If you do, disable those at least temporarily. Also try to web-browser from the VM to the fog server and see if that works.

                                      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/

                                      K 1 Reply Last reply Jan 10, 2017, 2:30 PM Reply Quote 0
                                      • K
                                        kyle.heath @Wayne Workman
                                        last edited by Jan 10, 2017, 2:30 PM

                                        @Wayne-Workman Yeah I can log into my fog management console using google chrome on my VM.

                                        K 1 Reply Last reply Jan 10, 2017, 2:36 PM Reply Quote 0
                                        • K
                                          kyle.heath @kyle.heath
                                          last edited by Jan 10, 2017, 2:36 PM

                                          @kyle.heath I may try to revert my VM to an earlier state and see if that helps.

                                          1 Reply Last reply Reply Quote 0
                                          • 1
                                          • 2
                                          • 3
                                          • 2 / 3
                                          2 / 3
                                          • First post
                                            24/60
                                            Last post

                                          158

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project