Categories

• Announcements

  Get the latest news on what's happening.
  177
  Topics
  754
  Posts

  

  @mechalas More help? Yes Please!

• General Topics

  View tutorials or talk about FOG in general.

  General

  Tutorials
  2150
  Topics
  17182
  Posts

  M

  I just pushed a fix that should solve this.

• Technical Help

  Get help with your FOG system.

  FOG Problems

  Hardware Compatibility

  Windows Problems

  Linux Problems

  Mac Problems

  General Problems
  10551
  Topics
  103411
  Posts

  J

  @george1421 Thanks for the response. The FOG Client will be installed on the devices, as it is part of the image we’ve uploaded to the manufacturer (in this case, Dell). I just didn’t know if the FOG client’s capability to join a system to the domain is restricted to systems that have just finished the imaging process via FOG or if there is another way to trigger that process.

• Developers

  Report bugs, request features, or get the latest progress.

  General

  Feature Request

  Bug Reports
  2180
  Topics
  20327
  Posts

  

  Changes needed on FOG server to support NFSv4

  Build the nfsv4 virtual fs mount points mkdir -p /opt/fog/data/capture mkdir -p /opt/fog/data/images (optional) Provide the same ./postinitscript files for both capture and deploy. mkdir -p /images/dev/postinitscripts mkdir -p /images/postinitscripts Edit the /etc/fstab to bind mount the virtual NFSv4 file system to the physical fog directories /images/dev /opt/fog/data/capture none bind 0 0 /images /opt/fog/data/images none bind 0 0

  If you included optional step #2 append this to the end of the /etc/fstab

  /images/postinitscripts /images/dev/postinitscripts none bind 0 0 Connect the virtual fs to the physical fs mount -a

  Now you should be able to run these commands to see if the mount works. Looking at /opt/fog/data/capture should give the same list as /images/dev and looking at /opt/fog/data/images should give the same list as /images. If that is valid then move on to the next step.

  Now we need to get the gid and uid of the fog service account fogproject.
  5.1 Run the following command to get fogproject’s uid: grep fogproject /etc/passwd | cut -d ":" -f3 note this value. It will most likely be 1000 or 1001 but could be anything, it depends on the host OS.
  5.2 Run the following command to get fogproject's gid: grep fogproject /etc/passwd | cut -d ":" -f4 note this value. It will most likely be 1000 or 1001. You will need the uid and gid values in the next step.

  Edit the /etc/exports file. In this case we are converting FOG to only operate in NFSv4 mode. So we will remove all of the FOG NFSv3 export lines and replace them with the NFSv4 export lines. Insert the following into the /etc/exports file.

  /opt/fog/data/ *(fsid=0,no_subtree_check,insecure) /opt/fog/data/images *(ro,sync,nohide,no_subtree_check,all_squash,insecure,anonuid=1001,anongid=1001) /opt/fog/data/capture *(rw,sync,nohide,no_subtree_check,all_squash,insecure,insecure_locks,no_wdelay,anonuid=1001,anongid=1001)

  Be sure to update the anonuid= and anongid= values above to match the values of the uid and gid you collected in the previous step.

  The last step is FOG server linux OS dependant. We will need to enable NFSv4 and disable all other NFSvX support. For Debian variants you need to do this:
  7.1 Edit /etc/default/nfs-common and make these adujustments NEED_STATD="no" NEED_IDMAPD="yes"

  7.2 Edit /etc/default/nfs-kernel-server Note that RPCNFSDOPTS is typically not included by default. Please add that option if it is not present.

  RPCNFSDOPTS="-N 2 -N 3" RPCMOUNTDOPTS="--manage-gids -N 2 -N 3"

  7.3 For RHEL compatible linux OS, edit /etc/nfs.conf and make thest changes:

  [nfsd] tcp=y vers2=n vers3=n vers4=y vers4.0=y vers4.1=y vers4.2=y

  ref: https://wiki.debian.org/NFSServerSetup

  Reboot the FOG server. This will check your edits as well as restart the NFS server in v4 mode.