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

Computer Name after imaging

Scheduled Pinned Locked Moved
Windows Problems
2
3
856
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
    loraxyguy
    last edited by Aug 8, 2020, 1:54 AM

    I have been using FOG host registration to set a computer name, and when I would deploy my image, the computer will always be set to the host name. Great! (No Fog Client). This is not a sysprepped image.

    Now, when I go to deploy a sysprepped image, the computer name always ends up as a random name, such as desktop-xxxxx standard/default unattend.xml, instead of the FOG host name that I registered it as. Is this simply a limitation of what can be done here? I am guessing FOG changes the name, but then sysprep changes the name after that? I believe the FOG client could resolve this, but I am seeing if it can done without.

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by george1421 Aug 7, 2020, 8:35 PM Aug 8, 2020, 2:35 AM

      There is a solution for this, it is to use a post install script to update the unattend.xml file on the target computer. This is how I use fog. I don’t use the fog client because the OU and host name are calculated at deployment time.

      The basis of this is documented here: https://forums.fogproject.org/topic/8889/fog-post-install-script-for-win-driver-injection

      I know the tread is a bit cluttered now, but look at the very top post then scroll to the bottom for the remainder of the posts. Pay special attention to this script fog.ad it has what you need to update the unattend.xml script on 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!

      L 1 Reply Last reply Aug 10, 2020, 5:50 AM Reply Quote 0
      • L
        loraxyguy @george1421
        last edited by Aug 10, 2020, 5:50 AM

        @george1421 Very nice, I will have to read into this. I will just need to comment out the AD domain joining and keep the host name change part only.

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

        200

        Online

        12.0k

        Users

        17.3k

        Topics

        155.2k

        Posts
        Copyright © 2012-2024 FOG Project