• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. professorb24
    3. Topics
    P
    • Profile
    • Following 0
    • Followers 0
    • Topics 11
    • Posts 21
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by professorb24

    • P

      Unsolved Deploy windows 11 fog

      Windows Problems
      • • • professorb24
      1
      0
      Votes
      1
      Posts
      346
      Views

      No one has replied

    • P

      Unsolved How to use fog with two different VLANs

      FOG Problems
      • • • professorb24
      9
      0
      Votes
      9
      Posts
      593
      Views

      george1421G

      @professorb24 said in How to use fog with two different VLANs:

      Yes, I can ping the 192.168.54.X network.

      This is positive. OK hopefully last question, what is device the dhcp server on the 54.x subnet? Is it the fog server on the 52.x subnet or something else?

    • P

      Unsolved What's the best way to rename the computer before joining the domain

      FOG Problems
      • • • professorb24
      4
      0
      Votes
      4
      Posts
      551
      Views

      george1421G

      @professorb24 Here is a wiki page on the fog client install and setup: https://docs.fogproject.org/en/latest/installation/client/install-fog-client/

      The unattend.xml file is a windows thing. There are many resources on the internet that discusses its setup: https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/update-windows-settings-and-scripts-create-your-own-answer-file-sxs?view=windows-11

      The unattend.xml file is an auto answer file used by the windows setup program to preanswer all of the questions that the installer might ask during installation. There are even answer file generators on the internet that you can answer a few simple questions and it will create the answer file in the proper format like this one: https://www.windowsafg.com/win10x86_x64_uefi.html (I would be careful entering your actual license key on a internet web page, just edit the answer file when you get it by hand to include your key).

      I also have some tutorials on fog post install scripts. This one has code snippets at the bottom of the post that discuss the unattend.xml file and how to potentially update the file with the script. https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script The way the forum works read the first post and then scroll to the end to read the second and third posts in the series.

    • P

      Unsolved post-installation script

      FOG Problems
      • • • professorb24
      2
      0
      Votes
      2
      Posts
      177
      Views

      george1421G

      @professorb24 I have a tutorial on how to do this with Dell computers, but the concept is almost the same for other vendors. The key is to have the driver files in inf format so pnputil.exe can install them. Lenovo use to have drivers in .exe format and not .inf format. That made things a bit harder when I was trying to setup lenovo computers.

      Looking at the script and it doesn’t appear to do anything. other than mount a wim image, but also be aware that the post install script runs withing a linux environment so it can’t directly interact with windows or the .wim file.

      Your post install script should copy the drivers over to the target computer after the image is placed on the target computer. All that FOG can do is leave files behind for windows to find them during OOBE/WinSetup.

    • P

      Unsolved inacessible boot device lenovo thinkbook laptop

      FOG Problems
      • • • professorb24
      2
      0
      Votes
      2
      Posts
      205
      Views

      george1421G

      @professorb24 I can read your post a number of ways. Let me see if I understand the intent. Let me use my words to describe your issue as I understand it.

      You imaged a computer with the same image that works with an HP laptop onto a Lenovo. When you boot through the FOG iPXE menu on the HP, it exits correctly and the target computer boots as expected. But when I boot through the FOG iPXE menu with the Lenovo it fails to boot saying inaccessible boot device.

      If I understand the issue correctly, then if you changed the boot order on the lenovo so that it boots directly from the hard drive does it boot correctly? In my mind its not clear if it is an image issue (something wrong with the information on the disk) or is it an iPXE or refind issue.

    • P

      Unsolved PXEv4 couldn't find ip address

      FOG Problems
      • • • professorb24
      3
      0
      Votes
      3
      Posts
      289
      Views

      Tom ElliottT

      @george1421 NBP is almost always the “label” of UEFI, but you’re describing PXEv4 MAC?

      Similarly, hte 0.0.0.0 seems to indicate that there’s no IP address on the machine in question. Maybe there’s no DHCP server.

      Without an image or more detail, we’re not sure how to help as @george1421 as suggested.

    • P

      Unsolved Inject HP and Lenovo drivers, applications such as Office, Google Chrome, Mozilla Firefox, VLC media player and fonts like Garamond, and Avenir light, demi, and regular into the Windows 11 images

      FOG Problems
      • • • professorb24
      5
      0
      Votes
      5
      Posts
      628
      Views

      P

      @Tom-Elliott i’ve tried this fog.custominstall

      Create the following file named fog.custominstall in the following path on the FOG server /images/postdownloadscripts.
      Copy the content into that newly created file
      #!/bin/bash
      . /usr/share/fog/lib/funcs.sh
      [[ -z $postdownpath ]] && postdownpath=“/images/postdownloadscripts/”
      case $osid in
      5|6|7|9)
      clear
      [[ ! -d /ntfs ]] && mkdir -p /ntfs
      getHardDisk
      if [[ -z $hd ]]; then
      handleError “Could not find hdd to use”
      fi
      getPartitions $hd
      for part in $parts; do
      umount /ntfs >/dev/null 2>&1
      fsTypeSetting “$part”
      case $fstype in
      ntfs)
      dots “Testing partition $part”
      ntfs-3g -o force,rw $part /ntfs
      ntfsstatus=“$?”
      if [[ ! $ntfsstatus -eq 0 ]]; then
      echo “Skipped”
      continue
      fi
      if [[ ! -d /ntfs/windows && ! -d /ntfs/Windows && ! -d /ntfs/WINDOWS ]]; then
      echo “Not found”
      umount /ntfs >/dev/null 2>&1
      continue
      fi
      echo “Success”
      break
      ;;
      )
      echo " * Partition $part not NTFS filesystem"
      ;;
      esac
      done
      if [[ ! $ntfsstatus -eq 0 ]]; then
      echo “Failed”
      debugPause
      handleError "Failed to mount $part ($0)\n Args: $"
      fi
      echo “Done”
      debugPause
      . ${postdownpath}fog.copydrivers
      # . ${postdownpath}fog.updateunattend
      umount /ntfs
      ;;
      *)
      echo “Non-Windows Deployment”
      debugPause
      return
      ;;
      esac

      Save and exit your text editor.
      Make the script executable with chmod 755 /images/postdownloadscripts/fog.custominstall **this part i get chmod: cannot * chmod 755 ‘/images/postdownloadscripts/fog.custominstall’ :No such file or directory please help!!!
      fog.copydrivers

      Create the following file named fog.copydrivers in the following path on the FOG server /images/postdownloadscripts.
      Copy the content into that newly created file
      #!/bin/bash
      ceol=tput el;
      manu=dmidecode -s system-manufacturer;
      dots “Identifying hardware”
      case $manu in
      [Ll][Ee][Nn][Oo][Vv][Oo])
      machine=$(dmidecode -s system-version)
      ;;
      [Dd][Ee][Ll][Ll])
      machine=$(dmidecode -s system-product-name)
      ;;
      I[Nn][Tt][Ee][Ll])
      # For the Intel NUC and intel mobo pick up the system type from the
      # baseboard product name
      machine=$(dmidecode -s baseboard-product-name)
      ;;
      *)
      # Technically, we can remove the Dell entry above as it is the same as this [default]
      machine=$(dmidecode -s system-product-name)
      ;;
      esac

      if the machine isn’t identified then no need to continue with this script, just return to caller

      if [[ -z $machine ]]; then
      echo “Unable to identify the hardware for manufacturer ${manu}”;
      debugPause;
      return;
      fi
      echo “${machine} Identified”;

      Removes Spaces in machine name, works better with path definitions machine=“${machine%”${machine##*[![:space:]]}“}”; 14-Sep-23 Jeffrey Boulais posted that the above code did not work for his install. He supplied this code as an alternative. If you run in to a problem using my code comment out my code and see if his code works better for your installation. The only right way is the one that works. Thank you Jeff for your input. machine=“$(echo -e “${machine}” | tr -d ‘[:space:]’)” 03-Jan-24 marsface posted that he could not get either of the two above machine clean up commands to work correctly so he provided this one below which worked for him.

      machine=“${machine//[[:space:]]/}”

      dots “Verifying we’ve found the OS disk”
      if [[ ! -d /ntfs/windows && ! -d /ntfs/Windows && ! -d /ntfs/WINDOWS ]]; then
      echo “! OS root Not found !”;
      debugPause
      return;
      fi
      echo “Found”;

      dots “Verifying target Arch”
      system64=“/ntfs/Windows/SysWOW64/regedit.exe”
      [[ ! -f $system64 ]] && arch=“x86” || arch=“x64”
      echo “${arch} found”;

      debugPause

      set osn path names based on the osid set in the FOG WebGui

      case $osid in
      5) osn=“win7” ;;
      6) osn=“win8” ;;
      7) osn=“win8.1” ;;
      9) osn=“win10” ;;
      esac

      dots “Preparing Drivers”
      clientdriverpath=“/ntfs/Drivers”
      remotedriverpath=“/images/drivers/$machine/$osn/$arch”

      debugPause

      if [[ ! -d “${remotedriverpath}” ]]; then
      echo “failed”;
      echo " ! Driver package not found for ${machine}/$osn/$arch ! ";
      debugPause;
      return;
      fi
      echo “Ready”;

      debugPause

      [[ ! -d $clientdriverpath ]] && mkdir -p “$clientdriverpath” >/dev/null 2>&1
      echo -n “In Progress”

      rsync -aqz “$remotedriverpath” “$clientdriverpath” >/dev/null 2>&1

      [[ ! $? -eq 0 ]] && handleError “Failed to download driver information for [$machine/$osn/$arch]”

      debugPause

    • P

      img to iso

      General
      • • • professorb24
      6
      0
      Votes
      6
      Posts
      862
      Views

      Tom ElliottT

      @professorb24 I’m really not understanding what the issue is.

      Are you asking “How do you deploy an image?”

      if that’s the case, you’re not using the GUI?

      I don’t fully understand what you’re asking here.

    • P

      Unsolved bootable USB FOG image

      FOG Problems
      • • • professorb24
      6
      0
      Votes
      6
      Posts
      970
      Views

      P

      @george1421: I cannot launch the FOS Linux engine.

    • P

      Unsolved Can't get pxe boot on my VM (FOG)

      FOG Problems
      • • • professorb24
      4
      0
      Votes
      4
      Posts
      373
      Views

      george1421G

      @professorb24 said in Can't get pxe boot on my VM (FOG):

      me to give out “fake” IP addresses

      I think we have a language conflict here.

      To use fog, the target computers (the devices where you will deploy your image), must use dhcp to get the pxe boot information. If you don’t have dhcp available for the client computers you will have a difficult time booting over the network. With that said, we do have a method to boot the computes into FOG via a usb boot stick. In this case you will need to take the usb boot drive around to the computers to start the imaging process.

      The second issue you have is WDS. Right now FOG and WDS can not both occupy the same IP subnet since they will fight each other for network booting.

    • P

      Unsolved Can't deploy image with FOG and PXE FOR FOG

      FOG Problems
      • • • professorb24
      1
      0
      Votes
      1
      Posts
      129
      Views

      No one has replied

    • 1 / 1