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

Client Not Joining AD Domain after Updating to Fog 1.3.0

Scheduled Pinned Locked Moved Solved
FOG Problems
2
3
1.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
    rstockham23
    last edited by Jun 29, 2016, 2:38 PM

    I recently updated to Fog 1.3.0 in order to be able to create and deploy images for Win 10 and Chromium. Had great success with Chromium, but yesterday I was trying to create and deploy a Windows 7 image. I’m a long time fog user and never had problems with this before, but after deploying the image, it did not auto-join the domain. The setting was selected for that client to join the domain and all the settings were still correct from the previous version, but after the image, it never joined. It changed the name, etc, but did not join the domain. Anyone else have any issues with this after updating? I’m not really sure where to go to troubleshoot what’s happening.

    Note: I did use Sysprep and the new Client. I followed the directions to disable the Fog Service and use the sysprep script to re-enable the service after the image. I also removed the checkbox for the early namechange option as well. All seemed to work except for the domain joining.

    1 Reply Last reply Reply Quote 0
    • W
      Wayne Workman
      last edited by Wayne Workman Jun 29, 2016, 8:42 AM Jun 29, 2016, 2:41 PM

      We need the client log to help. It’s here: c:\fog.log

      Also, 1.3.0 is not released yet. FOG Trunk will eventually become 1.3.0, but until then it’s just fog trunk.

      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
      • R
        rstockham23
        last edited by Jun 29, 2016, 3:41 PM

        Thanks Wayne. I checked out the log and also communicated some with Tom. I had to update my Active Directory info in Fog for Legacy Fogcrypt and the new password system. All is well now. Thanks!

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

        231

        Online

        12.1k

        Users

        17.3k

        Topics

        155.3k

        Posts
        Copyright © 2012-2024 FOG Project