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

New Machine Problems

Scheduled Pinned Locked Moved
Hardware Compatibility
4
26
9.9k
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.
  • G
    george1421 Moderator @Andrew134
    last edited by Jul 21, 2016, 1:33 PM

    @Andrew134 @Developers a little input on adjusting the image here?

    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!

    A 1 Reply Last reply Jul 21, 2016, 2:23 PM Reply Quote 0
    • A
      Andrew134 @george1421
      last edited by Jul 21, 2016, 2:23 PM

      @george1421 said in New Machine Problems:

      @Andrew134 @Developers a little input on adjusting the image here?

      Actually it seems like I got it working. Not exactly sure how but now my Elitedesk is up with the image. Lenovo not so much but I am beginning to believe the machine is the problem not fog Thank you everyone so much for your help! Cannot express how happy I am that this community is so helpful/ responsive to questions. If I come back around to thinking the image is the issue I will open a new topic but at this point I think it is the machine.

      G 1 Reply Last reply Jul 21, 2016, 2:33 PM Reply Quote 0
      • G
        george1421 Moderator @Andrew134
        last edited by Jul 21, 2016, 2:33 PM

        @Andrew134 Which ever you decide on this hardware, you will be happy with the 100s of improvements with the 1.3.0 build over 1.2.0.

        I would suggest that you go through the global fog settings and then look at the storage node settings to be sure they are now consistent with what you need.

        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!

        A 1 Reply Last reply Jul 21, 2016, 3:30 PM Reply Quote 0
        • A
          Andrew134 @george1421
          last edited by Jul 21, 2016, 3:30 PM

          @george1421 Got a quick one for you. What do I have to put in AD settings to make it work? The machine I added is not joining the domain automatically like it use to. Again I am sure it is a minor change like when we upgraded to 1.2.0 but I have not been successful at finding an answer.

          G 1 Reply Last reply Jul 21, 2016, 3:40 PM Reply Quote 0
          • G
            george1421 Moderator @Andrew134
            last edited by Jul 21, 2016, 3:40 PM

            @Andrew134 Lets see.

            I don’t use fog to connect the target to AD but use the unattend.xml file instead so, I’m going to have to make some educated guesses.

            You have the FOG client installed on the target computer? If so did you remember to start the fog client service and is it running?
            For the target computer are you sure you have the AD credentials set in the host properties in AD. That defined user account must have domain edit rights.
            Did you properly define the OU path for the target computer?

            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!

            1 Reply Last reply Reply Quote 0
            • A
              Andrew134
              last edited by Jul 21, 2016, 4:19 PM

              Just so others know/ so you know. There are two different Domain password spots. One for if you have the new client installed and one for legacy clients. It had my password in the new one’s spot where the client on my machines is the old client. Used FOGCrypt to generate the Legacy password again and it worked like a champ.

              1 Reply Last reply Reply Quote 1
              • 1
              • 2
              • 2 / 2
              2 / 2
              • First post
                21/26
                Last post

              159

              Online

              12.1k

              Users

              17.3k

              Topics

              155.4k

              Posts
              Copyright © 2012-2024 FOG Project