Like @Tom-Elliott said, the initial postdownload script always runs. However, you can use CASE or IF statements to either call a function or open another script. Here is my current postdownload script that I got from one of @george1421 and his wonderful driver injection scripts found here
#!/bin/bash
. /usr/share/fog/lib/funcs.sh
[[ -z $postdownpath ]] && postdownpath="/images/postdownloadscripts/"
if [ $img == "Win7BaseVM" ] || [ $img == "Win10BaseVM" ] ; then
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 /ntf >/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.deletelog
. ${postdownpath}fog.drivers
#. ${postdownpath}fog.ad
umount /ntfs
;;
*)
echo "Non-Windows Deployment"
debugPause
return
;;
esac
fi
You can see that I have an if statement at the beginning to only run his driver injection script if the image name is one of my golden image VM’s.
@astrugatch all -S does is setup the vhost file so it will redirect to requests to https. The -c specifies which private key to use. If you need the installer to create keys for you, you can use the -K switch, and if you need a new CA you can use -C switch.
The installer already creates the keys for you by default, and the fog client looks for the servers CA key for validating the client is talking to the proper server.
If you want to use your own self signed cert, I might recommend using the servers CA so it works with that being the only difference you use.
As we do create the keys, if you’d like to use the fog generated key, the installer can just be ran with the -S argument. The only thing is recommend for that case is to import the ca cert so you dont have the self signed error. Machines with the fog client installed should see the green padlock as we do import the ca as I said earlier.
@tom-elliott Tom, I just got around to installing a fresh CentOS 7.5 minimal server with FOG 1.5.4. I used the wiki instructions to install this system to the letter and it appears to be fixed. Sorry for the delay. I have another issue with 1.5.4 which I will detsil in a separate post. Thanks for your help and this post is indeed solved.
