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

Join domain not working in 1.2.0

Scheduled Pinned Locked Moved
FOG Problems
6
12
4.8k
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.
  • J
    Junkhacker Developer
    last edited by Sep 26, 2014, 7:36 PM

    what shows up in the c:\fog.log file of the computer you re-imaged that is not joining the domain?

    signature:
    Junkhacker
    We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

    1 Reply Last reply Reply Quote 0
    • A
      Andrew Seals
      last edited by Sep 27, 2014, 1:35 AM

      It is only showing events from today. I will image another PC and pull the log right after it finishes.

      1 Reply Last reply Reply Quote 0
      • J
        jbrabhamMSD
        last edited by Sep 28, 2014, 2:54 AM

        I’m seeing the same issue. I just upgraded to 1.2 and my clients are not joining, with ‘Join Domain after image task’ being checked. It worked on .32. Fog.log shows the following:

        HostRegister Exiting because only 1 mac address was found
        HostNameChanger Module is disabled on this host
        HostnameChanger Host name was not found in the database

        Both HostRegister and HostnameChanger are checked (enabled) under Service Configuration.

        1 Reply Last reply Reply Quote 0
        • C
          Chris Whiteley
          last edited by Sep 28, 2014, 11:47 PM

          bump as I am having this problem as well

          1 Reply Last reply Reply Quote 0
          • P
            pijltje
            last edited by Sep 29, 2014, 3:14 PM

            same here…

            1 Reply Last reply Reply Quote 0
            • A
              Andrew Seals
              last edited by Sep 29, 2014, 4:50 PM

              My log is attached. It wouldn’t let me copy/paste it here

              [url=“/_imported_xf_attachments/1/1385_fog1.txt?:”]fog1.txt[/url]

              1 Reply Last reply Reply Quote 0
              • J
                Junkhacker Developer
                last edited by Sep 29, 2014, 5:32 PM

                “HostnameChanger Module is disabled on this host.” is the hostnamechanger module enabled on the host management page? these settings need to be enabled both globally and per host

                signature:
                Junkhacker
                We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

                1 Reply Last reply Reply Quote 0
                • A
                  Andrew Seals
                  last edited by Sep 29, 2014, 5:36 PM

                  Is that new from version .32 to version 1.2? I saw that in the log but wasn’t sure if I should mess with it. I will set it now and test.

                  That would make sense why a newly registered machine would reimage and rename and an old one wouldn’t. The new machine does have all of the services checked in the Fog Console.

                  1 Reply Last reply Reply Quote 0
                  • J
                    jbrabhamMSD
                    last edited by Sep 29, 2014, 6:31 PM

                    I agree, I also see Hostname changer module is disabled in the log. However, it is enabled both globally and at the host level. I’ve tried unchecking and rechecking both, to no avail. Once I delete and reregister the device, it then works correctly / reflects in the log correctly.

                    1 Reply Last reply Reply Quote 0
                    • P
                      pijltje
                      last edited by Oct 13, 2014, 8:24 AM

                      In my case it was the Host Product Key for the activation.
                      After deleting the Host Product Key from fog, the computer name was changed and the computer was added to the domain…

                      Our problem is solved,we have a working system again…;-)

                      1 Reply Last reply Reply Quote 0
                      • ?
                        A Former User
                        last edited by Apr 8, 2015, 2:31 AM

                        Just an observation for anyone scratching their head.

                        I upgraded from 0.32 to 1.2.0 and noticed that I didn’t require the domain name in front of the Domain Username anymore.

                        Used the following to diag, FOG_SERVER_ADDRESS/fog/service/hostname.php?mac=XX:XX:XX:XX:XX:XX

                        Noticed that my domain name was in duplicate before my Domain Username.

                        Logic says remove it and it was golden! Sha-wing!

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

                        179

                        Online

                        12.1k

                        Users

                        17.3k

                        Topics

                        155.3k

                        Posts
                        Copyright © 2012-2024 FOG Project