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

Sysprep issue with FOG_CHANGE_HOSTNAME_EARLY

Scheduled Pinned Locked Moved Solved
Windows Problems
2
5
1.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.
  • L
    Lenain
    last edited by Jan 31, 2017, 3:28 PM

    Server
    • FOG Version: 1.3.3
    • OS: Ubuntu 14.0.4.1
    Client
    • Service Version: 0.11.8
    • OS: Windows 7 Pro 64bits
    Description

    I have sysprep errors due to hostname mismatch, in windows log I got warning because the hostname have change after FOG download. I’ve unchecked the FOG_CHANGE_HOSTNAME_EARLY but I still got the problem.
    Do I have to upload the image again? Does the FOGService 0.11.8 can change the hostname during sysprep device installation? On the master the FOGService is stop and with auto start, is it the correct way?
    Thanks

    1 Reply Last reply Reply Quote 0
    • L
      Lenain @Joe Schmitt
      last edited by Feb 7, 2017, 2:37 PM

      @Joe-Schmitt
      It work fine now, thanks.

      1 Reply Last reply Reply Quote 0
      • J
        Joe Schmitt Senior Developer
        last edited by Jan 31, 2017, 3:29 PM

        @Lenain https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

        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.

        L 1 Reply Last reply Feb 1, 2017, 7:43 AM Reply Quote 0
        • L
          Lenain @Joe Schmitt
          last edited by Feb 1, 2017, 7:43 AM

          @Joe-Schmitt
          Thanks for your quick answer, I’m changing that.
          In the futures developments could it be possible for FOGService to check registry values hklm\system\setup\SetupPhase, SetupType and SystemSetupInProgress? If they are all at 0 it means that sysprep is done, so FOGService could do nothing until those values are at 0?

          1 Reply Last reply Reply Quote 0
          • J
            Joe Schmitt Senior Developer
            last edited by Joe Schmitt Feb 1, 2017, 8:49 AM Feb 1, 2017, 2:49 PM

            @Lenain I’ve been working on better sysprep integration, so at some point there should be a release that handles it automatically.

            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.

            L 1 Reply Last reply Feb 7, 2017, 2:37 PM Reply Quote 0
            • L
              Lenain @Joe Schmitt
              last edited by Feb 7, 2017, 2:37 PM

              @Joe-Schmitt
              It work fine now, thanks.

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

              160

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project