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

    Windows 10 Domain Issue

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    5
    43
    10.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.
    • T
      Towndrunk
      last edited by

      I have been looking for an answer to this, and I can’t seem to figure out what my issue is. I recently updated from FOG 1.2.0 to Trunk to get the imaging working on our new Computers. Now that the imaging is working I’m trying to figure out why I can’t get our new images to add themselves to the domain.

      I have put the settings in the FOG Settings, Group Settings, and Host Settings with no change no matter where I put the information. I have both the normal password, as well as the Legacy password with FOGCrypt. The FOG Service is running on the image and I have the Hostname Changer enabled.

      I don’t know if I’m missing something, or if there is another log I can check for this. This is a Windows 10 Pro image that I’m trying to deploy. Any help would be appreciated. Thanks.

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

        Are you using the legacy or new client (and if so what version)? The legacy client has poor support for Windows 10.

        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 0
        • T
          Towndrunk
          last edited by Towndrunk

          I updated from 1.2.0 this week. I’m not currently using the following.

          Running Version 8537
          SVN Revision: 5892

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

            The legacy client does not support Windows 10 domain joining unfortantly.

            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.

            T 1 Reply Last reply Reply Quote 0
            • T
              Towndrunk @Joe Schmitt
              last edited by

              @Joe-Schmitt so the version that I’m using at this time does not support Windows 10 domain joining?

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

                You have to use the new client that comes with trunk to get windows 10 support.

                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.

                T 1 Reply Last reply Reply Quote 0
                • T
                  Towndrunk @Joe Schmitt
                  last edited by

                  @Joe-Schmitt I did update to trunk. The version that I’m running right now has the option for a Windows 10 image. I’m able to capture and deploy a Windows 10 image using those settings. I just can’t get it to join the domain.

                  Tom ElliottT 1 Reply Last reply Reply Quote 0
                  • Tom ElliottT
                    Tom Elliott @Towndrunk
                    last edited by

                    @Towndrunk I feel a need to clarify.

                    Windows 10 and Legacy Client will not work automatically, but it can work.

                    In the Windows 10 Image, get the RSAT Tools and enable (Follow this path)
                    Remote Server Administration Tools->Role Administration Tools->AD DS And AD LDS Tools->AD DS Tools->AD DS Snapin-ins and Command-line Tools

                    You don’t need anything else installed/enabled in RSAT for Domain joining to work on Windows 10 with the legacy client. However, I would not recommend using this as a means as it does enable the system to have relatively easy enabled access to actually look at and manage your Domain Controller from any system in your environment that has received this image. It will work, but it’s just easier to switch to the new client.

                    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

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

                      @Towndrunk The client is not FOG itself. The client is a separate file that you must install on the system images. FOG’s GUI having “Windows 10” in the list is only relevant to the image it’s referencing, it has nothing to do with the FOG Client software.

                      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

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

                        @Tom-Elliott @Towndrunk OR install the new client on your image.
                        https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#The_Different_Installers

                        There are two different clients. Legacy client and new client. You need the new client.

                        Updating to trunk does not mean all your images have the new client. Your images remain unchanged, in fact. You have to update them. Remove the old client, install the new client, re-capture and everything will work.

                        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
                        • T
                          Towndrunk @Tom Elliott
                          last edited by

                          @Tom-Elliott OK, I think I understand. Once I updated to Trunk, I went to “Service Configuration” and under “Client Management” and installed the new client from there before I made a new image. Looking at both the PC I made captured the image from, and the PC I deployed it to, they are both running FOG Service v 0.11.3

                          Is that the Client that you are talking about?

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

                            Please upload the fog.log from one of your problem hosts here. (Usually c:\fog.log).

                            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.

                            T 1 Reply Last reply Reply Quote 1
                            • T
                              Towndrunk @Joe Schmitt
                              last edited by

                              @Joe-Schmitt This is the log file from a PC that I just tried to deploy to. Windows 10 works fine, but not on the domain like in the past with Windows 7. I’m sure I have something wrong. I see the following in the log, but from that same PC right now I can reach the DC. Not sure what I have wrong.

                              7/14/2016 2:36 PM Client-Info Client Version: 0.11.3
                              7/14/2016 2:36 PM Client-Info Client OS: Windows
                              7/14/2016 2:36 PM Client-Info Server Version: 8537
                              7/14/2016 2:36 PM Middleware::Response Success
                              7/14/2016 2:36 PM HostnameChanger Checking Hostname
                              7/14/2016 2:36 PM HostnameChanger Hostname is correct
                              7/14/2016 2:36 PM HostnameChanger Attempting to join active directory
                              7/14/2016 2:36 PM HostnameChanger The specified domain either does not exist or could not be contacted, code = 1355

                              0_1468597067288_fog.log

                              1 Reply Last reply Reply Quote 0
                              • Tom ElliottT
                                Tom Elliott
                                last edited by

                                Based on the error I’m seeing:

                                https://social.technet.microsoft.com/Forums/en-US/6407eba2-58ac-4b07-9cf5-bddcffdcf19c/error-1355-the-specified-domain-either-does-not-exists-etc?forum=identitylifecyclemanager

                                It sounds like it just can’t find your domain so it cannot connect to the domain.

                                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

                                T 1 Reply Last reply Reply Quote 0
                                • T
                                  Towndrunk @Tom Elliott
                                  last edited by

                                  @Tom-Elliott I wasn’t sure if that had something to do with the settings or something else. Once the PC boots after the image is deployed, and I log in, I can add it to the domain manually with the same credentials/information I entered into FOG.

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

                                    @Towndrunk In the AD settings in FOG, are you using the FQDN or a sloppy 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/

                                    T 1 Reply Last reply Reply Quote 0
                                    • T
                                      Towndrunk @Wayne Workman
                                      last edited by

                                      @Wayne-Workman I’m using the FQDN, Ottawacc.local I have tried it both ways, and in all three locations. . . Settings, Group, and Host settings.

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

                                        @Towndrunk Try loosing the .local part.

                                        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/

                                        T 1 Reply Last reply Reply Quote 0
                                        • T
                                          Towndrunk @Wayne Workman
                                          last edited by

                                          @Wayne-Workman I will try it again now, with just Ottawacc. Is there one setting that overrides the other? If I am going to use this for every computer, would it be best to put it in the FOG Settings, or the Group Settings?

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

                                            @Towndrunk said in Windows 10 Domain Issue:

                                            Is there one setting that overrides the other?

                                            Not sure what you’re referring to.

                                            If I am going to use this for every computer, would it be best to put it in the FOG Settings, or the Group Settings?

                                            First in FOG Settings, then use groups to apply the defaults. When it’s in FOG Settings, inside groups when you check the join domain checkbox - and the fields are already cleared - it’ll populate with the defaults you have in FOG Settings.

                                            Also - just putting these things in FOG Settings ONLY will not automatically change settings on hosts. You have to tell fog to do this. This allows FOG to manage domain joining settings on a per-host basis. At my work, we have one fog server that joins computers to 2 different domains.

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

                                            208

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project