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

    Thinkcentre M57p wont register

    Scheduled Pinned Locked Moved
    FOG Problems
    4
    25
    8.6k
    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.
    • Jaymes DriverJ
      Jaymes Driver Developer
      last edited by

      [quote=“dwayneS, post: 36032, member: 25830”]Yes all of that was done and was working OK from day 1. After making the changes I mentioned above all was well. I only have 2 issues now.

      1. a section of my unattended file seems to not work. There is a command to enable the administrator account but that not working. I need to revisit.
      2. The computer is not being joined to the domain via fog client service. When I check the log file I get an unknown error 2202.[/quote]

      Is this by chance an old image? I have had problems like this happen (with one unit in particular that we use for nComputing) where the Administrator user becomes corrupt and had to be removed. I also add a SECOND administrator when I use the unattend file, i name him Admin, that way I have two instances in which to enter as the admin user.

      The only resolve I had for my issue was to set my image up again, it was daunting and well worth it!

      I am glad you got your FOG issue fixed, and thanks for telling us HOW you fixed it, that will help users in the future, I hope you get your image issue fixed 😞

      WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

      1 Reply Last reply Reply Quote 0
      • M
        Mentaloid
        last edited by

        You upgraded to 1.2.0? If so, you might want to verify that the default domain settings are correct in FOG config, noting that the domain portion should NOT be included in the username anymore.

        If you have clients that are not using the default (as in you specified the OU, and therefore the rest of the domain settings as well), then you may need to double check the individual clients/groups as well for misconfigured domain/user’s

        1 Reply Last reply Reply Quote 0
        • D
          dwayneS
          last edited by

          [quote=“Juan Antonio, post: 36077, member: 23837”]dof You set up the domain in FOG?[/quote]
          Yes i did set it up. i had it setup prior to the upgrade

          1 Reply Last reply Reply Quote 0
          • D
            dwayneS
            last edited by

            [quote=“Jaymes Driver, post: 36168, member: 3582”]Is this by chance an old image? I have had problems like this happen (with one unit in particular that we use for nComputing) where the Administrator user becomes corrupt and had to be removed. I also add a SECOND administrator when I use the unattend file, i name him Admin, that way I have two instances in which to enter as the admin user.

            The only resolve I had for my issue was to set my image up again, it was daunting and well worth it!

            I am glad you got your FOG issue fixed, and thanks for telling us HOW you fixed it, that will help users in the future, I hope you get your image issue fixed :([/quote]
            Thanks i always try to share solutions to problems i encounter as someone sure will be in my position somewhere down the line. No its not an old image. The win7 images are new and its my first time doing sysprep and first time deploying win7 on fog

            1 Reply Last reply Reply Quote 0
            • D
              dwayneS
              last edited by

              [quote=“Mentaloid, post: 36203, member: 4362”]You upgraded to 1.2.0? If so, you might want to verify that the default domain settings are correct in FOG config, noting that the domain portion should NOT be included in the username anymore.

              If you have clients that are not using the default (as in you specified the OU, and therefore the rest of the domain settings as well), then you may need to double check the individual clients/groups as well for misconfigured domain/user’s[/quote]
              hmmm thats interesting. i will have to try that when i return to work. the domain user section that is. When i searched the 2202 error is an AD authentication error and not a fog error, stating that the provided name is incorrect or in wrong format

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

              239

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project