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

Add pc to domain after deploying image

Scheduled Pinned Locked Moved
Feature Request
2
2
294
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.
  • M
    mark29
    last edited by Jun 11, 2024, 3:32 AM

    Hello, I am a recent user of Fog, my configuration is the following, I’m using Fog ver 1.5.10 deploying Windows 11 images to client with Fog as DHCP server; I’m using Fog to deploy images on PC without joining to domain so my next step it will be consider to join these to AD domain.
    I have some questions about:

    1. in my AD domain we use static Ip address, so how can I configure FOG to set static ip after deploying image? Considering my clients have different IP address from the IP that FOG use for deploying image…
      Thanks in advance for any help you could provide me. Have a nice day.
    T 1 Reply Last reply Jun 11, 2024, 10:21 AM Reply Quote 0
    • T
      Tom Elliott @mark29
      last edited by Tom Elliott Jun 11, 2024, 4:30 AM Jun 11, 2024, 10:21 AM

      @mark29 The dynamic nature of images and systems FOG doesn’t track the IP address of systems, anymore. In really early versions it did track the IP address at least but hasn’t for quite some time.

      That said, I think what you’re asking for is possible but it would require a Snapin to do so, and even that would be ugly. (If it truly must be static, this would be the best route in the end if you’re requiring only using FOG to manage this I think.)

      You would create a Powershell scriptp that utilizes the Set-NetIPAddress statement and probably need a lookup to figure out which device needs to be using which IP address and all (that’s really the ugly part.)

      The best case, though, I think, is to utilize DHCP reservations, as this would not require any special programming or even a snapin for that matter (another kink that can potentially not work appropriately.)

      The DHCP server options of your AD controller, can be used to define specific IP’s in an automated way, rather than rely on a program to set the IP address.

      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.

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

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

      140

      Online

      12.0k

      Users

      17.3k

      Topics

      155.2k

      Posts
      Copyright © 2012-2024 FOG Project