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

Win 10 Hostname Changer

Scheduled Pinned Locked Moved Unsolved
FOG Problems
2
5
550
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.
  • B
    benswan
    last edited by Nov 14, 2018, 2:46 PM

    I am testing deploying Win 10 image. The first time I deployed it, everything worked flawlessly. I made some changes to the image (nothing major) and then redeploy the image to the same machine. Now it seems as if FOG is changing the name and deploying it in our domina to early. The computer reboots before Windows has a chance to set up completely. This then causes an error in the Windows set up. In the management console, I can uncheck hostname changer and the image deploys perfect (obviously with a generic name). Is there a way I can delay the hostname service?

    Thanks

    1 Reply Last reply Reply Quote 0
    • S
      Scott Adams
      last edited by Nov 14, 2018, 2:57 PM

      Not sure if this is your issue, but I know that before you capture your image, you should stop the FOG Service and also set it to Disabled for the startup. Then, use a script that is called after the imaging to start the service again. I use a setupcomplete.cmd myself.

      B 1 Reply Last reply Nov 14, 2018, 3:26 PM Reply Quote 0
      • B
        benswan @Scott Adams
        last edited by Nov 14, 2018, 3:26 PM

        @Scott-Adams said in Win 10 Hostname Changer:

        setupcomplete.cmd

        Thanks Scott. I’m not sure if that is the problem or not. Shouldn’t the FOG service on the capture machine be turned off when sysprep runs? Also, the image works fine when I turn Hostname changer off, so would the service running on capture machine be the problem?

        Thanks for your reply.

        S 1 Reply Last reply Nov 14, 2018, 6:38 PM Reply Quote 0
        • S
          Scott Adams @benswan
          last edited by Nov 14, 2018, 6:38 PM

          @benswan Yes. However, you have to make sure that it is not only stopped, but disabled. If it is not disabled, the service will start back up automatically and then hostnamechanger will do its job.

          B 1 Reply Last reply Nov 15, 2018, 6:40 PM Reply Quote 0
          • B
            benswan @Scott Adams
            last edited by Nov 15, 2018, 6:40 PM

            @Scott-Adams Thanks Scott. That seemed to work with my initial test. I will test it again later this afternoon. I’m surprised that the service in the base image would impact the deployed host.

            Thanks

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

            165

            Online

            12.1k

            Users

            17.3k

            Topics

            155.3k

            Posts
            Copyright © 2012-2024 FOG Project